You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Kev Jackson <ke...@it.fts-vn.com> on 2005/01/25 04:40:52 UTC
Proposal
Hi,
I'm working on a project right now with real neophyte developers, and
one of the things I'm constantly having to do is to unset classpaths.
They keep installing crappy software that sets a classpath variable
(Oracle client being the main culprit here) and then when they use the
project build file, it falls over because of alien jars on the classpath
(not Ant's fault or anything).
I'm sure that this is a commonplace occurence, so I propose the following...
On the website (ant.apache.org), in bold letters across the front page
"PLEASE FOR THE LOVE OF $DEITY, UNSET YOUR CLASSPATH BEFORE RUNNING ANT!!"
or if not on the front page, at least in the manual section. I'm even
willing to add the documentation to the xdocs or html
Also I think it'd be a good idea to print this out when simply typing
"ant" at the command line - not just "build.xml does not exist"
Sorry, rant off
Kev
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Proposal
Posted by Stefan Bodewig <bo...@apache.org>.
On Tue, 25 Jan 2005, Steve Loughran <st...@apache.org> wrote:
> ant -noclasspath does what youwant
>
> we could be brutal and make that the default. That is, from ant1.7+
> we ignore the classpath unless you request otherwise.
Will break too many builds, sorry.
Stefan
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Proposal
Posted by Peter Reilly <pe...@apache.org>.
Kev Jackson wrote:
> Matt Benson wrote:
>
>> --- Steve Loughran <st...@apache.org> wrote:
>> [SNIP]
>>
>>
>>> ant -noclasspath does what youwant
>>>
>>> we could be brutal and make that the default. That
>>> is, from ant1.7+ we ignore the classpath unless you request otherwise.
>>> We say it was too much a source of trouble and leave it at that. Add a
>>> -classpath option for backwards compat; all is well.
>>>
>>> -steve
>>>
>>
>>
>> I like it.
>>
>> -Matt
>>
>>
> This is exactly what I'd like to happen - would it be possible to make
> this the default (please)?
I do not think so. I do not know how many times I have seen, on weblogs
and lists, people stating
how to add something to a CLASSPATH to get some ant script working.
Making -noclasspath the default would break a LOT of current scripts.
>
> Kev
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Proposal
Posted by Kev Jackson <ke...@it.fts-vn.com>.
Matt Benson wrote:
>--- Steve Loughran <st...@apache.org> wrote:
>[SNIP]
>
>
>>ant -noclasspath does what youwant
>>
>>we could be brutal and make that the default. That
>>is, from ant1.7+ we
>>ignore the classpath unless you request otherwise.
>>We say it was too
>>much a source of trouble and leave it at that. Add a
>>-classpath option
>>for backwards compat; all is well.
>>
>>-steve
>>
>>
>
>I like it.
>
>-Matt
>
>
This is exactly what I'd like to happen - would it be possible to make
this the default (please)?
Kev
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Proposal
Posted by Matt Benson <gu...@yahoo.com>.
--- Steve Loughran <st...@apache.org> wrote:
[SNIP]
> ant -noclasspath does what youwant
>
> we could be brutal and make that the default. That
> is, from ant1.7+ we
> ignore the classpath unless you request otherwise.
> We say it was too
> much a source of trouble and leave it at that. Add a
> -classpath option
> for backwards compat; all is well.
>
> -steve
I like it.
-Matt
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Proposal
Posted by Steve Loughran <st...@apache.org>.
Phil Weighill-Smith wrote:
> On Tue, 2005-01-25 at 09:22, Erik Hatcher wrote:
>
>
>>You may consider creating a custom ant command script which unsets
>>CLASSPATH before invoking the executable class.
>>
>
>
>
> Exactly what we do!
>
>
ant -noclasspath does what youwant
we could be brutal and make that the default. That is, from ant1.7+ we
ignore the classpath unless you request otherwise. We say it was too
much a source of trouble and leave it at that. Add a -classpath option
for backwards compat; all is well.
-steve
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Proposal
Posted by Phil Weighill-Smith <ph...@volantis.com>.
My guess is that, because of backward compatibility, the "ant" startup
scripts won't get changed to unset it (which they could do easily
enough). Some people use the classpath to actually add extra libraries
to Ant because of historical needs (yes, there are better means of doing
so now).
Some documentation stating that there can be issues, and that people
should check what their class path is if they have trouble running Ant,
would be a good thing. Other than that, use a crutch or persuade someone
that backwards compatibility isn't so critical in this case (or to add a
special "use environment's class path" option to Ant's invocation to
allow for backwards compatibility).
Phil :n.
On Tue, 2005-01-25 at 09:37, Kev Jackson wrote:
> Phil Weighill-Smith wrote:
>
> >On Tue, 2005-01-25 at 09:22, Erik Hatcher wrote:
> >
> >
> >
> >>You may consider creating a custom ant command script which unsets
> >>CLASSPATH before invoking the executable class.
> >>
> >>
> >>
> >
> >
> >Exactly what we do!
> >
> >
> <rant>My point was that it shouldn't be set in the first place,
> unsetting it before running is good, but it's a crutch. The developers
> shouldn't have it set in the first place</rant> Oh and Oracle setting
> it is no excuse as they have been told to uninstall the damn Oracle
> client on many many occasions
>
> Kev
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
--
Phil Weighill-Smith <ph...@volantis.com>
Volantis Systems
Re: Proposal
Posted by Kev Jackson <ke...@it.fts-vn.com>.
Phil Weighill-Smith wrote:
>On Tue, 2005-01-25 at 09:22, Erik Hatcher wrote:
>
>
>
>>You may consider creating a custom ant command script which unsets
>>CLASSPATH before invoking the executable class.
>>
>>
>>
>
>
>Exactly what we do!
>
>
<rant>My point was that it shouldn't be set in the first place,
unsetting it before running is good, but it's a crutch. The developers
shouldn't have it set in the first place</rant> Oh and Oracle setting
it is no excuse as they have been told to uninstall the damn Oracle
client on many many occasions
Kev
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org
Re: Proposal
Posted by Phil Weighill-Smith <ph...@volantis.com>.
On Tue, 2005-01-25 at 09:22, Erik Hatcher wrote:
> You may consider creating a custom ant command script which unsets
> CLASSPATH before invoking the executable class.
>
Exactly what we do!
--
Phil Weighill-Smith <ph...@volantis.com>
Volantis Systems
Re: Proposal
Posted by Erik Hatcher <er...@ehatchersolutions.com>.
You may consider creating a custom ant command script which unsets
CLASSPATH before invoking the executable class.
Erik
On Jan 24, 2005, at 10:40 PM, Kev Jackson wrote:
> Hi,
>
> I'm working on a project right now with real neophyte developers, and
> one of the things I'm constantly having to do is to unset classpaths.
>
> They keep installing crappy software that sets a classpath variable
> (Oracle client being the main culprit here) and then when they use the
> project build file, it falls over because of alien jars on the
> classpath (not Ant's fault or anything).
>
> I'm sure that this is a commonplace occurence, so I propose the
> following...
>
> On the website (ant.apache.org), in bold letters across the front page
>
> "PLEASE FOR THE LOVE OF $DEITY, UNSET YOUR CLASSPATH BEFORE RUNNING
> ANT!!"
>
> or if not on the front page, at least in the manual section. I'm even
> willing to add the documentation to the xdocs or html
>
> Also I think it'd be a good idea to print this out when simply typing
> "ant" at the command line - not just "build.xml does not exist"
>
> Sorry, rant off
>
> Kev
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
> For additional commands, e-mail: dev-help@ant.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org