On 9/19/07, Steve Loughran <[EMAIL PROTECTED]> wrote:
>
> Stefan Bodewig wrote:
>
> >
> > Also, we've seen a few Ant committers being involved with bug reports
> > and discussions here. Who knows, maybe graduating to Ant will make
> > those bonds even stronger and we'll end up with a few Ant committers
> > becoming Ivy committers as well.
> >
> > Stefan
>
> Oh, I'd like to get involved,
Great!
I'm just overwhelmed with umpteen other
> things.
>
> What I'd really like to do is add tighter support for Ivy inside Ant too.
This would be very nice indeed.
I've just checked in a FileProvider interface for resources, and have
> (uncommitted) changes to a lot of the resource enabled tasks to use
> FileProviders instead of requiring file system resources to be instances
> of FileResource. What that could do is let
> Ivy add a new resource that refers to an an artifact, which could then
> be used inline
>
> <copy todir="build/app/WEB-INF/lib" >
> <ivy:artifact org="org.apache.tomcat" artifact="tomcat"
> version="${tomcat.version}" />
> </copy>
>
> We could even have an ivy:artifacts collection, that dynamically
> represents a specific configuration from the ivy conf
>
> <copy todir="build/app/WEB-INF/lib" >
> <ivy:artifacts conf="webapp" />
> </copy>
Would this require to call resolve before? Or would it be roughly equivalent
to what a resolve do?
Xavier
This is for the 1.8 release; its something we need to get stable before
> freezing it in shipping code. One thing I'm thinking I'd like is some
> notion of a lifecycle for datatypes, so we can tell resources when they
> are created, and when they are no longer required.
-steve
>
> --
> Steve Loughran http://www.1060.org/blogxter/publish/5
> Author: Ant in Action http://antbook.org/
>
--
Xavier Hanin - Independent Java Consultant
http://xhab.blogspot.com/
http://incubator.apache.org/ivy/
http://www.xoocode.org/
