Thank you Stuart and Toni for detailed explanation! Very helpful. After browsing the code yesterday I did find org.ops4j.pax.url.mvn.defaultRepositories and* * org.ops4j.pax.url.mvn.repositories and used those to short cut resolution process. I also copied all of the profiles and platform definitions to local repo.
But with site and docs being down it was an adventure :) Would you consider publishing documentation in pdf format for local access in case something like that happens again? Maybe an export from confluence? Thank you again! Dmitry On Tue, Jun 9, 2009 at 9:55 AM, Toni Menzel <t...@okidokiteam.com> wrote: > > On 6/9/09, Toni Menzel <t...@okidokiteam.com> wrote: > > On 6/9/09, Dmitry Sklyut <dmi...@dsklyut.com> wrote: > >> 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. > > Apologize for that. > > > >> 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 > > Well the missing artifacts that you don't have in your local > > repo/nexus are probably the ones downloaded via the mvn url handler > > (Pax URL) that mimics maven behaviour/infrastructure. > > By default, it will use repo1.maven.org and ops4j repos when downloading. > > If you do so, then, you never have the artifacts in your repo. > > > > What can you do ? Best thing is probably to pipe all mvn handler calls > > through your nexus proxy, so it will cache the stuff for you. > > > > There are many ways to do this. > > As you see, Pax URL - MVN Handler (See > > http://paxurl.ops4j.org/display/paxurl/Mvn+Protocol) > > is the root component you are looking at. It is being used by pax > > runner pretty heavily. > > Check the settings for Repositories in Documentation to see how you > > can tweak it. > > > > > >> 2. How to stop pax-runner from trying to examine every known and unknown > >> repo while looking for latest versions of platforms and profiles > > mmhh.. how should it know where things are ? > > Best thing is to set the repository to you cache nexus: single point of > > entry. > > > >> 3. Why doesn't pax-runner respect a mirrow from settings.xml and tries to > >> go > >> out directly to repo1 and others? > > mmhh. it shouldn't. But it depends a bit on what exactly you do in > > settings.xml and where it is stored. > > (explain ?) > > Oh yes, i think to recall that mirrors are not yet implemented in our > maven-imitation. > Would be a feature request.. > > > > >> > >> Thanks in advance > >> > >> Dmitry > >> > > Hope this helps a bit. > > > > Toni > > > > > > -- > > Toni Menzel > > Independent Software Developer > > Professional Profile: http://okidokiteam.com > > t...@okidokiteam.com > > http://www.ops4j.org - New Energy for OSS Communities - Open > > Participation Software. > > > > > -- > Toni Menzel > Independent Software Developer > Professional Profile: http://okidokiteam.com > t...@okidokiteam.com > http://www.ops4j.org - New Energy for OSS Communities - Open > Participation Software. > > _______________________________________________ > general mailing list > general@lists.ops4j.org > http://lists.ops4j.org/mailman/listinfo/general
_______________________________________________ general mailing list general@lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general
