I added another commit on the maven3 branch that will generate plugin and group metadata when copying the repo. It will ignore any existing metadata, i.e. the bits you added to maven-javadoc-plugin. We should now be able to rebuild maven-debian-helper package and test it against all packages that use it to build. Note that I've had to include 2 utilities to make generation work as a shell script: unzip and xmllint. Debian/control has been updated accordingly. On Sat, 2015-03-21 at 23:34 +0100, Emmanuel Bourg wrote: > Running the tests at build time is a good idea. I'll create a patch for this later since it won't affect the maven 3 work. > Maybe it's necessary to build maven-debian-helper with maven-ant-helper? > Do you remember why you had to build maven-debian-helper with itself? This change wasn't necessary, I thought it cleaner to build a maven tool with maven instead of ant. It should save a bit of maintenance effort by removing a dependency. The change can be omitted if you feel strongly against it. On a side note, it looks like maven-ant-helper does a few of the same things that maven-debian-helper does, including copying /usr/share/maven-repo and invoking maven itself. I might have to port some of my maven-debian-helper code to maven-ant-helper. Of course what is actually invoked is up to the package (xmlunit doesn't use the maven-ant-helper script much at all). I've forked the (outdated) debian git repo for maven-ant-helper to store my changes [2]. I don't think this is ready yet, I want to do a few more tests. > > See commit e18be23 in [1] for how we can get rid of '2.x' versions, but > > would take a lot of work to check and update all ~320 packages. This > > works without any maven-metadata. I'm not sure if this will cause any > > more headaches than there already are if applied on a larger scale. > > Another idea would be to rewrite the poms and use the special > LATEST/RELEASE versions instead of 'debian'. Thus the packages would no > longer contain the 'debian' artifacts. However this requires metadata > for every libraries, not just the plugins. I've done some tests with the > version ranges and it seems they need the metadata too. That's odd, I'm able to build maven-debian-helper with e18be23 without the metadata for maven-repo-helper. Not sure about LATEST/RELEASE. Andrew [2] https://github.com/arcticwaters/maven-ant-helper/tree/maven3
Attachment:
signature.asc
Description: This is a digitally signed message part