Re: [Freemarker-devel] Dependency management

[Daniel D. <dd...@fr...>]

Friday, February 27, 2009, 11:38:09 AM, Attila Szegedi wrote:

> I've been experimenting with Ivy for some other projects of mine, and
> so far, I like it very much. It does one thing only (dependency  
> management), and does it right. It ain't and doesn't strive to be the
> kitchen sink Maven is.

(You know, I could even see the benefits of Maven's "fascist" approach
-- "Everyone shall do it this way, the way We said -- if that Only Way
were heavy-weight enough so that projects with the real-world's
chaotic complexity and variety could use it, not to mention when you
have some extravagant quality demands. Now some guys will stand up
saying they used it for this and that ultimately serous stuff with
Great success... I don't know, no tinned solutions ever worked for me.
Maybe I'm just so unlucky, but then, I can only live my own life,
so... Maven miserably failed for me when I tried to use it, and I can
see well ahead this will not change. It just shows that it was
developed with a few concrete project in mind (Turbine initially).
It's bit like Docgen... it generates docs fine for 3 project so far,
but if I will use it for a 4th, I bet I immediately add new options to
it again. But we state clearly that it's like that... use it if
happens to fulfill your needs to, but chances are high that it
doesn't.)

> Maven't big advantage is that everyone publishes to the Maven repo.  
> Ivy neatly solves this by being able to use Maven repositories for  
> fetching the JAR files :-)

OK, so, we had the same impressions. So then, shall we use Ivy for FM?

> Attila.
>
> On 2009.02.23., at 21:55, Daniel Dekany wrote:
>
>>> Ivy is definitely an option (and also the notorious Maven ;-)
>>
>> (Yeah... I would avoid Maven.)
>>
>>> ). From Bamboo's perspective Ivy is just another task called from
>>> Ant, so I guess that there won't be any problems with Ivy and
>>> Bamboo. But then everyone else (developers and users who build their
>>> own FreeMarker) would have to use Ivy as well, so before switching
>>> to Ivy we should be aware of the consequences.
>>
>> Oh, but we are aggressive bastards! :) *If* Ivy is a fine piece of
>> software, we are going to push it, right guys?
>>
>>> Stephan.
>>
>> -- 
>> Best regards,
>> Daniel Dekany

-- 
Best regards,
 Daniel Dekany