Okay, I tried the 'ant dist' target on my box, and of course it worked fine. I suspect b/c I am on windows... Looking at the error, I'm guessing that it is some sort of parsing the path that is different between Windows and Linux.
Would it be too much of a pain for you to run the maven build and let me know if the path fails there as well? I'm not much of an expert on the differences between windows and linux unfortunantly when it comes to these path resolutions... At least if it fails in Maven and Ant then we know it isn't something funky with how the build.xml file gets generated. Any other configuration developers have ideas? Or have linux and can try it? Eric > -----Original Message----- > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] > Sent: Sunday, December 07, 2003 1:14 AM > To: Jakarta Commons Developers List; [EMAIL PROTECTED] > Subject: RE: [configuration] binary builds. > > > Quoting Eric Pugh <[EMAIL PROTECTED]>: > > > Okay, > > > > Since the project is primarily built with Maven, the > build.xml hadn't been > > updated in a while. I ran 'maven ant' and the resulting > build file works > > and is now checked in! > > > > I just tried it (CVS upate, then "ant clean dist"), and it > doesn't work for me > :-(. It still tries to run the tests as part of the "dist" > target, and fails > as follows: > > > internal-test: > [mkdir] Created dir: > /home/craigmcc/Jakarta/jakarta-commons-sandbox/configuration/t > arget/test-reports > [junit] Running > org.apache.commons.configuration.TestBaseConfiguration > [junit] Tests run: 5, Failures: 0, Errors: 0, Time > elapsed: 0.842 sec > [junit] Testsuite: > org.apache.commons.configuration.TestBaseConfiguration > [junit] Tests run: 5, Failures: 0, Errors: 0, Time > elapsed: 0.842 sec > > [junit] Testcase: testRetrieve took 0.023 sec > [junit] Testcase: testInterpolation took 0.076 sec > [junit] Testcase: testMultipleInterpolation took 0.002 sec > [junit] Testcase: testInterpolationLoop took 0 sec > [junit] Testcase: testGetString took 0.001 sec > [junit] Running > org.apache.commons.configuration.TestClassPropertiesConfiguration > [junit] Tests run: 1, Failures: 0, Errors: 1, Time > elapsed: 0.87 sec > [junit] Testsuite: > org.apache.commons.configuration.TestClassPropertiesConfiguration > [junit] Tests run: 1, Failures: 0, Errors: 1, Time > elapsed: 0.87 sec > > [junit] Testcase: testClasspathLoading took 0.119 sec > [junit] Caused an ERROR > [junit] Could not open Resource > /org/apache/commons/configuration/test.properties > [junit] java.io.FileNotFoundException: Could not open Resource > /org/apache/commons/configuration/test.properties > [junit] at > org.apache.commons.configuration.ClassPropertiesConfiguration. > getPropertyStream(ClassPropertiesConfiguration.java:179) > [junit] at > org.apache.commons.configuration.ClassPropertiesConfiguration. > <init>(ClassPropertiesConfiguration.java:108) > [junit] at > org.apache.commons.configuration.TestClassPropertiesConfigurat > ion.testClasspathLoading(TestClassPropertiesConfiguration.java:93) > [junit] at > sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > [junit] at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccess > orImpl.java:39) > [junit] at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMeth > odAccessorImpl.java:25) > > [junit] Testcase: testClasspathLoading > > BUILD FAILED > file:/home/craigmcc/Jakarta/jakarta-commons-sandbox/configurat > ion/build.xml:94: > Test > org.apache.commons.configuration.TestClassPropertiesConfigurat > ion failed > > > FWIW, I'm running this on Linux (RH 9.0) with Sun JDK 1.4.2. > > Craig > > > > > I guess I should follow up with finding out how to get Gump > building as > > well? It seems like most of the jakarta projects seem to > use Gump. And > > with the large number of dependencies that Configuration > has, it might be > > good to include it as well. I ran 'maven gump' and got a > resulting gump.xml > > that looks like what is required? > > > > Eric > > > > > -----Original Message----- > > > From: Craig R. McClanahan [mailto:[EMAIL PROTECTED] > > > Sent: Saturday, December 06, 2003 10:56 PM > > > To: Dirk Verbeeck > > > Cc: Jakarta Commons Developers List > > > Subject: Re: [configuration] binary builds. > > > > > > > > > Quoting Dirk Verbeeck <[EMAIL PROTECTED]>: > > > > > > > Craig is the man to talk to for the nightly builds. > > > > He runs the builds for jakarta-commons. > > > > > > > > > > Yep. > > > > > > > The only requirement is that ant clean dist works but you > > > also might > > > > want to change the maven generated ant file to a more > traditional > > > > build.xml file. (take the build file of commons-modeler > as example) > > > > At least make the junit tests non mandatory. > > > > > > Right now, this problem is blocking my ability to add > > > "configuration" to the set > > > of nightly builds that I run ... the fact that the unit tests > > > fail (at line 82 > > > of build.xml) blocks the creation of the binary > distribution files. > > > > > > > > > > > -- Dirk > > > > > > Craig > > > > > > > > > > --------------------------------------------------------------------- > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: > [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
