You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi Marco,
Thank you for posting the demo. Unlike most demos I try, it worked first time out of the box! I like how the front and back are in different modules. I can work on front end separately and test changes with ng serve, as long as backend is running. But I can't test backend separately. I have to build the parent pom in order to test backend changes. Well that builds the front as well and it takes a long time to build the frontend over again, even though no changes were made to it. Is there a way to build and test the backend by itself? If I do mvn clean compile from the backend folder, it give error: "Could not resolve dependencies for project dev.marco:backend:jar:0.1-SNAPSHOT: Could not find artifact dev.marco:frontend:jar:0.1-SNAPSHOT".
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi Marco,
Thank you for posting the demo. Unlike most demos I try, it worked first time out of the box! I like how the front and back are in different modules. I can work on front end separately and test changes with ng serve, as long as backend is running. But I can't test backend separately. I have to build the parent pom in order to test backend changes. Well that builds the front as well and it takes a long time to build the frontend over again, even though no changes were made to it. Is there a way to build and test the backend by itself? If I do mvn clean compile from the backend folder, it give error: "Could not resolve dependencies for project dev.marco:backend:jar:0.1-SNAPSHOT: Could not find artifact dev.marco:frontend:jar:0.1-SNAPSHOT".
Beta Was this translation helpful? Give feedback.
All reactions