Am 06.09.2018 um 00:03 schrieb Emmanuel Bourg: > Le 28/08/2018 à 15:25, Markus Koschany a écrit : > >> I added a new rule to debian/maven.rules >> >> org.apache.xbean maven-xbean-plugin * s/.*/4\.5/ * * >> >> Expected behavior: >> >> The version in src/pom.xml will be tranformed from 4.1 to 4.5. >> >> Result: >> >> Version is still 4.1 > > For plugins and poms the exact type and version have to be specified in > the substitution rule. For example: > > org.apache.xbean maven-xbean-plugin maven-plugin s/4.1/4.5/ * * > > I have no idea if this was designed that way or if it's a bug.
I believe it is a bit unexpected and surprises people. It seems to be inconsistent to treat plugins differently. >> Ideally libxbean-java would provide a debian version of >> maven-xbean-plugin but that's another story. > > Generic 'debian' versions don't work with plugins unfortunately. > We would have to hack the Maven plugin validation logic. Perhaps we should rethink the current logic because depending on a specific version causes build failures every time such a plugin is updated. It puts people off to make such an update because then it is expected to fix all reverse-dependencies too. But just meddling with a package because you have to adapt a Maven rule seems like not a good use of our time.
signature.asc
Description: OpenPGP digital signature
__ This is the maintainer address of Debian's Java team <https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/pkg-java-maintainers>. Please use debian-j...@lists.debian.org for discussions and questions.