You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Igor Fedorenko (JIRA)" <ji...@codehaus.org> on 2008/04/18 16:03:55 UTC
[jira] Created: (MNG-3531) embedder always checks missing release
artifacts
embedder always checks missing release artifacts
------------------------------------------------
Key: MNG-3531
URL: http://jira.codehaus.org/browse/MNG-3531
Project: Maven 2
Issue Type: Bug
Components: Performance
Affects Versions: 2.1
Reporter: Igor Fedorenko
2.1 embedder always checks remote repositories for missing release artifacts. This is done multiple times during the same readProjectWithDependencies invocation and results in bad performance problems in embedding application (see MNGECLIPSE-523).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Moved: (MARTIFACT-25) embedder always checks missing release
artifacts
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MARTIFACT-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter moved MNG-3531 to MARTIFACT-25:
--------------------------------------------
Affects Version/s: (was: 2.1)
Fix Version/s: (was: 2.1)
3.0-alpha-1
Component/s: (was: Performance)
Workflow: jira (was: Maven New)
Key: MARTIFACT-25 (was: MNG-3531)
Project: Maven Artifact (was: Maven 2)
> embedder always checks missing release artifacts
> ------------------------------------------------
>
> Key: MARTIFACT-25
> URL: http://jira.codehaus.org/browse/MARTIFACT-25
> Project: Maven Artifact
> Issue Type: Bug
> Reporter: Igor Fedorenko
> Assignee: Jason van Zyl
> Fix For: 3.0-alpha-1
>
>
> 2.1 embedder always checks remote repositories for missing release artifacts. This is done multiple times during the same readProjectWithDependencies invocation and results in bad performance problems in embedding application (see MNGECLIPSE-523).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MNG-3531) embedder always checks missing release
artifacts
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-3531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MNG-3531:
------------------------------
Fix Version/s: 2.1
if done from the CLI - is this a regression from 2.0.9 to 2.1 behaviour?
> embedder always checks missing release artifacts
> ------------------------------------------------
>
> Key: MNG-3531
> URL: http://jira.codehaus.org/browse/MNG-3531
> Project: Maven 2
> Issue Type: Bug
> Components: Performance
> Affects Versions: 2.1
> Reporter: Igor Fedorenko
> Assignee: Jason van Zyl
> Fix For: 2.1
>
>
> 2.1 embedder always checks remote repositories for missing release artifacts. This is done multiple times during the same readProjectWithDependencies invocation and results in bad performance problems in embedding application (see MNGECLIPSE-523).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MARTIFACT-25) embedder always checks missing
release artifacts
Posted by "Igor Fedorenko (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MARTIFACT-25?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=140839#action_140839 ]
Igor Fedorenko commented on MARTIFACT-25:
-----------------------------------------
There are legit scenarios when requested artifacts do not exist in any repository (optional dependencies, for example). I think separate metadata for truly missing artifacts will always be necessary.
> embedder always checks missing release artifacts
> ------------------------------------------------
>
> Key: MARTIFACT-25
> URL: http://jira.codehaus.org/browse/MARTIFACT-25
> Project: Maven Artifact
> Issue Type: Bug
> Reporter: Igor Fedorenko
> Assignee: Brett Porter
> Fix For: 3.0-alpha-1
>
>
> 2.1 embedder always checks remote repositories for missing release artifacts. This is done multiple times during the same readProjectWithDependencies invocation and results in bad performance problems in embedding application (see MNGECLIPSE-523).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Work started: (MARTIFACT-25) embedder always checks missing
release artifacts
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MARTIFACT-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Work on MARTIFACT-25 started by Brett Porter.
> embedder always checks missing release artifacts
> ------------------------------------------------
>
> Key: MARTIFACT-25
> URL: http://jira.codehaus.org/browse/MARTIFACT-25
> Project: Maven Artifact
> Issue Type: Bug
> Reporter: Igor Fedorenko
> Assignee: Brett Porter
> Fix For: 3.0-alpha-1
>
>
> 2.1 embedder always checks remote repositories for missing release artifacts. This is done multiple times during the same readProjectWithDependencies invocation and results in bad performance problems in embedding application (see MNGECLIPSE-523).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MARTIFACT-25) embedder always checks missing
release artifacts
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MARTIFACT-25?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MARTIFACT-25.
---------------------------------
Resolution: Fixed
I used the method suggested by John to utilise the update check manager to track this in the local repository.
In the long run, we should certainly remove this in favour of requiring POMs in the remote repository - but it requires more work with some of the bigger repositories out there first.
> embedder always checks missing release artifacts
> ------------------------------------------------
>
> Key: MARTIFACT-25
> URL: http://jira.codehaus.org/browse/MARTIFACT-25
> Project: Maven Artifact
> Issue Type: Bug
> Reporter: Igor Fedorenko
> Assignee: Brett Porter
> Fix For: 3.0-alpha-1
>
>
> 2.1 embedder always checks remote repositories for missing release artifacts. This is done multiple times during the same readProjectWithDependencies invocation and results in bad performance problems in embedding application (see MNGECLIPSE-523).
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira