Hi folks... This is also related to Mark's and Mikko's email thread " Resolved the Maven 2 build error with the Derby embedded database"...
>From http://ant.apache.org/manual/index.html : Ant will only check whether the property has been set, the value doesn't matter. A property set to the empty string is still an existing property. For example: <target name="build-module-A" if="module-A-present"/> <target name="build-own-fake-module-A" unless="module-A-present"/> In the first example, if the module-A-present property is set (to any value, e.g. false), the target will be run. In the second example, if the module-A-present property is set (again, to any value), the target will not be run. Having said that, setting the property below is not what we should do, since it would (let me get rid of the conditional - it does) break everything else since now the build file thinks that derby is always set. Mark is right in that the property needs to be set for derby (to anything for that matter) and only if derby is the database, but we need to find out why the condition to do so doesn't get executed Hajo Birthelmer [EMAIL PROTECTED] office : +01.707.773.4646 cell : +01.707.318.9275 -----Original Message----- From: Philip Mark Donaghy [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 24, 2007 3:32 PM To: Jetspeed Developers List Subject: Resolved the Maven 2 build error with the Derby embedded database Hi, It seems the maven ant plugin requires that properties be declared in the build file to be acknowledged. Example, <target name="help" if="mytest"> The property mytest doesn't need to be declared when running this target with Ant. The command, ant -Dmytest=true help will execute the target help. Yet the target help will never execute using the maven plugin unless there is a property declaration. <property name="mytest" value=""/> 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. <property name="org.apache.jetspeed.database.is.derby" value="" /> <property name="org.apache.jetspeed.database.is.derby.embedded" value="" /> This and copying the derby jar to tomcat are blocking the maven 2 build. At the moment I don't know where that should be done. -- Philip Donaghy donaghy.blogspot.com del.icio.us/donaghy/philip Skype: philipmarkdonaghy Office: +33 5 56 60 88 02 Mobile: +33 6 20 83 22 62 --------------------------------------------------------------------- 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]
