Todd Thiessen wrote:
Correct. It can't import these modules. I am not sure what other kind
of support you may be referring to.
I don't understand what you mean by declaring modules in profiles
either. Why would you want to do this?
I think we are even here. I don't understand why would you want do use
properties for module names. :-)
Pros/Cons? Could you elaborate a little?
I never saw anyone using properties in the module names. However there
is quite few open source projects using such approach (e.g. when they
want to exclude certain modules from the build) and it is fully
supported by m2eclipse.
I have seen no documentation regarding defining multi-module
projects this way.
It is documented here http://maven.apache.org/pom.html#Profiles See
<modules> element.
Also, xsd schema for Maven's pom.xml is published and any decent xml
editor would provide you content assist based on it. More over, Maven
POM editor from m2eclipse provide form-based UI for editing all pom content.
So, modules could be declared like this:
<profiles>
<profile>
<id>someProfile</id>
<modules>
<module>module1</module>
<module>module2</module>
</modules>
</profile>
</profiles>
regards,
Eugene
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
