You are right that properties in ant once set are not modified. If you
look carefully the values that depend on any value are commented out in
build.properties - uncommenting them in your local copy will accomplish
exactly what is meant.
Also notice the order in which the properties are read:
: Geoff Howard [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 21, 2003 2:58 PM
To: [EMAIL PROTECTED]
Subject: RE: I may be wrong but...
You are right that properties in ant once set are not modified. If you
look carefully the values that depend on any value are commented out in
build.properties
: RE: I may be wrong but...
In the latest code (tip) that I brought down from cvs today, the exclude
properties are _not_ commented out in the build.properties file. It was
necessary for me to edit this file and comment them out.
Is it the case that I shouldn't be bringing down the tip
it and
it works fine. I'll just go with that.
Thanks for your help.
-Original Message-
From: Geoff Howard [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 21, 2003 3:39 PM
To: [EMAIL PROTECTED]
Subject: RE: I may be wrong but...
We're either looking at different files or you are misunderstanding
[mailto:[EMAIL PROTECTED]
Sent: Saturday, June 21, 2003 3:32 PM
To: [EMAIL PROTECTED]
Subject: RE: I may be wrong but...
I downloaded xml-cocoon2 from cvs to my local file system today. The tip
revision of build.properties that came to my system, (rev 1.15) reads as
follows
.
Thanks again.
-Original Message-
From: Geoff Howard [mailto:[EMAIL PROTECTED]
Sent: Saturday, June 21, 2003 5:52 PM
To: [EMAIL PROTECTED]
Subject: RE: I may be wrong but...
You are working with the wrong repository. They were switched around a few
months ago and the soft links between
