again....

http://github.com/klaas1979/ivy4r/


Am 24.08.2010 um 08:14 schrieb Nikos Maris:

Is there any support site for ivy4r, bug tracking or a mailing list?

On Mon, Aug 23, 2010 at 11:17 AM, Klaas Reineke <[email protected]> wrote:
> Hi,
> 
> ivy4r is not dead at all :)
> 
> I am still maintaining it and we are using it on our build server every day 
> for around 90 build plans. There is a need for better documentation and a few 
> examples. Right now I don't know any open feature request. There is an 
> outstanding merge from "stephenh" on git, but beside this everything is up to 
> date and working.
> 
> Regards Klaas
> 
> 
> 
> -----Original Message-----
> From: Nikos Maris [mailto:[email protected]]
> Sent: Monday, August 23, 2010 9:58 AM
> To: [email protected]
> Subject: Re: ivy4r vs buildr
> 
> Is there any partial Ivy support in the svn? Ivy4r seems to be a dead project.
> 
> ----------------------------------
> Nikos Maris
> Software Engineer
> IMC Technologies SA
> www.imc.com.gr
> 
> On Mon, Aug 23, 2010 at 4:48 AM, Alex Boisvert <[email protected]> 
> wrote:
>> On Sunday, August 22, 2010, Nikos Maris <[email protected]> wrote:
>>> Why does buildr provide dependency management when there is already
>>> Ivy? Does it make sense to make the transitive method use ivy4r in an
>>> upcoming buildr release? Having a fork of Ivy that is less
>>> configurable but simpler, is something that I wished when I started
>>> these days to learn Ivy.
>> 
>> What buildr does today is the minimum/easiest that could accomodate
>> people without reinventing Ivy.
>> 
>> Yes, the plan is to reuse Ivy (or a subset) to complete transitive
>> dependency support.  It will likely be an opinionated approach, with
>> many choices taken out of what's possible to do with Ivy, aligning
>> ourselves with Maven in terms of compatibility, and favoring
>> determinism.
>> 
>> For people who want full Ivy support, Buildr would defer to the Ivy4r plugin.
>> 
>> The timeframe for this seems to be Buildr 1.5 -- hopefully before the
>> end of 2010 but no guarantees.
>> 
>> alex
>> 
> 

Reply via email to