• Post Reply Bookmark Topic Watch Topic
  • New Topic
programming forums Java Mobile Certification Databases Caching Books Engineering Micro Controllers OS Languages Paradigms IDEs Build Tools Frameworks Application Servers Open Source This Site Careers Other Pie Elite all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Jeanne Boyarsky
  • Ron McLeod
  • Paul Clapham
  • Liutauras Vilda
Sheriffs:
  • paul wheaton
  • Rob Spoor
  • Devaka Cooray
Saloon Keepers:
  • Stephan van Hulst
  • Tim Holloway
  • Carey Brown
  • Frits Walraven
  • Tim Moores
Bartenders:
  • Mikalai Zaikin

Multi Module Maven Project using SVN

 
Marshal
Posts: 4501
572
VSCode Eclipse IDE TypeScript Redhat MicroProfile Quarkus Java Linux
  • Likes 1
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator
I have a multi-module Maven project which is version controlled using SVN.  I need to be able to release the modules independently, so each module has it's own trunk and maven version.

The directory structure is like this:
Since the Maven reactor expects the modules to be located directly below the parent, maven complains that it cannot find the modules because the modules are below it's trunk directory.

To work-around this, I appended /trunk to the module path in the parent pom:
I also needed to add a relativePath element to each module pom so that they could find the parent:
Is this normal, or is there some way to make the reactor SCM-aware, and deal with trunks and branches without the need to specify the path in each pom?
 
author & internet detective
Posts: 41860
908
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
    Number of slices to send:
    Optional 'thank-you' note:
  • Quote
  • Report post to moderator

Ron McLeod wrote:I have a multi-module Maven project which is version controlled using SVN.  I need to be able to release the modules independently, so each module has it's own trunk and maven version.


I'm not sure that you need to have a separate trunk/tags. I know you can have unrelated projects in the same trunk like:


That lets you use a relatie path in your aggregator pom and not to have to deal with the /trunk hack.

Cow for an excellent question!
 
With a little knowledge, a cast iron skillet is non-stick and lasts a lifetime.
reply
    Bookmark Topic Watch Topic
  • New Topic