Could someone from the dev team possibly explain their process of releasing parent poms such as the maven-plugins.
i see that the trunk of this includes <modules> for everything. However the release versions have this commented out. I presume this change is made just before a release is performed preventing the release plugin from processing the modules, which are not the things being 'released'. And then added again to the new SNAPSHOT version. Does this mean that the <modules> section in that pom is just developer aid and not a real part of the nature of that project., i.e. if we checkout a released version of maven-plugins we do not repeat the build that the trunk performs. I alsways get confused between the relationship and 'integration' of a parent, the indepence of children that can inherit from on older versions of the parent and the SCM domain (i.e. SVN will be copying all the child directories into the tag, even though they're not being released). couldnt find anything on the net explaining these kinds of scenarios and my head hurts from trying to anticipate the various pom relationships and ther overall dev and release lifecycle. Cheers, John -- View this message in context: http://www.nabble.com/Release-aggregating-parent-poms-tp20852139p20852139.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
