[LMPLUGIN-2] Versioning and deployment for SNAPSHOT and FINAL versions Created: 09/Mar/16 Updated: 19/Apr/16 Resolved: 23/Mar/16 |
|
| Status: | Closed |
| Project: | Magnolia Light Module Maven Plugin |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 1.0 |
| Type: | Task | Priority: | Neutral |
| Reporter: | Espen Jervidalo | Assignee: | Espen Jervidalo |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Template: |
|
||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||
| Task DoR: |
Empty
|
||||||||||||||||
| Sprint: | Basel 36 | ||||||||||||||||
| Story Points: | 0.5 | ||||||||||||||||
| Description |
|
Update: Nexus3 allows re-publishing packages, so we are able to publish e.g. mtk-0.10.0-snapshot over and over again. This issue lost the importance for now, while we're in testing-mode. Re-publishing in production is another topic. So the ticket is still valid as such. It's not possible to have maven-like development snapshots for npm packages (light modules) - npm is using semantic versioning and their repository does not support re-publishing of packages with same version (meaning it is not possible to publish 1.0.0-SNAPSHOT version multiple times). Some options:
The final version won't need an identifier, according to http://semver.org/:
When fetching the latest package, you won't get alpha or beta-versions in this case. But that's conform with how maven handles this. You will need to pin the version. OTOH release-candidates might be a problem.. build.5 < rc.1 Resources: |