Details
-
Type:
Bug
-
Status:
Open
-
Priority:
Major
-
Resolution: Unresolved
-
Affects Version/s: 3.1.4 (EE only), 3.2.2 (EE only), 3.3 RC4
-
Fix Version/s: None
-
Component/s: Tools: Archetypes
-
Labels:None
-
Environment:
Maven 2.2.1, Java 1.6
-
User impact:Low
-
Log Output:
-
Similar Issues:None
Description
A Mule build with a clean repo always fails when it gets to "Test for Mule Catalog Archetype" (tests/archetypes/catalog-archetype/pom.xml).
The workaround is:
cd tools/mule-catalog-archetype
mvn install
cd ../..
And then try to build again from the top level directory.
This does not affect end-users but is incredibly annoying for developers!
I cannot for the life of me figure out why this is happening, I've tried everything I can think of and compared this archetype to all the others, no idea what the problem is. Perhaps it's just a Maven bug?