Do you really need to version the trunk of a maven project? -


in trunk based development branching model, develop on trunk , release branch, every release requires updates pom files in both trunk , new branch.

for example, if version in trunk set 1.0-snapshot, release branch needs updated 1.0, , trunk 1.1-snapshot.

i'd alternative strategy preclude need update version on trunk, , associated tasks goes this. thinking it, shouldn't need apply version number trunk. version number becomes relevant during release process, maven (for multitude of reasons) requires version number.

as alternative, set version on trunk 0.0-snapshot, denote special build. problem though, place before every other version, far maven concerned.

an alternative might use large number. @ least place after every other version, true if trunk represents tip of development. feels bit arbitrary though.

the other option can see, use string version - e.g. head or latest, wouldn't conform latest maven versioning scheme. besides losing snapshot functionality, believe integer version considered newer string (see here).

so,

  1. does theory seem sound?
  2. if so, there better strategy out there?

you can use trunk-snapshot if desire. gives "latest" resolution static "version".


Comments

Popular posts from this blog

google api - Incomplete response from Gmail API threads.list -

Installing Android SQLite Asset Helper -

Qt Creator - Searching files with Locator including folder -