I hit the same usecase discussed at your blog, and have to orchestrate maven to activate all modules at release time ( maven -B release:prepare release:perform -Dmy-release together with additional profile activation at release plugin configuration.
For the currently setup, it will not go thru release plugin, it is a way for me to create a single maven build by combine a bunch of independent component sources thru Perforce mapping -D On Thu, May 14, 2015 at 1:21 AM, Karl Heinz Marbaise <khmarba...@gmx.de> wrote: > Hi Dan, > > On 5/14/15 8:12 AM, Dan Tran wrote: > >> Hi Bernd , >> >> I dont configure or execute any maven-deploy-plugin at my top level parent >> pom. >> >> The only thing that I have which may not be very conventional: >> >> all of my modules are conditional activated by profile looking for >> existing >> existing pom >> >> <profile> >> <id>enable-compX</id> >> <activation> >> <file> >> <exists>components/compX/pom.xml</exists> >> </file> >> </activation> >> <modules> >> <module>components/compX</module> >> </modules> >> </profile> >> >> >> I am using Maven 3.2.3 >> > > What's the reason having a module activating via profile... > > > http://blog.soebes.de/blog/2013/11/09/why-is-it-bad-to-activate-slash-deactive-modules-by-profiles-in-maven/ > > Kind regards > Karl Heinz Marbaise > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
