Details
-
Task
-
Resolution: Fixed
-
Neutral
-
None
-
None
-
-
Empty show more show less
-
Empty show more show less
-
Basel 36
-
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:
- publish snapshot versions with jenkins build-number - 1.0.0-build-1, 1.0.0-build-2
- publish snapshot versions with unix-timestamp - 1.0.0-SNAPSHOT-1457532202
The final version won't need an identifier, according to http://semver.org/:
Example: 1.0.0-alpha < 1.0.0-alpha.1 < 1.0.0-alpha.beta < 1.0.0-beta < 1.0.0-beta.2 < 1.0.0-beta.11 < 1.0.0-rc.1 < 1.0.0.
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:
https://docs.npmjs.com/misc/semver#prerelease-tags
http://blog.npmjs.org/post/77758351673/no-more-npm-publish-f
https://github.com/npm/npm-registry-couchapp/issues/148
http://nolanlawson.com/2014/09/01/the-limitations-of-semantic-versioning/
Checklists
Attachments
Issue Links
- is depended upon by
-
MTE-78 Integrate light-module-maven-plugin into templating kit
-
- Closed
-
- relates to
-
LMPLUGIN-6 Improve version conversion between Magnolia and SemVer
-
- Open
-
- mentioned in
-
Page Loading...