[jboss-dev-forums] [Design of JBoss Portal] - Re: Maven Migration Status

pom file http://anonsvn.jboss.org/repos/portal/modules/pom.xml discovery This file contains xml module=common/trunk/common problems This gives some problems. Consider you make a release then you would need to change the <module..> to common/release/yyyy-mm-dd/common Further more it gives the root-pom problem Thomas writes about. Suggestion I belive it would be better to make a svn directory i.e. /repos/portal/modules/trunks/pom.xml and in the trunks directory you should use svn external link to link common to common/trunk. and add an external for each module inside the root pom.xml the module ... would be consistent module common /module independent of your releases. result 1) A release would be a copy of trunks/pom.xml to i.e. releases/yyyy-mm-dd/pom.xml including changing the external list to common = common/release/xxx and so on. 2) the root pom would work nicely with mvn idea:idea .. mvn eclipse:eclipse (that I belive the current solution does not) improvement It seems you work with a two layer pom structure. It could be a good idea to make three layers root.pom --> module.pom --> artifact.poms Doing this works good with svn externals /Anders View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4089888#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...