Path: csiph.com!fu-berlin.de!bofh.it!news.nic.it!robomod From: =?utf-8?Q?Lo=C3=AFc_Rouchon?= Newsgroups: linux.debian.maint.java Subject: Re: Debian-Java 2025 wishlists Date: Wed, 18 Dec 2024 18:40:01 +0100 Message-ID: References: X-Original-To: debian-java@lists.debian.org X-Mailbox-Line: From debian-java-request@lists.debian.org Wed Dec 18 17:30:29 2024 Old-Return-Path: X-Amavis-Spam-Status: No, score=-2.096 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FOURLA=0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, RCVD_IN_VALIDITY_CERTIFIED_BLOCKED=0.001, RCVD_IN_VALIDITY_RPBL_BLOCKED=0.001] autolearn=no autolearn_force=no X-Policyd-Weight: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 CL_IP_EQ_HELO_IP=-2 (check from: .loicrouchon. - helo: .mail-4323.proton. - helo-domain: .proton.) FROM/MX_MATCHES_NOT_HELO(DOMAIN)=0; rate: -3.5 Feedback-ID: 55091204:user:proton X-Pm-Message-ID: 4c2307bc9bc5e40d8b6ea0ea87aeb9c5d4b63d42 MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mailing-List: archive/latest/23571 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/MGoa548ArSH3hwa1yWjvU5dBt2ABFtL0f5w8Q84GJWL8KFn_Bh5V_ybnrCNau4MOnsuJy2gmM3HfriXLFMCtBwOrf72RzsyrKQrTHdl2ego=@loicrouchon.com Approved: robomod@news.nic.it Lines: 71 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Wed, 18 Dec 2024 17:13:23 +0000 X-Original-Message-ID: X-Original-References: <04c32e66-c5c7-73e4-d71f-8f7d80391efb@apache.org> <3c228ddd-0dda-453b-8d48-0bcdfe1ad56c@riseup.net> Xref: csiph.com linux.debian.maint.java:12864 Hi, Thank you for this opportunity, here is my wishlist, mostly focused on maki= ng packaging easier, especially for people unfamiliar with the Debian packaging system (like me)= : 1/ Make the Debian version of maven able to locate its own plugins. Simplest example I could come up with. - Following packages were installed: maven, maven-debian-helper, maven-rep= o-helper) - Pom did not specify the maven-clean-plugin version (so that it would be = resolved from the installed maven) $ MAVEN_OPTS=3D"-Dmaven.repo.local=3D/usr/share/maven-repo" mvn --offline= clean [INFO] Scanning for projects... [INFO] [INFO] --------------------------< org.symly:symly >---------------------= ------ [INFO] Building Symly 0.11-SNAPSHOT [INFO] --------------------------------[ jar ]---------------------------= ------ [WARNING] The artifact org.apache.maven.plugins:maven-clean-plugin:jar:2.= 5 has been relocated to org.apache.maven.plugins:maven-clean-plugin:jar:3.2= .0 [INFO] [INFO] --- maven-clean-plugin:3.2.0:clean (default-clean) @ symly --- [INFO] ------------------------------------------------------------------= ------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------= ------ [INFO] Total time: 0.065 s [INFO] Finished at: 2024-12-18T09:46:09Z [INFO] ------------------------------------------------------------------= ------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-clean-plugi= n:3.2.0:clean (default-clean) on project symly: Execution default-clean of = goal org.apache.maven.plugins:maven-clean-plugin:3.2.0:clean failed: Plugin= org.apache.maven.plugins:maven-clean-plugin:2.5 or one of its dependencies= could not be resolved: Cannot access central (https://repo.maven.apache.or= g/maven2) in offline mode and the artifact org.codehaus.plexus:plexus-utils= :jar:1.1 has not been downloaded from it before. -> [Help 1] 2/ Add a cookbook on how to create poms that are compatible with both Maven and Debian best practices as well as a step by step guide for mh_make integ= ration. The page https://wiki.debian.org/Java/Packaging/Maven is very minimal, the "mh_make" section contains a deadlink to http://collab.debian.net/portal/planet-debian/markus-koschany-pdfsam-how-to= -upgrade-a-maven-application-for-debian. The only documentation I was able to find for mh_make is the youtube video. 3/ Provide a more controlled and flexible way of locating a JRE runtime for java start scripts. A possible solution would be findjava (I'm the author). I submitted a request for packaging via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug= =3D1039109 Emmanuel Bourg started to look at how to package findjava, but stopped not sure if because of time, interest or blockers. See https://github.com/loicrouchon/findjava/issues/1 Lo=C3=AFc