Home/ Questions/Q 7963501
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-04T05:37:11+00:00

Background one trunk and one branch in a standard svn layout, /trunk and /branches/prod

  • 0

Background

  1. one trunk and one branch in a standard svn layout, /trunk and /branches/prod
  2. about 20 modules in the maven project
  3. when i want to compile trunk, just type cd trunk; mvn clean package. but it will compile each of modules. something similar when the production need to be build.
  4. a center maven repo

Problem

  1. if it’s possible to compile the updated module only? actually i want to compile the modified source files only if possible. i know it’s a simple thing by ant or make. however, maven compile always make it from scratch.
  2. should pom.xml in trunk and prod keep the same artifactId and version? the same artifactId and version cannot work with maven:deploy because trunk and prod will overwrite each others deployed packages.
Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You can try to use the mvn -am -pl option which will limit the operation to a given module. 

    +-- root (pom.xml)
     +-- client (pom.xml) dep: core
     +-- server (pom.xml) dep: client
     +-- core (pom.xml) 
     +-- cli (pom.xml) dep:core

    If you do a 

    mvn -am -pl server LifeCycle

    only the server module and the modules which are used by the server will be run through the appropriate lifecycle.

    mvn -am -pl cli LifeCycle

    Only the cli module and the core module in this case will be run throught the given lifecycle.

    • 0