You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Kenney Westerhof (JIRA)" <ji...@codehaus.org> on 2005/09/05 13:31:02 UTC
[jira] Created: (MNG-836) plugin dependencies cannot be resolved when repository has same .
plugin dependencies cannot be resolved when repository has same <id>.
---------------------------------------------------------------------
Key: MNG-836
URL: http://jira.codehaus.org/browse/MNG-836
Project: Maven 2
Type: Bug
Versions: 2.0-beta-1
Reporter: Kenney Westerhof
Assigned to: Kenney Westerhof
Try: deleting ~/.m2/repository/org/codehaus and then build maven-model.
Since the snapshots id is used on both the normal and the plugin repositories,
maven-modello-plugin's dependencies cannot be resolved. Maven-modello-plugin
comes from snapshots..../plugins/ and it's dependencies are in snapshots..../.
Renaming the pluginRepository with id snapshots to something else fixes this,
but there seems to be a mixup in plugin repo's and artifact repo's.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Updated: (MNG-836) plugin dependencies cannot be resolved
Posted by "Kenney Westerhof (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-836?page=all ]
Kenney Westerhof updated MNG-836:
---------------------------------
Description:
Try: deleting ~/.m2/repository/org/codehaus and then build maven-model.
Somehow plugin dependencies are not resolved; weird that this doesn't occur more often.
This is because in DefaultPluginManager the verifyPlugin method calls checkRequiredMavenVersion
with just the PluginArtifactRepositories. The checkRequiredMavenVersion resolves the plugin and/or
its dependencies but does not have access to the normal artifact repositories, so only plugin repositories
can be searched for the plugin's dependencies.
Modified the verifyPlugin method to add the RemoteArtifactRepositories to the list.
was:
Try: deleting ~/.m2/repository/org/codehaus and then build maven-model.
Since the snapshots id is used on both the normal and the plugin repositories,
maven-modello-plugin's dependencies cannot be resolved. Maven-modello-plugin
comes from snapshots..../plugins/ and it's dependencies are in snapshots..../.
Renaming the pluginRepository with id snapshots to something else fixes this,
but there seems to be a mixup in plugin repo's and artifact repo's.
Fix Version: 2.0-beta-1
Component: maven-core
Remaining Estimate: 1 hour
Original Estimate: 3600
Summary: plugin dependencies cannot be resolved (was: plugin dependencies cannot be resolved when repository has same <id>.)
First I thought this was because of a duplicate repository <id>; changing it fixed it. But I couldn't
reproduce it again, and after fixing it it was something else; so I renamed this issue.
> plugin dependencies cannot be resolved
> --------------------------------------
>
> Key: MNG-836
> URL: http://jira.codehaus.org/browse/MNG-836
> Project: Maven 2
> Type: Bug
> Components: maven-core
> Versions: 2.0-beta-1
> Reporter: Kenney Westerhof
> Assignee: Kenney Westerhof
> Fix For: 2.0-beta-1
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> Try: deleting ~/.m2/repository/org/codehaus and then build maven-model.
> Somehow plugin dependencies are not resolved; weird that this doesn't occur more often.
> This is because in DefaultPluginManager the verifyPlugin method calls checkRequiredMavenVersion
> with just the PluginArtifactRepositories. The checkRequiredMavenVersion resolves the plugin and/or
> its dependencies but does not have access to the normal artifact repositories, so only plugin repositories
> can be searched for the plugin's dependencies.
> Modified the verifyPlugin method to add the RemoteArtifactRepositories to the list.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-836) plugin dependencies cannot be resolved
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-836?page=comments#action_46260 ]
Brett Porter commented on MNG-836:
----------------------------------
we're presently back to where we were, but the above can be used to form a test case
> plugin dependencies cannot be resolved
> --------------------------------------
>
> Key: MNG-836
> URL: http://jira.codehaus.org/browse/MNG-836
> Project: Maven 2
> Type: Bug
> Components: maven-core
> Versions: 2.0-beta-1
> Reporter: Kenney Westerhof
> Assignee: Brett Porter
> Fix For: 2.0-beta-1
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> Try: deleting ~/.m2/repository/org/codehaus and then build maven-model.
> Somehow plugin dependencies are not resolved; weird that this doesn't occur more often.
> This is because in DefaultPluginManager the verifyPlugin method calls checkRequiredMavenVersion
> with just the PluginArtifactRepositories. The checkRequiredMavenVersion resolves the plugin and/or
> its dependencies but does not have access to the normal artifact repositories, so only plugin repositories
> can be searched for the plugin's dependencies.
> Modified the verifyPlugin method to add the RemoteArtifactRepositories to the list.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-836) plugin dependencies cannot be resolved
Posted by "Kenney Westerhof (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-836?page=comments#action_46280 ]
Kenney Westerhof commented on MNG-836:
--------------------------------------
I fixed this in r278736, 2005-09-05...
> plugin dependencies cannot be resolved
> --------------------------------------
>
> Key: MNG-836
> URL: http://jira.codehaus.org/browse/MNG-836
> Project: Maven 2
> Type: Bug
> Components: maven-core
> Versions: 2.0-beta-1
> Reporter: Kenney Westerhof
> Assignee: Brett Porter
> Fix For: 2.0-beta-1
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> Try: deleting ~/.m2/repository/org/codehaus and then build maven-model.
> Somehow plugin dependencies are not resolved; weird that this doesn't occur more often.
> This is because in DefaultPluginManager the verifyPlugin method calls checkRequiredMavenVersion
> with just the PluginArtifactRepositories. The checkRequiredMavenVersion resolves the plugin and/or
> its dependencies but does not have access to the normal artifact repositories, so only plugin repositories
> can be searched for the plugin's dependencies.
> Modified the verifyPlugin method to add the RemoteArtifactRepositories to the list.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Commented: (MNG-836) plugin dependencies cannot be resolved
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-836?page=comments#action_46235 ]
John Casey commented on MNG-836:
--------------------------------
Do we have a test to prevent this regression in future, or are we no better off than before??
> plugin dependencies cannot be resolved
> --------------------------------------
>
> Key: MNG-836
> URL: http://jira.codehaus.org/browse/MNG-836
> Project: Maven 2
> Type: Bug
> Components: maven-core
> Versions: 2.0-beta-1
> Reporter: Kenney Westerhof
> Assignee: Brett Porter
> Fix For: 2.0-beta-1
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> Try: deleting ~/.m2/repository/org/codehaus and then build maven-model.
> Somehow plugin dependencies are not resolved; weird that this doesn't occur more often.
> This is because in DefaultPluginManager the verifyPlugin method calls checkRequiredMavenVersion
> with just the PluginArtifactRepositories. The checkRequiredMavenVersion resolves the plugin and/or
> its dependencies but does not have access to the normal artifact repositories, so only plugin repositories
> can be searched for the plugin's dependencies.
> Modified the verifyPlugin method to add the RemoteArtifactRepositories to the list.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
[jira] Closed: (MNG-836) plugin dependencies cannot be resolved
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-836?page=all ]
Brett Porter closed MNG-836:
----------------------------
Resolution: Fixed
was a regression caused by MNG-757, rolled back
> plugin dependencies cannot be resolved
> --------------------------------------
>
> Key: MNG-836
> URL: http://jira.codehaus.org/browse/MNG-836
> Project: Maven 2
> Type: Bug
> Components: maven-core
> Versions: 2.0-beta-1
> Reporter: Kenney Westerhof
> Assignee: Brett Porter
> Fix For: 2.0-beta-1
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> Try: deleting ~/.m2/repository/org/codehaus and then build maven-model.
> Somehow plugin dependencies are not resolved; weird that this doesn't occur more often.
> This is because in DefaultPluginManager the verifyPlugin method calls checkRequiredMavenVersion
> with just the PluginArtifactRepositories. The checkRequiredMavenVersion resolves the plugin and/or
> its dependencies but does not have access to the normal artifact repositories, so only plugin repositories
> can be searched for the plugin's dependencies.
> Modified the verifyPlugin method to add the RemoteArtifactRepositories to the list.
--
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org