If you have "trunks" underneath subprojects, that tells me they have independent release cycles. If you want them to be versioned separately, your structure is okay. If you want the master project to build and control the subprojects as modules, I would re-organize everything under one trunk.
Paul On Tue, Oct 19, 2010 at 9:40 AM, thisguy <bobsmith30...@yahoo.com> wrote: > > Hello experts, I'm trying to reconcile the standard maven project structure > with the standard svn project structure (with per-project versioning). I'd > like to have a subversion structure like this: > > pom.xml > --proj A > ----trunk > ------pom.xml > ------src > --proj B > ----trunk > ------pom.xml > ------src > > etc. > > How can I get maven to build everything properly? > > Should I use svn externals to magically remove the trunk directories so that > this layout would conform to standard maven layout? If I did that, how > would I handle the situation of wanting to build a particular > branch..wouldn't I have to update the externals properties back and forth > (cumbersome)? > > Or should I change all project poms to use parent relative paths of > "../../pom.xml" to get to the parent pom? But this technique wouldn't work > if I wanted to build a particular branch because it would be an extra level > deep (i.e. proj->branches->1.0.0->pom.xml). > > What is best practice here? Thank you. > > > -- > View this message in context: > http://maven.40175.n5.nabble.com/project-structure-with-per-project-trunks-and-svn-tp3219163p3219163.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
