Berin Loritsch wrote: > > Didn't you use to have a target named dist-avalon-excalibur? That way > Cocoon would build from avalon-excalibur, and then the dist would use > Cocoon?
I do have a jakarta-avalon-dist to address a similar circular dependency between the framework build and cocoon, but to date I have not needed to do what you describe for excalibur. > The project definition for avalon-excalibur has been changed to use the > "dist" target which runs the DataSource testing. It has used the dist target ever since it was introduced in July. See: http://cvs.apache.org/viewcvs/jakarta-alexandria/proposal/gump/project/jakarta-avalon-excalibur.xml?rev=1.1&content-type=text/vnd.viewcvs-markup - - - Interesting excerpts from http://jakarta.apache.org/builds/gump/2001-11-29/jakarta-avalon-excalibur.html : [junit] Running org.apache.avalon.excalibur.datasource.test.DataSourceTestCase [junit] Exception in thread "main" java.lang.AbstractMethodError [junit] TEST org.apache.avalon.excalibur.datasource.test.DataSourceTestCase FAILED [junit] Tests run: 10, Failures: 0, Errors: 0, Time elapsed: 2.188 sec - - - Questions: should I specify a different target? Or is there a dependency I am missing? - Sam Ruby -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
