What version did you give your modified maven-surefire-plugin?
When creating locally modified versions of plugins, it's a very good idea (best practice???) to give them a very clear/specific version that differentiates them from the "main" versions. For example, if your surefire modifications were based on plugin version 2.2, you might use a version like 2.2-MYCOMPANY-R1, or 2.2-MYCOMPANY-SNAPSHOT. Then add the plugin as a dependency in the pom with your version. HTH, Doug On 8/25/06, Maria Odea Ching <[EMAIL PROTECTED]> wrote:
Hi Gergely, Have you tried executing mvn install with -U to update the plugins for the project? e.g. mvn install -U Hope this helps :-) Thanks, Odea Gergely Szakály wrote: >Hi all, > >I made a modification to the surefire plugin for use in our project >(to modify the classloading order). I installed the plugin to our >company Maven repository. The surprise: when running Maven, Maven >recognises the new version of the plugin, the JAR file of the patched >plugin is downloaded to the local repository, but the POM file is >not. Consequently the build fails. > >On the other hand: > >If I download the POM file manually to the local repository, the >plugin starts working. > >If I add the plugin artifact to my Maven project as a dependency and >execute 'mvn compile', the same POM file *does get downloaded* and >the plugin starts working!!!! If I execute 'mvn install' instead 'mvn >compile', the POM is *not* downloaded. > >Any idea? > >Gergely > >__________________________________________________ >Do You Yahoo!? >Tired of spam? Yahoo! Mail has the best spam protection around >http://mail.yahoo.com > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
