Understandable. If you're worried about polluting the repo with suspect artifacts you can run mvn build-helper:remove-project-artifact to remove them afterwards. Just a suggestion.
On Wed, Sep 21, 2011 at 12:12 AM, Doug Cutting <[email protected]> wrote: > On 09/20/2011 04:09 PM, Stephen Gargan wrote: > > Its very curious that the build could not find the maven plugin. I've > just > > made a clean checkout with the patch and the 'mvn verify' goal ran fine. > Do > > you have a copy of the plugin in your local repo? > > No, I do not have a copy in my local repo. > > > Generating the sample project as part of the build references the > > maven-plugin. I'm thinking that the archetype plugin must fork a new > maven > > build for the sample and its this build that needs the plugin installed. > > Without the jar in the local repo neither the 'integration-test' or > 'verify' > > goals will succeed. The 'test' goal will pass because the sample project > is > > not generated or built and tying the generation to this phase will still > > fail without the maven-plugin installed locally. > > > > You should not have any issues running the install goal, its the default > > goal I usually run for maven builds; are you experiencing problems? If > you > > prefer not to I can remove the the integration testing from the build. > Let > > me know. > > Install works fine, but I prefer not to use it when testing patches. > > Doug >
