[ 
https://issues.apache.org/jira/browse/IVY-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13627515#comment-13627515
 ] 

Vyacheslav Sakhno commented on IVY-1414:
----------------------------------------

I've read a lot Maven documentation and articles instead of book. There is a 
number of reason to migrate from maven. My current reason is that project build 
code is written as a number of Ant targets which must be executed separately. 
In maven I need to create separate pom.xml files. There are no way to separate 
execution of Ant targets within one Maven lifecycle. I also don't like Maven 
because it have no good support for building graphs of projects(they must be 
located in the same directory and form a tree of projects, that is not always 
the case). For more reasons you can see Hibernate site explanaing for migration 
from Maven to Gradle. This is why i prefer at least procedural way, 
Turing-complete language way, to build projects which Ant and Gradle provide 
instead of fixed lifecycle. But beeing pragmatic to new technologies and 
looking for a best support in IDE for build tool i choose Ant + Maven used as 
Ivy(dependency download only) with drawbacks described before in this message.
                
> create possibility for easy transition from Maven
> -------------------------------------------------
>
>                 Key: IVY-1414
>                 URL: https://issues.apache.org/jira/browse/IVY-1414
>             Project: Ivy
>          Issue Type: Improvement
>          Components: Core
>    Affects Versions: 2.3.0
>            Reporter: Vyacheslav Sakhno
>
> Maven is declarative and not easy to understand build system. To build 
> several target they must be sequenced and executed together as a part of 
> lifecycle. That slowdown build speed by N times for N targets. The only 
> functionality maven do well is dependency management which is equivalent to 
> Ive functionality. So is does make sense to move to Ant+Ivy instead of Maven.
> I suggest to improve support for that migration:
> Make Ivy support maven dependency format: easy to implement for one developer 
> but removes 1 hour hand work for thousands developers over the world.
> Also make support of reading dependencies from maven repo and publishing the 
> to it.
> Though it is easy work to do it makes Ive more attractive for transition from 
> Maven.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to