On Sat, May 9, 2009 at 4:48 PM, Joerg Hohwiller <jo...@j-hohwiller.de>wrote:
> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi there, > > I found that there is a little list of incompatibilities form m2.1 at: > > http://maven.apache.org/release-notes.html > > However there are a lot more. > > E.g. with maven 2.0.x you could have a module included in your > toplevel pom that you also add as dependency to some plugin such > as checkstyle or findbugs. In maven 2.1 you have to remove the > module declaration or you will get a cyclic dependency error > (that is hard to unserstand since it says that some module depends > on itself - which is right but you can not see this in its pom > directly because it is inherited). > I think that's a bug. Having a plugin in the same reactor is bad, but building something and then passing it to a plugin is valid imo. I've had to do that to work around not being able to build and use a plugin in the same build. > > Additionally with maven 2.0.x you could have the same build > plugin twice, such as a javadoc-plugin configured to aggregate > and a javadoc-plugin configuered per module. Maven 2.1 accepts > the pom but seems to ignore the second, duplicate plugin. > Duplicate entries are bad, you should instead configure multiple executions. Something should notify you though that it's skipping the second plugin declaration. > > Regards > Jörg > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iEYEARECAAYFAkoF7CgACgkQmPuec2Dcv/95EgCePZW6Cd/dC8R9adyPtK6o89Xf > FRUAnj9Q6GgeeIi1LVBe1kq1Kx8BrE6w > =WgUV > -----END PGP SIGNATURE----- > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
