jetty-base 9.4 : download JARs or not ?
Tom Zeller
tzeller at dragonacea.biz
Wed May 31 00:51:12 EDT 2017
Mostly Scott,
Do we want to continue to include JARs in the jetty-base 9.4 artifact
(i.e. the tar.gz or .zip) or download them via Jetty's start.jar ?
We talked about using Jetty to download files, but unfortunately Maven
Central is hardcoded.
For example, here's an example from logback-impl.mod :
[files]
maven://ch.qos.logback/logback-core/${logback.version}|lib/logback/logback-core-${logback.version}.jar
[ini]
logback.version?=1.1.7
The idea above is to use the JAR from the local Maven repo if not
present in lib/. But, if the JAR does not exist in the local Maven
repo, it is downloaded using java.net.HttpURLConnection from a
hardcoded Maven Central URL, whereas we would want to use our Nexus
repo.
However, URLs like :
[files]
https://build.shibboleth.net/nexus/service/local/artifact/maven/redirect?r=snapshots&g=net.shibboleth.idp&a=idp-testbed&v=LATEST&p=war|testbed-war/idp-testbed.war
work. We could override the [files] section of the handful of Jetty's
logging modules (by copying those modules to jetty-base/modules). We
need to override versions anyways. Maybe we can do the [files]
override in the .ini, not sure.
If we really want to use Jetty to download files from our Nexus repo,
it probably wouldn't be much work to submit a patch to use an env var
if present instead of the hardcoded Maven Central URL.
FWIW, in the question posted at the top, continuing to include JARs in
the jetty-base 9.4 artifact means using the maven-dependency-plugin
configured in the POM to do the downloading.
Thx,
Tom
More information about the dev
mailing list