Community
Participate
Working Groups
Build Identifier: gemini-blueprint-1.0.0.M1 Found three errors in src/pom.xml for M1 release, when trying to build with maven 2.2 and 3.0 on MacOS X 10.6.4. These errors prevent a successful build and install of the software. All errors are related to the move of the com.springsource.bundlor.maven artifact from milestone(M6) to release status. Error 1: Referencing non-existant bundlor version. <plugin> <groupId>com.springsource.bundlor</groupId> <artifactId>com.springsource.bundlor.maven</artifactId> <version>1.0.0.M6</version> ^^^^^^^^ <= this no longer exists, 1.0.0.RELEASE seems to though. </plugin> Error 2: Trailing '/' character causes new bundlor package to not be found. <pluginRepository> <id>com.springsource.repository.bundles.release</id> <name>SpringSource Enterprise Bundle Repository - SpringSource Bundle Releases</name> <url>http://repository.springsource.com/maven/bundles/release/</url> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ backslash at end of url needs to be removed for mvn 2.2 on mac to work for some reason. </pluginRepository> Error 3: Bundlor goal "transform" not found in bundlor 1.0.0.RELEASE version <plugin> <groupId>com.springsource.bundlor</groupId> <artifactId>com.springsource.bundlor.maven</artifactId> <executions> <execution> <id>bundlor</id> <goals> <goal>transform</goal> ^^^^^^^^^^^^^^^^^^^^^^ <= needs to be changed to bundlor </goals> </execution> </executions> Reproducible: Always Steps to Reproduce: 1. Get a mac with java & maven 2. Download the gemini-blueprint 1.0.0.M1 release 3. Try to build with mvn -P equinox,it clean install
Hmm - maybe there's an issue with Maven 2.2 then. I just retried building the sources with Maven 2.0 (mentioned in the distribution readme) on a clean machine (no Maven repo) and everything builds just fine. The bundlor milestone is available at: http://repository.springsource.com/maven/bundles/milestone/com/springsource/bundlor/com.springsource.bundlor/ I'm changing the importance of this issue from bug to enhancement to see whether the problem can be fixed by upgrading bundlor and/or Maven.
I'm closing this bug since the build system will remain on Maven 2.0 (potentially migrating to Gradle rather then Maven 2.2).
Released - closing.