On Fri, 19 Sep 2003, Antoine Lévy-Lambert <[EMAIL PROTECTED]>
wrote:
>Von: Stefan Bodewig [mailto:[EMAIL PROTECTED]
>>One of the reasons for the new launcher has been a command line
>>length limitation. With this approach the command line would even
>>become longer, I'm afraid.
>
> This is just
On Fri, 19 Sep 2003, Antoine Lévy-Lambert <[EMAIL PROTECTED]>
wrote:
> I am a bit concerned about the fact that CLASSPATH is ignored by the
> new launcher.
But the old launcher (Main) will still work the same way.
> There are lots of scripts which invoke ant as script, and set
> CLASSPATH to inc
On Fri, 19 Sep 2003, Conor MacNeill <[EMAIL PROTECTED]>
wrote:
> On Fri, 19 Sep 2003 12:18 am, Stefan Bodewig wrote:
>
>> Not in this case, as the classloader created in Launcher contains
>> all that's been in the CLASSPATH already itself.
>
> I'm not sure that is true.
Yes, my fault, I didn't lo
On Fri, 19 Sep 2003 12:18 am, Stefan Bodewig wrote:
> On Fri, 19 Sep 2003, Conor MacNeill <[EMAIL PROTECTED]>
> > This approach in the end is really the same as not using the
> > CLASSPATH variable. After all, if we don't delegate, we wont find
> > the classes the user has put in their classpath wh
On Fri, 19 Sep 2003, Conor MacNeill <[EMAIL PROTECTED]>
wrote:
> The issue comes from getting it to not delegate.
I know.
> This approach in the end is really the same as not using the
> CLASSPATH variable. After all, if we don't delegate, we wont find
> the classes the user has put in their cla
On Thu, 18 Sep 2003 11:41 pm, Stefan Bodewig wrote:
> On Thu, 18 Sep 2003, Conor MacNeill <[EMAIL PROTECTED]>
> >
> > I don't think this will work. No matter which classloader you use to
> > find the class, if it is found on the system class loader it will
> > try to load dependent classes with the
On Thu, 18 Sep 2003, Conor MacNeill <[EMAIL PROTECTED]>
wrote:
> On Wed, 17 Sep 2003 08:29 pm, Stefan Bodewig wrote:
>> (2) Fix all tasks that load classes - like Definer - to delegate to
>> the classloader created in Launcher instead of the system
>> classloader.
>
> I don't think this will work
> > As ant.jar cannot be found on the system classloader anymore, any
> > class loaded from the system classloader (i.e. classes coming from
> > CLASSPATH) can't load the Task class for example.
> >
> > I see two options:
> >
> > (1) live with it and document it properly (which means
> people may
On Wed, 17 Sep 2003 08:29 pm, Stefan Bodewig wrote:
> So far all our documentation more or less states that putting your jar
> containing custom tasks into ANT_HOME/lib or pointing to it in your
> CLASSPATH was equivalent. This is no longer true if the new launcher
> is used.
True.
>
> As ant.ja
