Hi guys, didn't get to test this over the US holidays. For the CBUILDS I overload the repo during the integration test phase to isolate the tests from the internet so I can test "mvn release"... (Imagine that). The latest parent hates this... I'm using maven-invoker-plugin..
[WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequireNoRepositories failed with message: Some poms have repositories defined: org.codehaus.mojo.patch.it:it-project-parent version:1 has repositories [integration.test.remote.repo]Mojo is syncronized with repo1.maven.org. The rules for repo1.maven.org are that pom.xml files should not include repository definitions. If repository definitions are included, they must be limited to SNAPSHOT only repositories. [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ 1) Is there a way to to say "stuff it" to the rule during integration test phase? That way I can keep current with the parent. 2) What is the issue with overloading/specifying repos in the POM? Thanks, Lee ________________________________ From: Benjamin Bentmann <[email protected]> To: Mojo Developer List <[email protected]> Sent: Sat, November 21, 2009 11:08:15 AM Subject: [mojo-dev] [VOTE] Release Mojo Parent POM 23 Hi, apart from the usual plugin version updates, the new parent provides a) an enforcer rule to help preventing repos in the POM and b) a profile "mojo-release" to produce a complete source distro Complete overview of changes since last release: http://fisheye.codehaus.org/browse/mojo/trunk/mojo/mojo-parent/pom.xml?r1=10743&r2=11290 An up-to-date snapshot is deployed. [ ] +1 [ ] 0 [ ] -1 The vote is open for 72 hours and will succeed by lazy consensus. Benjamin --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
