Databases
StackOverflow2013
Postsdbo
POmaven use release:branch to branch select modules
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POmaven use release:branch to branch select modules
    primarykey
    data
    text
    <p>I have a maven multi module project like so </p> <pre><code>modA modB modC modD custom-pom.xml </code></pre> <p>And here the pom </p> <pre class="lang-xml prettyprint-override"><code>&lt;project&gt; &lt;modelVersion&gt;4.0.0&lt;/modelVersion&gt; &lt;groupId&gt;com.xx.xx.correspondence&lt;/groupId&gt; &lt;artifactId&gt;xxHudsonTP&lt;/artifactId&gt; &lt;version&gt;1&lt;/version&gt; &lt;packaging&gt;pom&lt;/packaging&gt; &lt;modules&gt; &lt;module&gt;modA&lt;/module&gt; &lt;module&gt;modB&lt;/module&gt; &lt;/modules&gt; &lt;/project&gt; </code></pre> <p>Now, when I invoke release:branch with the intent of creating a branch on custom-pom.xml like so </p> <pre><code>mvn release:branch -DbranchName=new-branch -f custom-pom.xml </code></pre> <p>It ends up creating a branch with all 4 modules. </p> <p>Is there any way using release plugin to make sure only selected modules are branched without resorting to branching each module separately.? </p> <p>Any other maven plugins..? </p> <p><strong>Edited</strong> The background of this questions stems from the fact that the svn repo that I am working with has about 20 different modules with 4 different artifacts that they need to generate. I could have easily gone with grouping the modules into sub folders, but since a few modules are common between the artifacts, I didn't think too much into splitting them up. </p> <p>I understand that branching all modules is trivial and probably simple to manage, but the other developers in the team have this feeling of dealing with too much for accomplishing simple tasks like a one line bug fix. Hope that helps. </p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USAnand Hemmige
    1. USAnand Hemmige
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POmaven use release:branch to branch select modules
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POmaven use release:branch to branch select modules
      1. This table or related slice is empty.
      1. VTApproveEditSuggestion
    1. COIt is recommended to use `<profiles>` instead of `-f custom-pom.xml`, see [here](http://maven.apache.org/guides/introduction/introduction-to-profiles.html) for more details.
      singulars
      1. POmaven use release:branch to branch select modules
      1. USyorkw
    2. COWhat is wrong with branching all the modules at once? Most Version Control systems make branching almost "free" in terms of storage and management. Also, Maven doesn't really play well when you try and "trick" it into doing things it doesn't like.
      singulars
      1. POmaven use release:branch to branch select modules
      1. USToby Jackson
    3. CO@yorkw - thats a good idea. +1 for that..
      singulars
      1. POmaven use release:branch to branch select modules
      1. USAnand Hemmige
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload