[
http://issues.ops4j.org/jira/browse/PAXURL-10?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_11055
]
Stuart McCulloch commented on PAXURL-10:
----------------------------------------
thanks - regarding snapshots, Maven repositories are normally only releases or
only snapshots and
repo1.maven.org/maven2 is definitely only releases, so no point in checking it
ever for snapshot info.
the repository info from the pom.xml says what artifacts the repository should
be checked for, eg:
<repositories>
<repository>
<id>ops4j-repository</id>
<name>The OPS4J Standard Repository</name>
<url>http://repository.ops4j.org/maven2</url>
<snapshots>
<enabled>false</enabled>
</snapshots>
</repository>
</repositories>
so we can definitely pass this to Pax-Runner/Pax-Url but it depends if you want
to add some way
to mark repositories as either 'releases' or 'snapshots' (ie. separate
command-line options?)
> Slow maven artifact resolution/download
> ---------------------------------------
>
> Key: PAXURL-10
> URL: http://issues.ops4j.org/jira/browse/PAXURL-10
> Project: Pax URL
> Issue Type: Bug
> Components: mvn
> Affects Versions: 0.2.0
> Reporter: Stuart McCulloch
> Assignee: Alin Dreghiciu
> Priority: Critical
>
> I've noticed the 0.7.0 release of Pax-Runner seems to take longer pulling
> bundles from the local maven repository.
> It seems to sit there "connecting..." for several seconds, then decides to
> get the bundle from the local filesystem.
> It now takes over a minute to deploy, where it was taking a few seconds :(
> FYI, digging deeper it seems to be spending most of the time in
> "collectPossibleDownloads" from Pax-URL where it
> goes round querying all the remote repositories, even though it has a fixed
> version (ie. not SNAPSHOT/LATEST) and
> the artifact itself is already sitting in the local repository.
> Even for SNAPSHOT artifacts it would often be better to use the one from the
> local repository first, because a lot of
> the time these are locally compiled bundles that have not even reached the
> remote repositories. It's also pointless
> to check the central repository for SNAPSHOT information because it only has
> released artifacts.
> (Maven repositories are marked as having snapshots/releases but I don't
> believe this info is captured by Pax-URL)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general
