-
Task
-
Resolution: Done
-
Blocker
-
None
-
NEW
For JBDS 8.0.0.Beta2: Please perform the following tasks:
0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), Reject this JIRA.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta2
Unresolved JIRAs with fixVersion = 4.2.0.Beta2, 8.0.0.Beta2
1. Ensure your component features/plugins have been properly upversioned, eg., from 1.0.0 to 1.0.1.
NOTE: If you already did this for the previous milestone you do not need to do so again.
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
2. Update your root pom to use parent pom version 4.2.0.Beta2-SNAPSHOT;
<parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.2.0.Beta2-SNAPSHOT</version> </parent>
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT;
mvn clean verify -Dtpc.version=4.40.0.Beta3 # (if the TP is already released) or mvn clean verify -Dtpc.version=4.40.0.Beta3-SNAPSHOT # (if still being staged)
4. Branch from your existing master branch into a new jbosstools-4.2.0.Beta2x branch;
git checkout master git pull origin master git checkout -b jbosstools-4.2.0.Beta2x git push origin jbosstools-4.2.0.Beta2x
5. NOW THAT YOU HAVE BRANCHED, check out your master branch.
git checkout master git pull origin master
6. Update your master branch parent pom to use the latest version, 4.2.0.Beta2-SNAPSHOT:
<parent> <groupId>org.jboss.tools</groupId> <artifactId>parent</artifactId> <version>4.2.0.Beta2-SNAPSHOT</version> </parent>
Now, your root pom will use parent pom version:
- 4.2.0.Beta2-SNAPSHOT in your jbosstools-4.2.0.Beta2x branch, and
- 4.2.0.Beta3-SNAPSHOT in your master branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding New + Noteworthy JIRAs to do, please complete them next.
- is related to
-
JBDS-2212 audit version numbers of features/plugins in JBDS 5.0.0 vs. 4.1.3
- Closed
-
JBDS-3034 add tern.java to JBDS target platform so that it can be resolved when building JBDS update site, including jst.jsdt
- Closed
-
JBDS-3036 update splash and installer graphics for JBDS 8
- Closed
-
JBIDE-16871 use lowercase paths & filenames for JBT & JBDS artifacts
- Closed
-
JBDS-3035 deprecate then remove JBDS audit-versions ant script
- Closed