Databases
StackOverflow2013
Postsdbo
PO
 

Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>As far as I know, there is no solution to answer what you asked.</p> <p>You have to keep in mind that multimodule projects (aggregation) means that every submodule share the same application lifecycle. This is <strong>really</strong> what modules and aggregation are intended to.</p> <p>I see 2 differents workarounds.</p> <h2>You have 2 real differents lifecycles</h2> <p>There is indeed 2 groups in your 4 submodules, lets say group1 : A and B, group 2, C and D.</p> <p>Split them into 2 new projects : </p> <pre><code>Group1 |-- Project A | `-- pom.xml |-- Project B | `-- pom.xml `-- pom.xml Group2 |-- Project C | `-- pom.xml |-- Project D | `-- pom.xml `-- pom.xml </code></pre> <p>Pro : You may be able to branch group 1 and 2 separately. Cons : You won't be able anymore to perform simultaneaous action (in one command) on every project (like realeasing or builind them)</p> <h2>You really have 1 single lifecycle</h2> <p>This is probably the case. You may want to branch only 1 or 2 submodules because of your very good understanding of the underlying architecture of the project. An so, you don't want to deal with too many conf / artifacts / time building ... Indeed, all those reasons may have indirects impacts that you won't see. Always build the whole project !</p> <p>If this is for space saving (however most of SCM allow you to branch with few space, like Yorkw said), because your SCM allow you to get only submodules (and maybe both, like for Clearcase) ... sorry, there is no solution. This is the maven way, and I think this is the good one. (ok it's a little bit demagogic, but I really believe what I said)</p> <p><strong>Don't hesitate to explain us why you really want to branch only a subset of your modules.</strong> If there is another reason, you may have more accurate(s) solution(s).</p>
    singulars
    1. This table or related slice is empty.
    1. POmaven use release:branch to branch select modules
      singulars
      1. PTQuestion
    1. PTAnswer
    1. This table or related slice is empty.
    1. USJean-Rémy Revy
    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. This table or related slice is empty.
    1. This table or related slice is empty.
    1. COThanks for the response. Judging by your answer, I really think my situation is closer to your first scenario - different lifecycles. However, I was hesitant to group together into common folders since there are quite a few *shared* modules between 2 lifecycles. Hence, I could not figure out how a branch requiring some shared modules and some modules from other lifecycle would look like. Any recommendations on that.. ? I edited my original question explaining the background.
      singulars
      1. PO
      1. USAnand Hemmige
    2. COProject A and B are commmon dependencies, used by project C and D ? Like A = model, B = ejb/services, C = war and D = ear ? Like this ?
      singulars
      1. PO
      1. USJean-Rémy Revy
 

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