However, analyzing the script a bit further I figured out, that the
failing operation is actually the very last anyway. I.e. after the
creation of the DB its content is for some reason zip-ed up as a jar
which is placed into the project's home directory. I don't quite
understand what that's good for (backup of the virgin DB?) but if I
understand this correct, then this line shouldn't change anything anyway
with respect to the later running tomcat, serving data from that DB,
should it?
What I thus did was prefixing the basedir-value with the above property,
i.e.:
<target name="jarup">
<zip destfile="cosmosdb.jar"
basedir="${derby.system.home}/cosmosdb"/>
<echo message="Finished building cosmosdb"/>
</target>
And after that change I indeed got:
Buildfile:
C:\JavaDevt\org.eclipse.cosmos\data-collection\org.eclipse.cosmos.dc.local.registry\persistence_setup\build.xml
buildschema:
jarup:
[zip] Building zip:
C:\JavaDevt\org.eclipse.cosmos\data-collection\org.eclipse.cosmos.dc.local.registry\persistence_setup\cosmosdb.jar
[echo] Finished building cosmosdb
cosmosdb:
BUILD SUCCESSFUL
Total time: 4 seconds
So, can you confirm that I didn't modify the semantic here, i.e. that
this script still does what the original script has been intended to do?
Why is the freshly created DB zipped up and copied over to the project's
directory? Who or what tool is supposed to use it there?