Shash:
> By using the "uptodate" task instead of "available", and putting an
> "unless" check in the build task directly in build-common.xml, I can
> get it to work. The only problem is keel-core and keel-server, because
> the JAR names are expanding to keel-keel-core.2.0.jar and
> keel-keel-server-2.0.jar (extra keel- prefix).
Hmm, interesting. The dependset stuff I have is basically supposed to remove the .jar
file if anything has changed in the module. Then the available checks if the jar is
there or not. Same principal I guess.
> Unless you are also working on it, I can do some more tests and check
> in....I also need to read up and learn on the depnedsets you have
> there. The uptodate I used looks like:
>
> <uptodate property="build.notRequired"
> targetfile="${keel-sub.build}/lib/${keel-sub.jar.name}.jar" >
> <srcfiles dir= "${keel-sub.src}" includes="**/*.java"/>
> </uptodate>
That would do it for the Java files, but not for any conf changes, etc. But it's
cleaner than the way I'm doing it now! I've got it in pieces a bit, so maybe give me a
few minutes and see if I can get it sorted out - if not, I'd be happy to pass the buck
:-)
Michael Nash
JGlobal Ltd.
http://www.jglobal.com
Bahamas Commerce and Trade
http://www.bahamascommerce.com
http://keelframework.org/documentation
Keelgroup mailing list
[EMAIL PROTECTED]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
