Le 16/03/2015 09:46, Andrew Schurman a écrit : > Although specifying the version for javadoc may be reasonable, it will > break again if users need to add their own goals not covered by default > in a phase.
True, but the main purpose of the system repository under /usr/share/maven-repo is to build Debian packages without downloading artifacts from Maven Central. Users are not supposed to use it for their own Maven project and run random plugins. That's why I think solving the generic case is not necessary, we can focus on the few plugins relevant to the Debian packaging tasks. > A quick look at deb-triggers looks like it's just what we need. I'll > investigate a solution similar to the triggers in man-db. Ideally a trigger that doesn't use Java would be necessary, since the Java libraries do not depend on a JRE. > We know we need metadata for plugins, but it'll likely be needed for all > artifacts if we start using more features of Maven. I suggest we move forward with the following plan: 1. add the metadata to libmaven-javadoc-plugin-java (I just uploaded a new version of the plugin in experimental with the metadata included) 2. merge your changes in maven-debian-helper and bump the version to 2.0 3. install the metadata with the prefixes in maven-debian-helper 4. upload maven-debian-helper 2.0 to experimental 5. request a rebuild of the ~320 packages depending on maven-debian-helper And in a second phase, adopt a trigger based metadata generation. Emmanuel Bourg -- To UNSUBSCRIBE, email to debian-java-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: https://lists.debian.org/55070bc9.7000...@apache.org
