[
http://jira.codehaus.org/browse/MNG-4117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=171527#action_171527
]
Jochen Hebbrecht commented on MNG-4117:
---------------------------------------
I get it, you need 2 tags:
<repositories>
</repositories>
AND
<pluginRepositories>
</pluginRepositories>
> 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
