Ivy.xml files are duplicated in all the sub-projects, and are painful to use when cloning the repository and configuring the dependencies.
Using an other dependency / project life-cycle solution such as maven would be a good idea, but there are few challenges to tackle:
we need to compile ATL transformations in the Maven build process
we need a complex, 2 step Tycho-based build to generate the update site and resolve Eclipse-based dependencies (same as NeoEMF)
For now the former is an issue, because there is no usable solution to compile ATL transformations in a maven build. The later is similar to what we use in NeoEMF
Ivy.xml files are duplicated in all the sub-projects, and are painful to use when cloning the repository and configuring the dependencies.
Using an other dependency / project life-cycle solution such as maven would be a good idea, but there are few challenges to tackle:
For now the former is an issue, because there is no usable solution to compile ATL transformations in a maven build. The later is similar to what we use in NeoEMF