ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From <cost...@covalent.net>
Subject Re: <antlib> (was RE: Ant 1.9 & Task Packaging)
Date Thu, 24 Jan 2002 00:36:16 GMT
On Wed, 23 Jan 2002, Tim Dawson wrote:

>
> <antlib location="${weblogic.home}/lib/weblogic.jar"/>

Or with the existing ant:

    <taskdef resource="META-INF/ant.tasks"
	     classpathref="jkant" />

It works fine, I use it every day ( with ant.tasks beeing a properties
file listing task names and their impl ).

Costin

>
> I think they'd probably be happy to add that to each of the build.xml files
> in exchange for not having to include a version of ant inside their
> weblogic.jar file.
>
> So what's holding us back with implementing <antlib>? There were some
> proposals a while back but nothing ever really happened with them, it seemed
> there was some concern about forward-compatibility with Ant2 - is that still
> the concern?
>
> Tim
>
> > -----Original Message-----
> > From: Stefan Bodewig [mailto:bodewig@apache.org]
> > Sent: Tuesday, January 22, 2002 7:14 AM
> > To: ant-dev@jakarta.apache.org
> > Subject: Re: Ant 1.9 & Task Packaging
> >
> >
> > On Mon, 21 Jan 2002, Tim Dawson <tdawson47@yahoo.com> wrote:
> >
> > > currently we have a few packages, "taskdefs", for the - supposedly -
> > > core stuff, and taskdefs.compilers, taskdefs.condition,
> > > taskdefs.rmic, and then a catchall, taskdefs.optional.* where
> > > everything else is bunched. This is a bit confusing as some tasks
> > > haven't been migrated to a hierarchy, etc.
> >
> > It is not strictly a matter of migration (the compiler, rmic and
> > condition subpackages just happened to suddenly be there 8-).  Moving
> > classes into different packages can create backwards compatibility
> > problems as well (there is at least one link on our external tools
> > page to a task that "extends org.apache.tools.ant.taskdefs.Javac").
> >
> > Of course we are free to chose new packages for Ant2 as we like.
> >
> > > org.apache.tools.ant2
> > > 	(main engine, interfaces, abstract superclasses)
> >
> > make that org.apache.ant, no need for the 2 IMHO as Ant 1.x is in the
> > tools subpackage.
> >
> > Most (all?) proposals use that package as well.
> >
> > > Anything inside of core and included in the build would have to pass
> > > a strict "can this run without ANY 3rd party jars?"
> >
> > A very hard rule and we won't hold it, I'm sure.  Crimson is a 3rd
> > party jar.
> >
> > > Further, if we're really moving to a container architecture with
> > > Ant2, then we should define a spec for the build file, execution
> > > engine, and task extensions API through a JSR
> >
> > Has been proposed by others (Conor) before.
> >
> > > BEA should be able to provide a "weblogic.jar" that could just be
> > > referenced in a build file, and used with whatever recent version of
> > > Ant you've downloaded.
> >
> > You are absolutely correct, they should be.  Why don't they?  All
> > people would have to do was to add a single <taskdef> line.
> >
> > Stefan
> >
> > --
> > To unsubscribe, e-mail:
> > <mailto:ant-dev-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail:
> > <mailto:ant-dev-help@jakarta.apache.org>
>
>
> _________________________________________________________
> Do You Yahoo!?
> Get your free @yahoo.com address at http://mail.yahoo.com
>
>
> --
> To unsubscribe, e-mail:   <mailto:ant-dev-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:ant-dev-help@jakarta.apache.org>
>
>


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


Mime
View raw message