ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Antoine Levy-Lambert" <anto...@gmx.de>
Subject Re: VOTE ant-vss antlib promote to antlib proper
Date Tue, 01 Aug 2006 19:39:13 GMT
Hello,

+1 with DDs views.

Regards,

Antoine
-------- Original-Nachricht --------
Datum: Tue, 1 Aug 2006 08:04:57 -0500
Von: "Dominique Devienne" <ddevienne@gmail.com>
An: "Ant Developers List" <dev@ant.apache.org>
Betreff: Re: VOTE ant-vss antlib promote to antlib proper

> > > I am +1 for moving VSS support into its own antlib. The only
> > > problem is that adding the antlib to ANT_HOME/lib will not ensure
> > > that existing build files will work, because to get the stuff
> > > autoloaded, they need to declare it in a new namespace. Unless,
> > > that is, the main defaults.properties file still declares the
> > > existing task in its (new) location...
> > >
> > Good point, so if the vote passes, we should make sure that we
> > implement the changes in a BWC way.
> 
> +1 on making VSS an antlib.
> 
> However, I'm not sure at all we should bind ourselves to moving things
> to antlibs in a BC manner necessarily. One of the benefits to going
> more towards releasing Ant as a smaller core and a set of antlibs is
> to avoid trying to load a bunch of tasks (Jars) all the time, when a
> fraction only is actually used. I personally don't think it's
> unreasonnable to force <vss> users to explicitly load the antlib in
> their build file, using XML NS or an explicit <antlib>.
> 
> So, +1 on simply removing the vss entries to optional.properties, and
> provide the antlib. --DD

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
For additional commands, e-mail: dev-help@ant.apache.org


Mime
View raw message