Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.java > #9105 > unrolled thread
| Started by | Christopher Hoskin <christopher.hoskin@gmail.com> |
|---|---|
| First post | 2016-05-11 00:40 +0200 |
| Last post | 2016-05-11 00:50 +0200 |
| Articles | 2 — 2 participants |
Back to article view | Back to linux.debian.maint.java
Dependencies packaged without POMs Christopher Hoskin <christopher.hoskin@gmail.com> - 2016-05-11 00:40 +0200
Re: Dependencies packaged without POMs Emmanuel Bourg <ebourg@apache.org> - 2016-05-11 00:50 +0200
| From | Christopher Hoskin <christopher.hoskin@gmail.com> |
|---|---|
| Date | 2016-05-11 00:40 +0200 |
| Subject | Dependencies packaged without POMs |
| Message-ID | <rxotR-3v7-25@gated-at.bofh.it> |
[Multipart message — attachments visible in raw view] — view raw
Hello, Some libraries (e.g. Jython) are packaged for Debian, but don't use Maven. In these cases it may be that nothing is installed into /usr/share/maven-repo. How should Maven projects which reference such dependencies be packaged? According to the spec [0], <scope> and <systempath> should be used to reference such jars. But this appears not to work in practice ([1]). I suspect I'm not the first person to want to reference a library without an entry in $REPO, so I'm wondering how this is normally handled? Thanks. Christopher [0] https://wiki.debian.org/Java/MavenRepoSpec, [1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723919
[toc] | [next] | [standalone]
| From | Emmanuel Bourg <ebourg@apache.org> |
|---|---|
| Date | 2016-05-11 00:50 +0200 |
| Message-ID | <rxoDw-3zC-23@gated-at.bofh.it> |
| In reply to | #9105 |
Le 11/05/2016 à 00:34, Christopher Hoskin a écrit : > How should Maven projects which reference such dependencies be packaged? > According to the spec [0], <scope> and <systempath> should be used to > reference such jars. But this appears not to work in practice ([1]). Actually you can use <systemPath> with maven-debian-helper, it's just the package generator mh_make that doesn't support it. To deal with such a dependency you have to: 1. ignore it during the mh_make process 2. re-enable it by editing the generated debian/maven.ignoreRules file 3. patch the pom to set the <systempath> However this is really a last resort solution, it's preferable to modify the package and install the Maven artifacts. Emmanuel Bourg
[toc] | [prev] | [standalone]
Back to top | Article view | linux.debian.maint.java
csiph-web