Philip Mark Donaghy wrote:
[snip]
There are a number of properties used in the etc/build.xml that are
not declared. This is preventing the target sql-execute-derby from
running. Declaring the o.a.j.is.derby and o.a.j.is.derby.embedded
properties will fix this.
This issue probably needs some testing for each database as Mikko has
pointed out it breaks the build for other databases. See related
thread "MySQL fails with Maven2.. on derby execute".
Yes, this project could desperately use a nightly multiplatform
multidatabase multimaven multicustombuild procedure. Any volunteers?
Im busy trying to do my part in putting out the 2.1 release on time.
Maybe SpikeSource will volunteer some help ...
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
