Use an aggregated repository as default maven repository
--------------------------------------------------------
Key: PAXURL-62
URL: http://issues.ops4j.org/browse/PAXURL-62
Project: Pax URL
Issue Type: Improvement
Components: mvn
Reporter: Alin Dreghiciu
Assignee: Alin Dreghiciu
Fix For: 1.0.1
back on the performance issue with pax exam/pax runner we discussed a while
back. One of the reasons finding something as a profile goes slow is because of
the resolution process, To figure out where an artifact is located mvn: handler
has to go to all the repos and look for metadata determine highest version (in
some cases) and then get the artifact. In case that there are more repositories
out there , as in current case where we have 4 (central, ops4j, spring
external, spring releases) this process could be very slow. An simple solution
to speed this up is to have just one repo to look into it.
This is the reason why I asked for this:
https://issues.sonatype.org/browse/OSSRH-50 . And this is already done and can
be accessed at: {{http://osgi.sonatype.org/content/groups/pax-runner/}}
the advantage in this case is that Nexus will pre merge the metadata from all
of this repositories and give it back in one shot so the resolution process
should be faster. I did not made actual measurement but is look also faster
doing a manual test.
As this is an indirection, another advantage of the approach is that in the
future we can easily add/remove repos on the fly without having users download
a new version of pax runner.
Nice is that if we do that I can remove the special handling of profile
repository that I added to the list just in case that --profiles was used, fro
the same reasons. To not search yet another repository if there are not
profiles involved. But now, the profiles repository is already in the composite
repository.
In Pax Runner the option can be tested using the
{{\--repositories=http://osgi.sonatype.org/content/groups/pax-runner/}}
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
