Next steps... Turning off internal.plugin proxying for mvn-proxy and trying again. That will have to wait for tomorrow.
Bingo, I can reproduce the problem that you are seeing: [INFO] artifact org.apache.maven.plugins:maven-surefire-report-plugin: checking for updates from internal.plugins [INFO] artifact org.apache.maven.plugins:maven-surefire-report-plugin: checking for updates from central [DEBUG] maven-surefire-report-plugin: resolved to version 2.1-INTERNAL-r485987-pMSUREFIREREP-6 from repository central [DEBUG] Trying repository central Downloading: http://PROXY:9999/repository/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 [DEBUG] Artifact not found - using stub model: Unable to locate resource in repository org.apache.maven.plugins:maven-surefire-report-plugin:pom:2.1-INTERNAL-r485987-pMSUREFIREREP-6 Just to ensure that the repository is available I added a profile: <profile> <id>internal</id> <repositories> <repository> <id>internal.plugins</id> <name>Maven-Proxy Repository</name> <url>http://sapolnpeapp/maven2_repositories/internal_plugins</url> <releases> <enabled>true</enabled> </releases> <snapshots> <enabled>false</enabled> </snapshots> </repository> </repositories> </profile> And ran mvn -Pinternal -X site > site-noplugin.txt But I get the same error. I can see from the debug the repository is available: [DEBUG] (f) remoteRepositories = [[internal.plugins] -> http://PROXY/maven2_repositories/internal_plugins, [apache.snapshots] -> http://people.apache.org/maven-snapshot-repository, [inhouse] -> http://PROXY/maven2_repositories/inhouse, [external_free] -> http://PROXY/maven2_repositories/external_free, [external_nonfree] -> http://PROXY/maven2_repositories/external_non_free, [inhouse_snapshot] -> http://PROXY/maven2_repositories/inhouse_snapshot, [central] -> http://repo1.maven.org/maven2] And I double checked I could browse to the location (I had a typo before) This may be a maven resolution defect, in that you can not shadow an existing plugin on a different repository. But that doesn't make sense since plugins have moved from codehaus to central before. Not sure what to do next. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
