>There already is: ant.file.PROJECTNAME - is there any reason why you
wouldn't want to add a name attribute to your project element?
In our project we have close to 100 ant files.. We are currently enforcing
to keep the project name same as file name so that we don't have to bother
about having 1
On 2010-04-13, Raja Nagendra Kumar wrote:
>> only possible if we have something meaningful (ant.file.SOME_GUID
>> wouldn't help anybody) and thus need the build file writer's help via
>> 's name attribute.
> This is very informative Stefan. Based on the read only nature, if the
> project name do
>only possible if we have something meaningful (ant.file.SOME_GUID
>wouldn't help anybody) and thus need the build file writer's help via
>'s name attribute.
This is very informative Stefan. Based on the read only nature, if the
project name does not exist, can the file name be considered as proj
On 2010-04-13, Raja Nagendra Kumar wrote:
> Stefan,
>> If you really want the directory that contains the build file
> Yes, I am looking for a way to reference dir that contains the build
> file. this location is different than basedir.
Take the approach described in the manual page for .
>
Stefan,
> If you really want the directory that contains the build file
Yes, I am looking for a way to reference dir that contains the build file.
this location is different than basedir.
In my case, the project does not have any name, hence as generic approach of
referring to this file would he
On 2010-04-13, Raja Nagendra Kumar wrote:
> if I use
>
>
>
>
>
> instead I want to say
>
>files="tasks/TaskDefs.xml,
> PreDefs.xm,
> CompDefs.xml"
> />
>
If your build files's location is the same as
or there seem to be need for generic referring to the directory location of
the ant script file..
some thing like
ant.dir.this or ant.dir. XYZ (if the project is named as XYZ) etc.. I would
prefer this syntax.
in similar lines to
ant.file.XYZ name as in
Are there similar thing exists pl.
--
