RE: Defining task-specific properties - what "namespace" should I use?

[Jose Alberto Fernandez <JF...@viquity.com>]

I really think that will not solve much.
If I have to give <jikes> options for <javac> why don't
just have a separate task for <jikes> than for <javac>?
I mean, will we expect that each user has to change his/her
copy of build.xml to make it suit their own build environment?

As people said before what is needed is a general mechanism for
configuring tasks. Some way to say "all my <javac>s should use
jikes and this options. A different user may indicate that all
their <javac>s should use modern compile and these other options.
All that without modifing the build.xml file.

Some XSLT style that ANT would apply automatically may probably do
that. But is has to work as transparently as the current property
definitions. And if no file is provided the appropriate default 
behaviour should work.

Jose Alberto

> -----Original Message-----
> From: Stefan Bodewig [mailto:bodewig@bost.de]
> Sent: Thursday, September 14, 2000 12:36 AM
> To: ant-dev@jakarta.apache.org
> Subject: Re: Defining task-specific properties - what 
> "namespace" should
> I use?
> 
> 
> >>>>> "NS" == Nico Seessle <ni...@seessle.de> writes:
> 
>  NS> Javac (jikes) uses some properties to set options which
>  NS> are available only to jikes and not the other compilers.
> 
> Yes and I'd really like to take it a very different approach to
> it. I've been kicking around this idea for quite some time now, how
> about
> 
> <javac ..>
>   <jikes pedantic="no" emacs="yes" />
> </javac>
> 
> which would be ignored if using a different compiler than jikes.
> 
> Would an approach like this fit your needs?
> 
> I know it has some limitations if compared to a CSS based approach -
> even compared to the property approach we currently take. 
> 
> Most notably I can easily setup my environment to always call Ant
> with -Dbuild.compiler.emacs=true now, while I'd need to ensure every
> build file has a <jikes> element nested into every <javac> with the
> appropriate setting of the emacs attribute to achieve the same effect.
> 
> Stefan
>