In the effective POM for my project, I have the following repositories
- apache.snapshots
- project.snapshots
- central
And I have the following plugin repositories
- internal.plugins
- apache.snapshots
- central
So, this does not have internal.plugins as a repository, only has it as a
plugin repository.
I think this should be ok.
I vaguely remember needing a normally repository for something in
addition to the plugin repo but I can't recall why that was. It
should be ok for internal_plugins to only be a plugin repo.
verify that the pom has the correct version details for the plugin
> e.g.
> <plugin>
> <artifactId>maven-surefire-report-plugin</artifactId>
> <version>2.1-INTERNAL-r485987-pMSUREFIREREP-6</version>
> </plugin>
The effective POM of my root project does not show any plugins or their
versions
If you have been tinkering with snapshots I find that they are used
before released versions so I lock down the version in the pom. YMMV.
delete the maven-surefire-report-plugin from your m2 local repo
> run mvn -X surefire-report:report > surefire-report-report.txt
>
> again delete the maven-surefire-report-plugin from your m2 local repo
> run mvn -X site > site.txt
>
> Now look at the surefire-report-report.txt, I am hoping that you will
> find that it resolves and downloads the plugin correctly from your
> internal_plugins.
Not sure if you mean surefire-report symbolically or literally. My patch has
nothing to do with maven-surefire-report-plugin. I have patched
maven-surefire-plugin and surefire-junit projects.
Ahh, I thought you were patching surefire-report, so you can run that
on the command line.
Are you running mvn site or mvn surefire? Try them both, I think
running surefire directly should work, at least it does for
surefire-report.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
