[
https://issues.apache.org/jira/browse/IVY-1414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gintas Grigelionis updated IVY-1414:
------------------------------------
Description:
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 Ivy
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 Ivy more attractive for transition from
Maven.
was:
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.
> 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
> Priority: Major
>
> 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
> Ivy 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 Ivy more attractive for transition from
> Maven.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
