Re: Different parent/child configuration without child located customization?

Le sam. 27 nov. 2021 à 21:58, Falko Modler a écrit : > Am 27.11.2021 um 20:25 schrieb Romain Manni-Bucau: > > 1. Profiles dont work by design since they must be activated and have the > > same issue that plugin flag > > In what I proposed the activation happens automatically via > ...

Re: Different parent/child configuration without child located customization?

Am 27.11.2021 um 20:25 schrieb Romain Manni-Bucau: 1. Profiles dont work by design since they must be activated and have the same issue that plugin flag In what I proposed the activation happens automatically via ... activation, so I don't get your point. Sure, if you don't have a suitable

Re: Different parent/child configuration without child located customization?

Hi Just to answer to the 2 proposals: 1. Profiles dont work by design since they must be activated and have the same issue that plugin flag 2. Tiles plugin is not bad and relates to the issue i mentionned about custom lifecycles in an old thread but it is not really related to this particular

Re: Different parent/child configuration without child located customization?

For frontend development with Maven I found it to be easiest to define a custom lifecycle for a custom artifact type / packaging, e.g. "angular-app", "angular-lib", "webpack-app" etc. This way it is possible to specify a build flow which is more appropriate for frontend development than the

Re: Different parent/child configuration without child located customization?

Hi, what also works in many cases is a profile with file activation, e.g. if there is src/main/kotlin add the kotlin plugin. You can even use flagfiles to control this, which isn't pretty but sometimes it makes sense Cheers, Falko

Re: Different parent/child configuration without child located customization?

Hi Sławomir, Ok, finally got the trick, it is a good one actually and even if a bit more verbose than mine it is more "buit-in", thanks a lot and probleme solved! Romain Manni-Bucau @rmannibucau | Blog | Old Blog

Re: Different parent/child configuration without child located customization?

Hi It can be for both cases. You want to configure everything in parent pom - right? Some executions for all child only and some for parent only. So everything can be done in one place, like: frontend-maven-plugin

Re: Different parent/child configuration without child located customization?

Hi Sławomir, It solves the parent case but not the child one (the exact opposite). So i can install node only in parent but i can't run npm install && npm run in all children. Do I miss anything? Romain Manni-Bucau @rmannibucau | Blog

Re: Different parent/child configuration without child located customization?

Hi, Try something like in parent pom maven-failsafe-plugin 3.0.0-M5 test-id

Different parent/child configuration without child located customization?

Hi all, I regularly hit an issue with plugin definition: it is not possible to define the plugin for children in a parent. Let me detail a concrete case: i want a parent module to define the plugins for children modules but I don't want the parent to have these plugins. A common solution is to