You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jochen Hebbrecht (JIRA)" <ji...@codehaus.org> on 2009/03/30 10:56:12 UTC
[jira] Issue Comment Edited: (MNG-4117) PluginNotFoundException:
Plugin could not be found in internal repository
[ http://jira.codehaus.org/browse/MNG-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171372#action_171372 ]
Jochen Hebbrecht edited comment on MNG-4117 at 3/30/09 3:55 AM:
----------------------------------------------------------------
When I add this to my setting.xml
<mirrors>
<mirror>
<id>archiva.internal</id>
<url>http://mavenrepo.MYCOMPANY.be:8080/archiva/repository/internal</url>
<mirrorOf>central</mirrorOf>
</mirror>
... I'm able to download the plugin!
So when there are multiple repositories available, it fails :-(
was (Author: jochus):
When I add this to my setting.xml
<mirrors>
<mirror>
<id>archiva.internal</id>
<url>http://mavenrepo.rmg.be:8080/archiva/repository/internal</url>
<mirrorOf>central</mirrorOf>
</mirror>
... I'm able to download the plugin!
So when there are multiple repositories available, it fails :-(
> PluginNotFoundException: Plugin could not be found in internal repository
> -------------------------------------------------------------------------
>
> Key: MNG-4117
> URL: http://jira.codehaus.org/browse/MNG-4117
> Project: Maven 2
> Issue Type: Bug
> Affects Versions: 2.1.0
> Environment: windows xp sp3
> Reporter: Jochen Hebbrecht
> Attachments: error.log
>
>
> Hi,
> I'm having a strange problem with a maven-plugin. I'm not sure this is a bug, it could be an incorrect configuration at my side too.
> We use Archiva as an internal repository and in that repository, we stored a custom maven-plugin (it's a fork on the maven-jdev-plugin, but it can only be used in our company, so we're not reflecting it to the open source community). But when we want to retreive the maven-plugin, we get the following error (check the attachment: error.log).
> You can actually see him retreiving the POM file from Archiva, and it tells me: "Artifact resolved". But then I tries to download the JAR file from repo1.maven.org, which isn't there of course and it never checks our internal repository again :-(.
> Any idea's what is going wrong here? Why does MVN download the POM from Archiva, but not the JAR?
> Regards,
> Jochen
--
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