Step 1 of 4: Choose Issues

Cancel

Key Summary Description
JBIDE-16244

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Central Discovery]

For JBIDE 4.2.0.Alpha1 [Central Discovery]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for Central Discovery task JIRA

JBIDE-16243

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Freemarker]

For JBIDE 4.2.0.Alpha1 [Freemarker]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for Freemarker task JIRA

JBIDE-16242

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Portlet]

For JBIDE 4.2.0.Alpha1 [Portlet]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for Portlet task JIRA

JBIDE-16241

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Central]

For JBIDE 4.2.0.Alpha1 [Central]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for Central task JIRA

JBIDE-16240

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Arquillian]

For JBIDE 4.2.0.Alpha1 [Arquillian]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for Arquillian task JIRA

JBIDE-16239

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Webservices]

For JBIDE 4.2.0.Alpha1 [Webservices]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for Webservices task JIRA

JBIDE-16238

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Forge]

For JBIDE 4.2.0.Alpha1 [Forge]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for Forge task JIRA

JBIDE-16237

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [GWT]

For JBIDE 4.2.0.Alpha1 [GWT]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for GWT task JIRA

JBIDE-16236

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Birt]

For JBIDE 4.2.0.Alpha1 [Birt]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for Birt task JIRA

JBIDE-16235

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JavaEE]

For JBIDE 4.2.0.Alpha1 [JavaEE]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for JavaEE task JIRA

JBIDE-16234

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [OpenShift]

For JBIDE 4.2.0.Alpha1 [OpenShift]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for OpenShift task JIRA

JBIDE-16233

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Base]

For JBIDE 4.2.0.Alpha1 [Base]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

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

JBIDE-16232

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Hibernate]

For JBIDE 4.2.0.Alpha1 [Hibernate]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for Hibernate task JIRA

JBIDE-16231

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Server]

For JBIDE 4.2.0.Alpha1 [Server]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for Server task JIRA

JBIDE-16230

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JBT Update Sites]

For JBIDE 4.2.0.Alpha1 [JBT Update Sites]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for JBT Update Sites task JIRA

JBIDE-16229

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [VPE]

For JBIDE 4.2.0.Alpha1 [VPE]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for VPE task JIRA

JBIDE-16228

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [JST]

For JBIDE 4.2.0.Alpha1 [JST]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for JST task JIRA

JBIDE-16227

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [Aerogear]

For JBIDE 4.2.0.Alpha1 [Aerogear]: 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.Alpha1

Unresolved JIRAs with fixVersion = 4.2.0.Alpha1, 8.0.0.Alpha1

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for Aerogear task JIRA

JBIDE-16217

JBIDE-16226 For JBIDE 4.2.0.Alpha1: Code Freeze + Branch [LiveReload]

For JBIDE 4.2.0.Alpha1: Please perform the following tasks:

0. If nothing has changed in your component since the last milestone or GA release on this branch, Reject this JIRA.

Otherwise:

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

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

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.Alpha1-SNAPSHOT;

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

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

mvn clean verify -Dtpc.version=4.40.0.Alpha1  # (if the TP is already released)
  or
mvn clean verify -Dtpc.version=4.40.0.Alpha1-SNAPSHOT # (if still being staged)

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

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

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

Search for all task JIRA, or Search for LiveReload task JIRA

Cancel