"Morrison, John" wrote:
>
> > > I've extended the build.xml file so that if install.dir
> > _isn't_ defined then
> > > the system displays a 'can't do' message. What do people think?
> >
> > I think a project should define a default install dir that
> > can be overridden
> > by the user's .ant.properties file.
>
> I was thinking more for the projects which don't install. The mods I made
> to the build.xml file mean that, if a install.dir isn't defined *anywhere*
> (note it's still in there, just commented out), the build.xml already has
> the functionality to say the project can't do an (un)installation.
>
> <shrug/> I thought it was a good idea ;)
Now that I have more information, I see where it might be useful. However,
if a project does not support installs, then they should simply <echo/> a
message saying something to the fact--regardless of whether ${install.dir}
is set or not.
But that's my oppinion....
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
