ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sam Berlin <>
Subject Multi-Project IvyDE
Date Mon, 30 Mar 2009 17:34:33 GMT
Hi All,

We have a large multi-project repository that currently uses Ivy+Ant and
works very well.  I'm looking into using IvyDE, but setting it up for a
large multi-project repository seems to be a real pain.

An ivy.xml file exists in each project, and a shared ivysettings exists
under the 'common' project's directory.  I've been able to configure IvyDE
properly by using "project:///ivysettings.xml" in the common project's IvyDE
properties and 'project://common-project-name/ivysettings.xml' in each other
module's IvyDE properties.  This works, but is a real pain to setup.

What I'd like to do is something similar to the m2eclipse plugin, where they
take the parent of a multi-module pom and the plugin automatically creates a
project for each module.  In Ivy-land, this would be similar to subant after
ivy:buildlist within Ant.

Would you be amenable to having some kind of 'Checkout as Ivy Project' or
'Create Ivy Project' that scans for subdirectories containing ivy.xml
(perhaps offering options similar to buildlist) and then automatically
creating each project it finds?  The setup wizard could ask where a shared
ivysettings is for each project and automatically fill in the properties for
each project.  Something like this would be an amazing step in in terms of
usability of IvyDE for multi-project repositories.

I can investigate into how m2eclipse does this and try and create something
similar for IvyDE if people think this is a feature that would be accepted.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message