StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I think the important thing to realize is that in a multi-module build, maven <em>always</em> uses the the version that is from your <em>local repository</em>. This applies in multi-module builds too! So when you reference the "parent" pom you're getting the published parent artifact from your local maven repository. So when you do <strong>mvn install</strong> you repeatedly publish each module to your local repo.</p> <p>While developing, <em>your own modules</em> are probably versioned to something like X.X-SNAPSHOT. The reference to the parent-pom is X.X-SNAPSHOT. Don't change these before you're ready to release. </p> <p>So a simple case would be: Before initial release all modules are called 1.0-SNAPSHOT. When makin the initial release "golden build", rename all 1.0-SNAPSHOT modules to 1.0. When starting development on the 1.1 release, you change all version numbers to 1.1-SNAPSHOT. And so on...</p> <p>The custom is to work with snapshot versions until you're releasing, at which point you update the version numbers everywhere. In the day-to-day development you do not change the version numbers because snapshot-releases get treated differently than hard-version releases.</p> <p><strong>Edit:</strong> After some thought I think some of your confusion in the "comments" section arises from this: The version number in your pom reflects the overall <em>application version</em>. Any given <em>pom</em> change does not necessarily change the <em>application</em> version number. If you need to track changes in the pom I would suggest you use a source control system. So in the 3 month period you work on version 1.0, it's reasonable to keep the version number at 1.0-SNAPSHOT. In the (for instance) 3 week period you work on 1.1, the version number is 1.1-SNAPSHOT. </p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

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