-
Epic
-
Resolution: Done
-
Blocker
-
None
-
Improve version auditing
-
Done
For JBIDE 4.3.0.Alpha1: Please perform the following tasks:
1. Ensure your component features/plugins have been properly upversioned, eg., from 1.0.0 to 1.1.0 or 1.0.100.
Please also ensure that the version of your plugins in the 4.2.x branch is a SMALLER version, to prevent a user from accidentally updating from your Mars version to your Luna version. For example, org.jboss.tools.stacks.core cannot be version 1.1.1 in JBDS 8.0.2, and 1.1.0 in JBDS 9.
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
2. Close (do not resolve) this JIRA when done.
- is related to
-
JBIDE-18848 setup tests for ide-config.properties
- Closed
-
JBDS-3163 change publishing process so that JBDS staging builds go to devstudio.redhat.com instead of www.qa server
- Closed
-
JBIDE-18772 Include publish steps in pom files
- Closed
-
JBIDE-16970 create mechanism to verify that nightly build is different from previous milestone
- Closed
-
JBIDE-18742 Only rely on rsync to publish new aggregate (remove other comparators and checks)
- Closed
-
JBIDE-18743 [release] Testing: write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*)
- Closed
-
JBIDE-18762 Pull description field from a given component's JSON in order to determine its parent project (Python scriptlet?)
- Open
- relates to
-
JBIDE-19729 Version Auditing
- Open
-
JBIDE-19018 JBT Central Discovery staging site contains early access child site in its composite*.xml
- Closed
-
JBIDE-19056 A Mojo to validate a version (compared to baseline)
- Closed