Bug#1054324: Inability to override install.to.usj property
Le 2023-10-21 à 17 h 28, Emmanuel Bourg a écrit : Le 21/10/2023 à 22:54, Jérôme Charaoui a écrit : Alternatives are: package name status quo, using "libjruby-maven-plugin-java" (singular), or breaking out the various plugins into different packages (even though they all depend on each other), but it's all sub-optimal. +1 for libjruby-maven-plugin-java, I'd rather not touch the settings of maven-debian-helper without extensive testing. Fair enough, I'll do that in the short term. Maybe the bug can remain open so that the issue may be looked at at some point in the future. Thanks, -- Jérôme
Bug#1054324: Inability to override install.to.usj property
Le 21/10/2023 à 22:54, Jérôme Charaoui a écrit : Alternatives are: package name status quo, using "libjruby-maven-plugin-java" (singular), or breaking out the various plugins into different packages (even though they all depend on each other), but it's all sub-optimal. +1 for libjruby-maven-plugin-java, I'd rather not touch the settings of maven-debian-helper without extensive testing. Emmanuel Bourg
Bug#1054324: Inability to override install.to.usj property
Package: maven-debian-helper Version: 2.6.4 Severity: wishlist Hello, Lately, I've been working on updating the jruby-maven-plugins package. As part of this work I wanted to rename the binary package from "jruby-maven-plugins" which is not java-policy compliant, to "libjruby-maven-plugins-java". However, this causes maven-debian-helper to install the jars into /usr/share/java because the package name isn't recognized as a maven plugin by the regex. This might be easily fixed by passing -Dinstall.to.usj=false but unfortunately this can't be done because the maven command called by the maven debhelper module passes "-Dinstall.to.usj=true" to Maven directly. I believe we can just drop this property from the debhelper Maven command-line: by default, the property is true anyway. This would allow packages to override the automatic decision to install to usj. Alternatives are: package name status quo, using "libjruby-maven-plugin-java" (singular), or breaking out the various plugins into different packages (even though they all depend on each other), but it's all sub-optimal. Thanks! -- Jérôme
