Hi Felipe,
>From your email, I realized that I use the wrong files to patch last time
:(, I will redo this.
While Vincent hasn't replied yet and to save your time, in the last test of
release, I added the tag in build-common.xml
<property name="cargo.jar.name" value="cargo-0.5"/>
And in build.xml under samples/servlet
<filter token="cargo.jar.name" value="$cargo.jar.name}.jar/>
I got away with the evaluation of the ${cargo.jar.name}.
I'm not sure how Vincent does this, and not sure the above help you.
--Xuan
-----Original Message-----
From: Felipe Leme [mailto:[EMAIL PROTECTED]
Sent: Wednesday, 20 July 2005 1:52 PM
To: Cactus Developers List
Subject: Re: CACTUS_17_BRANCH created
Vincent,
I added cargo properties in most of the required places, but couldn't
figure it out how to evaluate the ${cargo.jar.name} property on the
sample's build.xml; it's generated as:
<property name="cargo.jar"
location="../../lib/${cargo.jar.name}"/>
instead of:
<property name="cargo.jar"
location="../../lib/cargo-0.5.jar"/>
Do you know where is it set?
Thanks,
-- Felipe
Vincent Massol wrote:
> I ran it from the build but you're right, the real test is to run it
> from the release zips as it can uncover issues as the one you've fixed
> (the missing cargo jar in the distribution).
---------------------------------------------------------------------
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]
