Benson, Why would we use Maven 3, knowing that Hudson doesn't support it and that XmlSchema builds fine with Maven 2?
Andreas On Sat, Jan 22, 2011 at 21:06, Apache Hudson Server <[email protected]> wrote: > See <https://hudson.apache.org/hudson/job/xmlschema-new-trunk-jdk15/6/changes> > > Changes: > > [veithen] Fixed an issue in SchemaBuilder that prevented it from resolving > imports without schemaLocation, but for which a schema has been registered > using XmlSchemaCollection#getKnownNamespaceMap(). > > ------------------------------------------ > Started by an SCM change > Building remotely on ubuntu2 > Updating https://svn.apache.org/repos/asf/webservices/xmlschema/trunk > U xmlschema-core/src/test/java/tests/ImportTest.java > A xmlschema-core/src/test/resources/xml.xsd > A xmlschema-core/src/test/resources/knownNamespace.xsd > U > xmlschema-core/src/main/java/org/apache/ws/commons/schema/SchemaBuilder.java > At revision 1062249 > [xmlschema-new-trunk-jdk15] $ /bin/bash -xe /tmp/hudson4164742453256892038.sh > + cd trunk > + /home/hudson/hudson-slave/tools/Maven_3.0/apache-maven-3.0/bin/mvn clean > deploy > /tmp/hudson4164742453256892038.sh: line 2: > /home/hudson/hudson-slave/tools/Maven_3.0/apache-maven-3.0/bin/mvn: No such > file or directory > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
