Why would you want to make anything a property? To avoid duplication is generally the main one.
My original point though you confirmed... m2eclipse does not support importing modules with properties. Which leads me to my next question... Should it? And yes I have seen that link. It however does not explain why I would want to use modules in profiles. Profiles, from my understanding, are meant to define various environments like a test environment that would use a test server instead of a production server. Modules are the same always so why would I want to put it in a profile? Again, Pros/Cons?? I understand the syntax of putting it in a profile, but not the value of doing so. And BTW, I found this link to be much better at describing profiles but it is just as lacking wrt putting module information in a profile. http://maven.apache.org/guides/introduction/introduction-to-profiles.htm l --- Todd Thiessen -----Original Message----- From: Eugene Kuleshov [mailto:[EMAIL PROTECTED] Sent: Thursday, November 27, 2008 12:02 PM To: [email protected] Subject: Re: [m2eclipse-user] Multi-modules with properties 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 --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email
