On 4 June 2010 09:18, MartyMcFly <martymc...@smart-mail.de> wrote: > > Hi, > > I have a multimodule project in which some modules need an additional > sourcefolder, whereas other modules dont. > To avoid redefining this in each of the relevant modules I want to add this > to the parent pom and activate the project if this folder X is present. > > Unfortunately this seems not working as the activation section seems to be > interpreted during the parent pom, where no folder X exists. Ergo the > profile is deactivated and the relevant modules are failing. > > How can I activate profiles, defined in the parent pom, for some modules ? > > Is there another way which avoids redefining this in every module ? >
don't go against the maven way... apart from generated source code, you should only have one source folder per module... and if you are generating source code, best practice is to keep that in its own module (but obviously generate the source code into target/generated-source/plugin-name/..... and have the plugin add the generated directory as a source root... only as a last resource should you use build-helper) > > Thanks > > PS: Using maven 2.2.1 > -- > View this message in context: > http://old.nabble.com/Activate-differernt-profiles-in-Multimodule-projects-tp28776973p28776973.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
