Gavin wrote: > >> -----Original Message----- >> From: Robert Burrell Donkin [mailto:[email protected]] >> Sent: Thursday, 28 May 2009 4:36 PM >> To: [email protected] >> Subject: Re: building rat... >> >> scott comer wrote: >>> maybe you know better than me, but i see something: >>> >>> [INFO] [site:attach-descriptor] >>> [INFO] Unable to load parent project from a relative path: Could not >>> find the model file 'C:\wks\pom.xml'. for project unknown >>> [INFO] Parent project loaded from repository. >> maven seems to complain of this a lot. usually doesn't seem to matter. >> (hard to tell for sure without running at debug.) >> >>> allTests: >>> [au:antunit] Build File: >>> C:\wks\rat\apache-rat-tasks\src\test\resources\antunit\report-normal- >> operation.xml >>> [au:antunit] Tests run: 3, Failures: 0, Errors: 1, Time elapsed: 0.703 >> sec >>> [au:antunit] Target: testCustomMatcherSentToFile caused an ERROR >>> [au:antunit] at line 173, column 43 >>> [au:antunit] Message: Unable to find a javac compiler; >>> [au:antunit] com.sun.tools.javac.Main is not on the classpath. >>> [au:antunit] Perhaps JAVA_HOME does not point to the JDK. >>> [au:antunit] It is currently set to "C:\Program >> Files\Java\jdk1.6.0_11\jre" >>> >>> (note, my environment variable JAVA_HOME is set to C:\Program >>> Files\Java\jdk1.6.0_11. who put \jre on the end?) >> maven did >> >> when something goes wrong, i find maven is often cryptic. the only way i >> can debug a maven build is to run with debug on. > > FWIW, Buildbot reports the same errors as Scott [1] and now fails since I > added the assembly:assembly step. > > [1] - http://ci.apache.org/builders/rat_trunk/builds/48 > > Running it with --debug gives it this output : > > http://ci.apache.org/builders/rat_trunk/builds/50/steps/compile/logs/stdio > > Hopefully that will help. > Let me know please if Buildbot can do other tests for the project. > > For now I will leave assembly:assembly and --debug turned on in Buildbot, so > any new commits to Rat project will see failure reports come to this list > until such a time as the problems are solved or you tell me to alter the > tests once more :)
rat is a multiple module project that uses a combined inherited and aggregated top level pom. so, i would expect running 'assembly:assembly' at top level to fail. - robert
