On Sat, 15 Oct 2016, Emmanuel Bourg wrote: > Hum old bug, it should have been closed since we use the 0.x version for > this library now.
Well closure-compiler doesn’t, it depends on the debian version, and so do all things that depend on it. > Le 15/10/2016 à 00:29, Thorsten Glaser a écrit : > > > Shouldn’t *every* artefact have a debian version, anyway? > > Every artifact (except the Maven plugins) should have a generic version > that doesn't change with every update. The recommended version is > 'debian' because it's the default and doesn't require any extra OK. > substitution rule, but sometimes we use a '<n>.x' version when two > incompatible versions share the same groupId/artifactId (junit 3 and 4 > is a good example). AFAICT, this doesn’t apply to jsr305? > > Anyway, patch attached. I applied to join pkg-java on Alioth; if > > that’s granted I’ll commit and team-upload it, otherwise I might > > consider an NMU unless you prefer to handle this. > > I added you to the group, welcome :) The patch isn't strictly OK, thanks. > necessary, you could add a substitution rule in the minify-maven-plugin > package (in debian/maven.rules) such as: No, because it chokes before mh_make is even finished, and I cannot change debian/maven.rules and restart mh_make because it starts from the beginning. > A 'debian' version wouldn't hurt though, I added a --relocate option to > maven-repo-helper recently to ease the migration from '<n>.x' to > 'debian' version or other groupId/artifactId changes. OK, nice. Merci, //mirabilos -- tarent solutions GmbH Rochusstraße 2-4, D-53123 Bonn • http://www.tarent.de/ Tel: +49 228 54881-393 • Fax: +49 228 54881-235 HRB 5168 (AG Bonn) • USt-ID (VAT): DE122264941 Geschäftsführer: Dr. Stefan Barth, Kai Ebenrett, Boris Esser, Alexander Steeg