> The trouble starts, however, when I try to use 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
For those looking for a workaround, physically copying the patch artifact POM manually to the patch artifact folder of the local repository for the initially referenced project, in this case maven-surefire-plugin/2.3-INTERNAL-r486153-pSUREFIRE-31/maven- surefire-plugin-2.3-INTERNAL-r486153-pSUREFIRE-31.pom will get the build rolling. And once done, the patch continues to work.
