On 12/13/06, Nikunj Mehta <[EMAIL PROTECTED]> wrote:
surefire-junit. However, I need to share the patch with others in my
company as well as make the patched artifacts available for use on other
machines.
Therefore, I decided to create an internal repository to host these
patched artifacts (call it internal.plugins). I chased down the
"dragon's tail" and deployed the maven-surefire-plugin as well as
surefire (and its child) projects on this internal repository. I named
this version as 2.1-INTERNAL-r486153-pSUREFIRE-31 for surefire, and
2.3-INTERNAL-r486153-pSUREFIRE-31 for maven-surefire-plugin. All went
fine up until this point.
The trouble starts, however, when I try to use with these new artifacts
by adding internal.plugins to the pluginRepositories of my project.
Maven resolves maven-surefire-plugin as shown in the following debug
output to central:
[INFO] artifact org.apache.maven.plugins:maven-surefire-plugin: checking
for updates from internal.plugins
[INFO] artifact org.apache.maven.plugins:maven-surefire-plugin: checking
for updates from apache.snapshots
[INFO] artifact org.apache.maven.plugins:maven-surefire-plugin: checking
for updates from central
[DEBUG] maven-surefire-plugin: resolved to version
2.3-INTERNAL-r486153-pSUREFIRE-31 from repository central
[DEBUG] Trying repository central
Downloading:
http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-surefire-plugin/2.3-INTERNAL-r486153-pSUREFIRE-31/maven-surefire-plugin-2.3-INTERNAL-r486153-pSUREFIRE-31.pom
[DEBUG] Artifact not found - using stub model: Unable to locate resource
in repository
I wrote that document, but I have never seen your error before.
It is odd that the deployed version is resolving the version correctly
but incorrectly identifying the repository as central.
I have a mvn-proxy in the way (since we don't have direct internet
access) and so it could be that mvn-proxy is finding the plugin for me
even though it is attempting to access centrl.
It is interesting the mvn surefire-report:report resolves to version
2.2 and not the newer version.
I'm running mvn site now to see what is resolved, it should be the new
version since this is defined in the pom hierarchy.
I've got other things on for the next hour or so, so it will be a
little while before I have my investigation done and an answer.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
