[jboss-dev] Why Maven sucks (part 1)

[Carlo de Wolf]

Ovidiu Feodorov wrote:
> Jason T. Greene wrote:
>> Ovidiu Feodorov wrote:
>>>
>>> Thank you, Rémy
>>>
>>> The system I am talking about I delegates the build tasks to ant, 
>>> feeding it with the appropriate dependency information. In this 
>>> respect, your build can be as simple as "ant", no need for maven 
>>> commands.
>>
>> Awesome. This is exactly how it should be. The whole idea of limiting 
>> a project to 5 build commands is flawed. Using "profiles" to solve 
>> this limitation is also flawed (and confusing).
>>
>> How does your system compare to Ivy (besides support for native code 
>> integration)? Do you have any plans to support pulling from maven2 
>> repos as a stop-gap?
> 
>  From a dependency management perspective, Ivy and Fragma are pretty 
> much the same thing, except obviously the fact that Fragma supports 
> generically "attributed" artifacts, which is essential for heterogeneous 
> development environments. Not JBoss' case, maybe with the exception of 
> JBossWeb and its support for native connector code.

Ivy has the notion of configurations, so any type of artifact can be 
published.

> If you really interested in a point-to-point comparison, I could add 
> that to the manual.

Yes, very much. I would like to see what Fragma gives over Ivy. And also 
  I would like to see a list of (useful) features which Ivy & Fragma 
have that Maven doesn't provide.

Carlo