maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nikunj Mehta" <nrmeht...@gmail.com>
Subject Re: Patched artifacts resolved incorrectly from internal repository
Date Wed, 13 Dec 2006 23:18:22 GMT
Now I am a little confused

On 12/13/06, Barrie Treloar <baerrach@gmail.com> wrote:
>
> Just to re-iterate, since my env has changed a bit in debugging.
>
> I have re-run surefire-report:report with no plugin installed and it
> correctly resolves to internal_plugins, so it looks like mvn site is
> resolving incorrectly.
>
> [DEBUG] Trying repository internal_plugins
> Downloading:
> http://PROXY/maven2_repositories/internal_plugins/org/apache/maven/plugins/maven-surefire-report-plugin/2.1-INTERNAL-r485987-pMSUREFIREREP-6/maven-surefire-report-plugin-2.1-INTERNAL-r485987-pMSUREFIREREP-6.pom
> 1/1K
> 1K downloaded
> [DEBUG]   Artifact resolved
> [DEBUG] Retrieving parent-POM:
> org.apache.maven.plugins:maven-plugins::4 for project:
> null:maven-surefire-report-plugin:maven-plugin:
> 2.1-INTERNAL-r485987-pMSUREFIREREP-6
> from the repository.
> ...
>
This means the POM is correctly resolved, which seems to be a problem in my
case. In an earlier email, you said

> From the logs you can see that the version number is being correctly
> identified as the internal version, but then central is incorrectly
> being contacted.
>

Are these two things consistent? Appreciate your looking in to this!

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message