As the originator of this thread ;-), and much investigation
after the fabulous reponses I played with the os.* and ENTITY
structures and couldn't do what I wanted.
So, I just combined a bunch of stuff together, and re-architected
what I wanted. Now the user_env.prop contains user defined
properties (duh!) and that will be platform specific. The rest
is in the build.xml file which is generic.
The thing that kinda broke it for me was Ants inability to
define a <path> inside a <target>, or to do lazy references
to a parameterised <path>.
Cheers,
-- jon
----- Original Message -----
From: "Varnavas, Frank" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, June 07, 2001 1:13 AM
Subject: RE: Including property files
> I missed some of this thread. What was the conclusion?
>
> I had already used the <property file= > functionality to separate common
> properties from individual makefiles. I am also using <!ENTITY
> specifications to separate common xml from individual makefiles. But what I
> haven't been able to do is conditional or parameterized inclusion of the
> common xml to allow for different platform types.
>
> Since the originator of this thread specifically made reference to this sort
> of functionality, was this thread concluded with a way to do this?
>
> Also: Is there a way to specify a URL as the source of external properties?
>
> Thanks
> Frank V
>
> -----Original Message-----
> From: Jon Eaves [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, June 05, 2001 7:13 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Including property files
>
>
> Hi all,
>
> Thanks to those that replied. It appears that I should have
> read the documentation somewhat better.
>
> Mind you, the documentation is pretty poor, anybody else
> noticed that ;-)
>
> Cheers,
> -- jon
>
> PS: It's a joke. Don't reply.
>
> ----- Original Message -----
> From: "Mark Ashton" <[EMAIL PROTECTED]>
> To: <[EMAIL PROTECTED]>
> Sent: Wednesday, June 06, 2001 1:07 AM
> Subject: RE: Including property files
>
>
> > Correct me if I'm wrong, but I thought that the file attribute on property
> > had to point to a java property file, which doesn't use xml syntax. The
> ant
> > docs say:
> >
> > By setting the file attribute with the filename of the property file to
> > load. This property file has the format as defined by the file used in the
> > class java.util.Properties.
> >
> > I assume by the .xml extension on your file that these are other ant
> > buildfiles?
> >
>
>
