Stefan Bodewig wrote:
On Thu, 13 Oct 2005, Peter Reilly <[EMAIL PROTECTED]> wrote:
Can you point out where you have seen this reference so that it can
be modified.
I trusted Steve's writing 8-)
I trusted Stefan's reviewing of my writing :)
---
Kev Jackson wrote:
OK. they were tail first, and I have stated that fact both in the
draft and in the big projects chapter of the second edition of Java
development with Ant. Which means that I have bit of editing to do on
the CVS-managed copies of that chapter. I've been trying to finish
On Thu, 13 Oct 2005, Peter Reilly <[EMAIL PROTECTED]> wrote:
> Can you point out where you have seen this reference so that it can
> be modified.
I trusted Steve's writing 8-)
Stefan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
OK. they were tail first, and I have stated that fact both in the
draft and in the big projects chapter of the second edition of Java
development with Ant. Which means that I have bit of editing to do on
the CVS-managed copies of that chapter. I've been trying to finish
that chapter since a
Kev Jackson wrote:
Peter Reilly wrote:
At one stage, the import task behaved as if
it was added at the end of the build file. This was an
unexpected consequence (bug!) of the initial implementation.
This was changed (I think) in 1.6.1 or 1.6.2, so that the import behaved
as if it was inline. I
On 10/13/05, Peter Reilly <[EMAIL PROTECTED]> wrote:
> At one stage, the import task behaved as if
> it was added at the end of the build file. This was an
> unexpected consequence (bug!) of the initial implementation.
> This was changed (I think) in 1.6.1 or 1.6.2, so that the import behaved
> as
Peter Reilly wrote:
At one stage, the import task behaved as if
it was added at the end of the build file. This was an
unexpected consequence (bug!) of the initial implementation.
This was changed (I think) in 1.6.1 or 1.6.2, so that the import behaved
as if it was inline. I have just checked th
Peter Reilly wrote:
At one stage, the import task behaved as if
it was added at the end of the build file. This was an
unexpected consequence (bug!) of the initial implementation.
This was changed (I think) in 1.6.1 or 1.6.2, so that the import behaved
as if it was inline. I have just checked the
At one stage, the import task behaved as if
it was added at the end of the build file. This was an
unexpected consequence (bug!) of the initial implementation.
This was changed (I think) in 1.6.1 or 1.6.2, so that the import behaved
as if it was inline. I have just checked the manual for the
task
Stefan Bodewig wrote:
On Thu, 13 Oct 2005, Kev Jackson <[EMAIL PROTECTED]> wrote:
However if I try to run the project buildfile (./build.xml), none of
the properties are available (quick checks with echo just give me
variables instead of expanded properties).
This is not what I've se
On Thu, 13 Oct 2005, Kev Jackson <[EMAIL PROTECTED]> wrote:
> Yes the properties file is being loaded (just rechecked now). It
> seems to be a problem if I reference a property from the common
> properties file within the project specific file.
Hmm, may it just be the order in which files are lo
Stefan Bodewig wrote:
On Thu, 13 Oct 2005, Kev Jackson <[EMAIL PROTECTED]> wrote:
However if I try to run the project buildfile (./build.xml), none of
the properties are available (quick checks with echo just give me
variables instead of expanded properties).
This is not what I've se
On Thu, 13 Oct 2005, Kev Jackson <[EMAIL PROTECTED]> wrote:
> However if I try to run the project buildfile (./build.xml), none of
> the properties are available (quick checks with echo just give me
> variables instead of expanded properties).
This is not what I've seen in the past. Properties d
Hi all,
I'm trying to refactor a build file we have here into a commonly used
set of targets and then project specifc targets. Here's my directory setup
./common/build.xml
./common/build.properties
./build.xml (shown below)
Now in the common/build.xml I use the property file tag to read in
14 matches
Mail list logo
