Allow module updates for beta releases

Description

Currently users need to reinstall the software with each new beta release. The project setup must be changed to make it possible to update the modules via the NetBeans auto update service.

The problem right now is that the auto update service only considers the specification version for comparing the module version. The specification version can only handle version numbers of final releases, e.g. '2.0.0'. This is considered by the maven-nbm-plugin which uses the pom version but strips of the snapshot part. This makes a snapshot version equal to the release version.

Environment

None

GitHub Work

None

Activity

Show:

Tonio Fincke20 November 2015 at 14:40

change fix version

Olga Faber16 November 2015 at 09:14

ok

Marco Peters21 September 2015 at 13:50

the OpenIDE-Module-Specification-Version attribute in the manifest is now set to a version which is defined by a property in the pom.xml. The property is used to filter the manifest file.
The version is increased with each update.

Marco Peters13 August 2015 at 13:22

A possible solution might be:

  • The maven filter functionality can be used to set the OpenIDE-Module-Specification-Version attribute in the manifest.mf file. The value can be defined by a property defined in the pom file. This can be any value e.g. 999.20150726. The nbm-plugin will not replace the value if it already exist.

  • We have a special development module repository which is used during the beta phase.

  • For the final release we switch to a stable module repository. An there we use the correct version number of the final release.

This way it is only necessary to reinstall SNAP only for the final release, but not for every beta release.

Fixed

Details

Assignee

Reporter

Fix versions

Affects versions

Components

Priority

Created 13 August 2015 at 13:11
Updated 20 November 2015 at 14:40
Resolved 20 November 2015 at 14:40

Flag notifications