Torsten Werner a écrit : > On Sun, Mar 14, 2010 at 8:52 PM, Ludovic Claude > <ludovic.claud...@googlemail.com> wrote: > >> Not a bug, Maven requires all its plugins to use a real version, so this >> is why maven-javadoc-plugin is registered with its version only. >> > > But that means, we always have to change a lot of packages whenever a > new upstream version of a maven plugin has been uploaded? > > Torsten > No, the latest version of maven-debian-helper will scan the Maven repository and look for the installed version of the plugins, and force the use of those versions in the POM files. So that means that any projects that use Maven for their build will not need any change and will pick up automatically the correct Debian version. I'm assuming here that there is only one version of the plugin in Debian, which should be the case.
There is one exeption to this rule though: if you update one of the core Maven plugins (the list of which is in /usr/share/maven-repo/org/apache/maven/maven-project/debian/maven-project-debian.jar/org/apache/maven/project/pom-4.0.0.xml), then you are forced to update Maven. There has been for example an update of the maven-javadoc-plugin, and I will have to update Maven, some projects may fail if they did not specify the version of the plugin in their POM file. Normally this list of core plugins should not be upgraded unless there is a new version of Maven, this is to ensure that builds are consistent (new since Maven 2.0.9) Ludovic -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
