XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Blocker Blocker
    • 4.3.0.Alpha1
    • None
    • common, usage

      For JBIDE 4.3.0.Alpha1 [Base]: Please perform the following tasks:

      0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., XulRunner, GWT, Freemarker, BIRT), Reject this JIRA.

      Otherwise:

      0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Alpha1

      Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1

      1. Ensure your component features/plugins have been properly upversioned, eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.

      NOTE: If you already did this for your master branch, you do not need to do so again. Please also ensure that the version of your code in the master branch is greater than your code in the 4.2.x branch.

      mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
      

      2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;

        <parent>
          <groupId>org.jboss.tools</groupId>
          <artifactId>parent</artifactId>
          <version>4.3.0.Alpha1-SNAPSHOT</version>
        </parent>
      

      3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;

      mvn clean verify -Dtpc.version=4.50.0.Alpha1  # (if the TP is already released)
      

      4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;

      git checkout master
      git pull origin master
      git checkout -b jbosstools-4.3.0.Alpha1x
      git push origin jbosstools-4.3.0.Alpha1x
      

      5. Close (do not resolve) this JIRA when done.

      Search for all task JIRA, or Search for Base task JIRA

              alexeykazakov Alexey Kazakov
              nickboldt Nick Boldt
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: