Hi all,
Today is branch/codefreeze day as planned for jbosstools-4.1.1.Alpha1 [1].
Special note:
A. This only involves projects that are included in JBoss Tools Core/Developer Studio, it
is *not* related
to things that are part of JBoss Tools Integration Stack (i.e. bpel, esb, jbpm3, etc.)
B. This is an alpha, mainly to pick up Kepler SR1 fixes and already done
bugfixes/features.
There is no respins or QE planned for this besides "does it install" test.
By request jiras for each component have been created too: see
https://issues.jboss.org/browse/JBIDE-15437 and subtasks.
These jiras contains similar but less details as the instructions below:
0) Make sure your component(s) has no remaining jiras for 4.1.1.Alpha1 in jira.
1) Make sure you component(s) version number has changed micro version if it had changes
since 4.1.0 was released!
You can use this to change it for a subtree:
mvn org.eclipse.tycho:tycho-versions-plugin:set-version
-DnewVersion=<component-version>-SNAPSHOT
2) Make sure your component uses 4.1.1.Alpha1-SNAPSHOT as the version for jboss tools
parent.
Should look something like this:
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.1.1.Alpha1-SNAPSHOT</version>
</parent>
3) Make sure your component builds and passes its tests when run locally.
$ mvn clean verify -Dtpc.version=4.31.0.Alpha1
4) Make a branch for the Alpha1 builds to use.
This would be made on jbosstools-4.1.x, thus the steps would be something like:
$ git checkout jbosstools-4.1.x
$ git pull origin jbosstools-4.1.x
$ git checkout -b jbosstools-4.1.1.Alpha1x
$ git push origin jbosstools-4.1.1.Alpha1x
5) Resolve the jira related to branching for your component or comment on it why it can
not be done.
Thank you!
[1]
https://issues.jboss.org/browse/JBIDE#selectedTab=com.atlassian.jira.plug...
--
/max