Open enexusde opened 4 years ago
When it comes down to properties / profiles / modules the problem may reside within the poms and not withing the plugin, as those do not take care about resolving and/or setting variables.
Can you give a bit more detailed insight into your pom structure?
If you have a structure like this:
And configure the app's
pom.xml
to run:npm
you like to skip:npm
forApp
andBackend
.In order to skip the execution for
App
andBackend
you specify askip.npm=true
in the App'spom.xml
andskip.npm=false
in Fe1 and Fe2.The build will fail having the message:
Backend should not run the npm because it is skipped by
skip.npm=true
from the parent's pom.