[magnolia-dev] [JIRA] (LMPLUGIN-2) Versioning and deployment for SNAPSHOT and FINAL versions

[JIRA (on behalf of Espen Jervidalo)]

Title: Message Title

Espen Jervidalo updated an issue   Magnolia Light Module Maven Plugin / LMPLUGIN-2 Versioning and deployment for SNAPSHOT and FINAL versions Change By: Espen Jervidalo 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/: bq. 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/ Add Comment   This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) ---------------------------------------------------------------- For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com> ----------------------------------------------------------------