On Tue, 2015-03-17 at 11:10 +0100, Emmanuel Bourg wrote: > > Great, let me know when it's ready to be merged. All ready [1] and works on two packages that I tried. Would you prefer a github pull request? I've included 2 commits (the last two) which aren't strictly necessary, but fix the bug that I was seeing intermittently in tests. I also believe the tests should be run as part of building the package otherwise they will be forgotten, but we'll have to mock out some of the process forks to make them reliable on a build machine first. They are currently turned off. It turns out there are 2 different metadata files that we need when referencing a goal instead of a phase: one for plugin prefixes and one for versions. I changed the default build to not use the prefix form when calling goals until we can get both generated. Any builds that do will fail until they change to the non-prefix form (plus an explicit version for anything other than javadoc) or wait until my next set of changes are ready. You were right about the correct name of the metadata file. > Regarding the plan, we'll also have to transition maven-ant-helper to > Maven 3. At first glance, it appears just a few dependency tweaks in the control file. It's not necessary for any projects that use maven-debian-helper, but I'll take a look. On Sat, 2015-03-14 at 09:03 +0100, Emmanuel Bourg wrote: > What logic would be obsoleted? If we could leverage the version ranges > and get rid of the generic 'debian' and '2.x' versions that would be > awesome. 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. Andrew [1] https://github.com/arcticwaters/maven-debian-helper/tree/maven3
Attachment:
signature.asc
Description: This is a digitally signed message part