|
|
Re: XMLC CVS Update: msg#00033
java.enhydra.xmlc
|
Subject: |
Re: XMLC CVS Update |
Did you try Ant-1.5.1. There was a pretty major bug in Ant-1.5
which made the Barracuda contrib build bomb so the current CVS for
Barracuda currently supports Ant-1.5.1 or greater. It had something
to do with calling <ant ....> and I know that the XMLC build does
lots of that. I highly suggest upgrading. Also, I'd document
the version of Ant needed rather than store it in CVS. We used to
do that with Barracuda, but since almost everyone has Ant already
installed, that is kind of pointless. Just say which version of Ant
is supported by your build system and people will just use that version
(or better) of Ant if they want to build XMLC.
Jake
At 02:53 PM 10/29/2002 +0900, you wrote:
OK, now I remember why I have the
script: to make sure right version of Ant is used.
In my system setup, I have Ant 1.5 as default and the version of Ant
included in release/lib is 1.4.1. I am having problem compiling XMLC with
1.5.
David
On Tuesday, Oct 29, 2002, at 14:35 Asia/Tokyo, Jacob Kjome wrote:
Why a build.sh? Ant is
already started via a shell script and you can set up all your classpaths
and other environment settings using build.xml and properties files
without needing an additional shell script or is this for something else?
Jake
At 01:02 PM 10/29/2002 +0900, you wrote:
Hi,
There are some update to the CVS over the weekend. Richard has
committed the new XMLC dynamic reloading codes.
I have added a build.sh and move the build time jars to
release/build-lib in the CVS. I have tested this on Mac OS X. If you test
this out on other platforms, please let me know if it works for you.
Thanks.
David Li
_______________________________________________
XMLC mailing list
XMLC@xxxxxxxxxxx
http://www.enhydra.org/mailman/listinfo.cgi/xmlc
</blockquote></x-html>
| |