I've noticed that 3.0-beta-1 has different xml validation checking. For instance, it didn't complain about -- , and it did complain when one of our POMs had 2 <dependency> elements that had the same <groupId> and <artifactId>.
-Marshall On 5/18/2010 10:06 AM, Thilo Götz wrote: > No, I'm running 2.2.1. > > On 5/18/2010 15:08, Marshall Schor wrote: > >> My guess: an issue with the maven version. Are you running maven >> version 3.0-beta-1 ? >> >> -Marshall >> >> On 5/18/2010 8:36 AM, Thilo Götz wrote: >> >>> After successfully building core, I moved on to the >>> sandbox, trying to build aggregate-addons. Is that >>> correct? That gives me: >>> >>> Missing: >>> ---------- >>> 1) org.apache.uima:uima-assembly-single-project:jar:1-SNAPSHOT >>> >>> So I try to compile build/uima-assembly-single-project with >>> mvn install, which results in: >>> >>> c:\build\uima\build\uima-assembly-single-project>mvn install >>> [INFO] Scanning for projects... >>> [INFO] >>> ------------------------------------------------------------------------ >>> [ERROR] FATAL ERROR >>> [INFO] >>> ------------------------------------------------------------------------ >>> [INFO] Error building POM (may not be this project's POM). >>> >>> >>> Project ID: unknown >>> POM Location: c:\build\uima\build\uima-assembly-single-project\pom.xml >>> >>> Reason: Parse error reading POM. Reason: in comment after two dashes (--) >>> next >>> character must be > not (position: STAR >>> T_DOCUMENT seen ... - other folders per the PEAR spec at the top level\r\n >>> -- ... @31:13) for project unknown >>> at c:\build\uima\build\uima-assembly-single-project\pom.xml >>> >>> So I remove the second dash, and it builds. This is weird. Is >>> that a maven bug, do you think? >>> >>> Anyway, I'll change it. >>> >>> --Thilo >>> >>> >>> >>> > >
