-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Stephen,
> > If A(1.0) has root(1.2-SNAPSHOT) as a parent it should never have been > released as the pom for A(1.0) is based on content from root(1.2-SNAPSHOT) > which is subject to change... which means that a released pom does not have > a definitive content... bad karma I agree and cant speak for Ralph, but I do NOT change versions (or anything else that is relevant for deploying) of container-modules at all. Why should I release a new version of my parent POMs if just some leave changed or even if some internal site-report-setting changed. People that want to use my deployed artifacts do NOT care about such changes. But in my case every developer always checks out the entire head (or tag/branch) of SCM. So there are different aspects of a deployed POM. If you ask me, all stuff like <reporting>, <scm>, <issueManagement>, <distributionManagement>, etc. is nuts for deployed POMs. But others may have a different view of the world. But this might be the point where we do not get together with relase-plugin. We simply have to accept that maven gives us flexibility to do things different ways and release-plugin maybe can NOT address all of these ways and thats just OK. > > -Stephen > Regards Jörg -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAkoNxdIACgkQmPuec2Dcv/8SEgCgl/9Hnv5vfFAaRpz3noNdZuW1 x/IAn0AOXx3MSnC9xWvWFZKrZURU7OcR =aIQF -----END PGP SIGNATURE----- --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
