Add support for multiple ivy.xml files in a single module

[GoogleCodeExporter]

Hi,

I wondered if it would be possible to support multiple ivy.xml files inside
a single module?

regards,
Maarten

Original issue reported on code.google.com by maarten....@gmail.com on 31 Mar 2009 at 1:15

[GoogleCodeExporter]

Hm, could you describe your usecase a bit more detailed? I currently can't 
think of a
usecase that is not possible to solve with different modules in IntelliJ.

Original comment by andreas....@gmail.com on 1 Apr 2009 at 7:30

[GoogleCodeExporter]

Yes, we can workaround it by using multiple modules, but I would like to have 
the
choice whether to combine multiple source-dirs into 1 IntelliJ module or not...

For instance, we have the following source structure:
/path/sourcesA/...
/path/sourcesATest/...
/path/sourcesB/...
/path/sourcesBTest/...

Some of us are combining the sources and the tests of A into a single module, 
while
others like to have them as separate modules. With the current IvyIDEA plugin, 
it is
not possible to have both the sources and the tests in a single module.

Maarten

Original comment by maarten....@gmail.com on 2 Apr 2009 at 7:51

[GoogleCodeExporter]

I still don't get it, sorry. Why is it not possible to have sources and tests 
in a
single module? Assuming you have different dependencies for every sources path, 
you
can create an ivy file with configurations for every sources dir. 

Now the guy who wants to have one module just uses one ivy-module and turns on 
all
configurations, combining all dependencies into one module. 

The guy who wants different modules just creates different ivy-modules and uses
always the same ivy file but for every module he uses a different 
configuration, so
he just have the dependencies he needs for the particular module.
Why doesn't this work for you? 

BTW: I am not the ivyidea developer, I am just curious. :)

Original comment by andreas....@gmail.com on 2 Apr 2009 at 8:44

[GoogleCodeExporter]

The ivy.xml for every sources path is located inside the path itself, for 
instance,
the ivy.xml files are here:

/path/sourcesA/ivy.xml
/path/sourcesATest/ivy.xml

We have about 100 such source paths, so creating 1 big ivy.xml containing
configurations/dependencies for every sourcepath is possible but doesn't seem 
very
practical.

Maarten

Original comment by maarten....@gmail.com on 2 Apr 2009 at 9:13

[GoogleCodeExporter]

Ah, now I see. We only have max 3 modules which can be easily setup inside one 
ivy
file. I agree, doing this for so many source paths is prolly a pain and would 
blow up
the ivy file to a mess.

Original comment by andreas....@gmail.com on 2 Apr 2009 at 9:29