Le 17/03/2015 04:47, Andrew Schurman a écrit : > I suppose it depends on which package triggers the trigger. My thought > was to put it solely in maven-debian-helper which does depend on > default-jdk and therefore a JRE.
The trigger I had in mind was associated with the installation of a Java library containing Maven artifacts. Whenever an artifact is installed under /usr/share/maven-repo, the trigger would generate or update the metadata files. If the trigger is installed by maven-debian-helper it won't generate the metadata of the libraries already installed. > You were close with your commit. The metadata needs to be the one found > in remote repositories: named maven-metadata.xml, not > maven-medatadata-local.xml. Luckily contents of that and *-local appear > to be identical. See [1] for where this happens. Actually I added the metadata with the assumption that the system repository was used as a local repository copied at build time instead of a remote repository since that's how maven-debian-helper operates currently. > I'm going to move my changes to a branch [2] and rebase them on top of > upstream/master so I can make a few changes. The branch doesn't exist > yet, but should be there before the weekend. I've moved machines since > the last time I touched this and looks like I depended a few stale files > that don't exist on this machine. Great, let me know when it's ready to be merged. Regarding the plan, we'll also have to transition maven-ant-helper to Maven 3. 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/5507fdb3.9090...@apache.org
