2009/6/9 Dmitry Sklyut <dmi...@dsklyut.com> > Hi All, > > Maven repo and svn outages yesterday brought up a question. Some of the > pax-runner required artifacts are not cached in either locall or in my nexus > proxy. > This is especially true of platform and profile artifacts. There was not a > a trace of those outside of maven-metadata.xml. > pax-dir-url jar artifacts was also missing, but pom was there. pax-runner > was also very slow to start while trying to look/parse maven-metadata.xml > and maven-metadata-local.xml from many locations. > > So the questions: > 1. What is the best way to replicate required artifacts in my local > environment
one way is to use the maven-pax-plugin to resolve and download the project dependencies, but this won't cache the pax-runner profiles unless you have them as dependent artifacts in your Maven project we have discussed caching of artifacts downloaded via the pax-url-mvn bundle, but afaik this is still an open issue - adding this would require either re-implementing logic to update Maven metadata (and risk corrupting the local repo) or embedding the new Mercury resolver which would be a safer option IMHO > 2. How to stop pax-runner from trying to examine every known and unknown > repo while looking for latest versions of platforms and profiles Alin has added caching of platforms/profiles: http://issues.ops4j.org/browse/PAXRUNNER-262 which should help - and he also discusses the issue of caching Maven artifacts in that issue 3. Why doesn't pax-runner respect a mirrow from settings.xml and tries to go > out directly to repo1 and others? > again it comes down to how much of Maven do we re-implement / embed inside pax-runner - the logic to scan the settings.xml and configure proxies can be quite convoluted at times. you might want to try using "mvn org.ops4j:maven-pax-plugin:provision" to invoke pax-runner - because this is a Maven plugin it has access to the relevant Maven components to look at your settings, etc. and select the correct (proxied) repositories which it then hands over to pax-runner to sum up: we're aware of the offline issues, but want to make sure we get the right solution > Thanks in advance > > Dmitry > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general > -- Cheers, Stuart
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
