Win a copy of Reactive Streams in Java: Concurrency with RxJava, Reactor, and Akka Streams this week in the Reactive Progamming forum!
  • 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 all forums
this forum made possible by our volunteer staff, including ...
Marshals:
  • Campbell Ritchie
  • Liutauras Vilda
  • Junilu Lacar
  • Jeanne Boyarsky
  • Bear Bibeault
Sheriffs:
  • Knute Snortum
  • Tim Cooke
  • Devaka Cooray
Saloon Keepers:
  • Ron McLeod
  • Stephan van Hulst
  • Tim Moores
  • Tim Holloway
  • Carey Brown
Bartenders:
  • Piet Souris
  • Frits Walraven
  • Ganesh Patekar

Multi Module Maven Project using SVN

 
Saloon Keeper
Posts: 2722
354
Android Eclipse IDE Angular Framework MySQL Database TypeScript Redhat Java Linux
  • Likes 1
  • Mark post as helpful
  • send pies
  • 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: 39530
776
Eclipse IDE VI Editor Java
  • Mark post as helpful
  • send pies
  • 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!
 
Seriously Rick? Seriously? You might as well just read this tiny ad:
Java file APIs (DOC, XLS, PDF, and many more)
https://products.aspose.com/total/java
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!