"Morrison, John" wrote:
> > Probably. It might be a good thing to have Ant check into its CVS
> > repository. That way all new users have a template build.xml file
> > to simply fill in the details with.
> >
> > What do you think?
>
> When it's finished. I don't have any commit access to ant. Do you?
No, but I know who does :)
It should be easily downloadable though. Perhaps after we write up the
standard on Jakarta's web site we can add a link to the skeleton build.xml
file.
> > > AYW
> >
> > I'm not familiar with that one...
>
> As You Wish/Want
I see now. Thanks
> > > > > Also, did I put the property file= instructions in the
> > > > correct place and
> > > > > does Ant function as I think (ie, putting them where they
> > > > are and in the
> > > > > order they are would mean that, for example, project.name
> > > > couldn't be
> > > > > overridden...?)
> > > >
> > > > I think so. Question: doesn't the Ant shell scripts already
> > > > apply the user
> > > > properties before the build.xml file is even read?
> > >
> > > I don't know. I only know that the file can exist!
> >
> > That is true. I'll have to check the Avalon build structure.
> > I _thought_ I saw it in the ant shell scripts, but my memmory
> > could be faulty (not the first time ;P).
>
> The only thing I've found is...
>
> in ant
>
> if [ -f $HOME/.antrc ] ; then
> . $HOME/.antrc
> fi
>
> in ant.bat
>
> if exist "%HOME%\antrc_pre.bat" call "%HOME%\antrc_pre.bat"
>
> Couldn't see any reference to user properties.
You are right. I just looked at Avalon's setup, and it only has
two entries:
<property file=".ant.properties"/>
<property file="${user.home}/.ant.properties"/>
That allows a .ant.properties file in the ${base.dir} to override
properties in build.xml as well.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
