ant-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Maarten Coene <maarten_co...@yahoo.com>
Subject Re: distribution of ivy with ant
Date Tue, 09 Jun 2009 21:47:04 GMT

Or maybe we can create an extra Ant distribution which contains the standard Ant tasks + Ivy
(+ other antlibs?)

Maarten




----- Original Message ----
From: Jean-Louis BOUDART <jeanlouis.boudart@gmail.com>
To: Ant Developers List <dev@ant.apache.org>
Sent: Friday, May 29, 2009 5:38:24 PM
Subject: Re: distribution of ivy with ant

IMHO Ant and Ivy may be released separately.

Each project has his own release process. Release are more common on ivy
whereas Ant is released once in one or two years.
Does it means that ant will make a whole distribution for each strong
enhancements on ivy? I agree Xavier that people may want to update their own
ivy version without waiting for an ant distribution.

Even if ivy offer a lot of ant tasks its first of all a standalone tool that
provide all you need to deal with dependency management. This means ivy was
originally made to work outside of any ant context.

Considering that it make sense that ivy is and should stay an optionnal ant
task.

"1. Out-of-the-box support for dependency management for ant
2. Better integration of ivy with ant
3. No more check, download and load ivy targets in build files
4. Lowered entry barrier to using ivy  for existing ant users
5. Exposure of ivy to more users"
I'm totally +1 but i'm not sure Ant is the best place to do that.
To have out of the box support you will need to provide some preconfigured
targets  (that also implies to have conventions) ivysettings.xml and this is
not the job of "ant".

If you are looking for a tool that make a distribution of ant+ivy with
conventions / preconfigured targets / preconfigured ivy conf and that is
still flexible you should probably look at :

   - Gradle (http://www.gradle.org)
   - EasyAnt (http://www.easyant.org).


>From my point of view those two projects can make the usage of ant+ivy
easier.

Cheers,
Jean Louis Boudart


2009/5/28 Nick Pellow <npellow@atlassian.com>

> +1 to shipping Ivy with Ant - maybe even call it Ant 2.0 ?
>
>
> On 28/05/2009, at 2:30 AM, Jason Trump wrote:
>
>  That is definitely a cool idea.  Another possibility would be to use
>> embedded Ivy to implement an auto-update feature for ant and/or ivy itself.
>> Not a "three-dialogs-per-day" kind of auto-update feature, of course.
>>
>> jason
>>
>> ________________________________
>>
>> From: Martin Eigenbrodt [mailto:martineigenbrodt@googlemail.com]
>> Sent: Wed 5/27/2009 2:02 AM
>> To: Ant Developers List
>> Subject: Re: distribution of ivy with ant
>>
>>
>>
>> I think this is a great Idea and could bring the power of ivy to the core
>> of
>> ant. You could then even change taskdef (or write  a similair task) to
>> support somethingh like:
>>
>> <taskdef org="cobertura" module="cobertura" revision="1.9.1"
>> resource="tasks.properties"/>
>>
>> No need to manually download the files and setup a path before. This would
>> make using ant extensions/ thirdparty tasks easier.
>>
>> Best regards,
>>
>> Martin
>>
>>
>>
>> 2009/5/27 Xavier Hanin <xavier.hanin@gmail.com>
>>
>>  On Tue, May 26, 2009 at 4:49 PM, Steve Loughran <stevel@apache.org>
>>> wrote:
>>>
>>>  Enis Soztutar wrote:
>>>>
>>>>  I don't know if it is discussed previously but I was wondering why ivy
>>>>>
>>>> is
>>>
>>>> not included in the ant distribution. More and more projects previously
>>>>> depending on ant start to use ivy, but the build files are cluttered
>>>>>
>>>> with
>>>
>>>> ivy-download, check-ivy-antlib, etc. Technically ivy is a subproject of
>>>>>
>>>> ant,
>>>
>>>> and it can be used optionally. However if they are distributed together
>>>>> there will be several benefits:
>>>>> 1. Out-of-the-box support for dependency management for ant
>>>>> 2. Better integration of ivy with ant
>>>>> 3. No more check, download and load ivy targets in build files
>>>>> 4. Lowered entry barrier to using ivy  for existing ant users
>>>>> 5. Exposure of ivy to more users
>>>>>
>>>>> the only drawback I can think of is the extra ivy jar file in the
>>>>> distribution.
>>>>>
>>>>> Is there any plans on the roadmap?
>>>>>
>>>>>
>>>>>  Now that ivy is part of Ant, it makes sense to start thinking of
>>>> bundling
>>>> the two. However, it may tie the release cycle of the faster moving item
>>>> (ivy) to that of the slower one.
>>>>
>>>
>>> Ivy may still be released separately too, so that people wanting to
>>> upgrade
>>> their Ivy version without waiting for a release of Ant could still do it.
>>> WDYT?
>>>
>>> Xavier
>>>
>>>
>>>  Do you think things have stabilised/slowed down enough for this? We can
>>>>
>>> of
>>>
>>>> course increase the release frequency of Ant...
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org
>>>> For additional commands, e-mail: dev-help@ant.apache.org
>>>>
>>>>
>>>>
>>>
>>> --
>>> Xavier Hanin - 4SH France
>>> BordeauxJUG co leader - http://www.bordeauxjug.org/
>>> Blogger - http://xhab.blogspot.com/
>>> Apache Ivy Creator - http://ant.apache.org/ivy/
>>>
>>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> 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
>
>



      

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


Mime
View raw message