[JBoss JIRA] (JBIDE-17757) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [JBT Update Sites]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-17757:
----------------------------------
Summary: For JBIDE 4.2.0.Beta3: Code Freeze + Branch [JBT Update Sites]
Key: JBIDE-17757
URL: https://issues.jboss.org/browse/JBIDE-17757
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: updatesite
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.Beta3 [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), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3
[Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], 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.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Beta3-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT;
{code}
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)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.2.0.Beta3x
git push origin jbosstools-4.2.0.Beta3x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Beta3-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and
* *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JBT Update Sites task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17759) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Hibernate]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-17759:
----------------------------------
Summary: For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Hibernate]
Key: JBIDE-17759
URL: https://issues.jboss.org/browse/JBIDE-17759
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: hibernate
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.Beta3 [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), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3
[Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], 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.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Beta3-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT;
{code}
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)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.2.0.Beta3x
git push origin jbosstools-4.2.0.Beta3x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Beta3-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and
* *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17761) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [OpenShift]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-17761:
----------------------------------
Summary: For JBIDE 4.2.0.Beta3: Code Freeze + Branch [OpenShift]
Key: JBIDE-17761
URL: https://issues.jboss.org/browse/JBIDE-17761
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.Beta3 [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), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3
[Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], 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.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Beta3-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT;
{code}
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)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.2.0.Beta3x
git push origin jbosstools-4.2.0.Beta3x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Beta3-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and
* *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17760) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Base]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-17760:
----------------------------------
Summary: For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Base]
Key: JBIDE-17760
URL: https://issues.jboss.org/browse/JBIDE-17760
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core, usage
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.Beta3 [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), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3
[Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], 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.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Beta3-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT;
{code}
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)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.2.0.Beta3x
git push origin jbosstools-4.2.0.Beta3x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Beta3-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and
* *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Base task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17753) For JBIDE 4.2.0.Beta3: Code Freeze + Branch
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-17753:
----------------------------------
Summary: For JBIDE 4.2.0.Beta3: Code Freeze + Branch
Key: JBIDE-17753
URL: https://issues.jboss.org/browse/JBIDE-17753
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Nick Boldt
Priority: Blocker
Fix For: 4.2.0.Beta3
For JBIDE 4.2.0.Beta3: 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), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3
[Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], 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.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Beta3-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT;
{code}
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)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.2.0.Beta3x
git push origin jbosstools-4.2.0.Beta3x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Beta3-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and
* *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
See also: JBDS-3081
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17741) Embeddable cartridges description is not decorated
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17741?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-17741:
----------------------------------
Priority: Minor (was: Major)
> Embeddable cartridges description is not decorated
> --------------------------------------------------
>
> Key: JBIDE-17741
> URL: https://issues.jboss.org/browse/JBIDE-17741
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Priority: Minor
> Attachments: cartridges_decorator.png
>
>
> Description label of the embeddable cartridges are not styled (decorated). This text should be styled (decorated) as it was in the previous versions, bcs. it is only description, not the cartridge name (or at least, it's internal cartridge name and it is not appropriate to show it to the users like this).
> !cartridges_decorator.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17754) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Aerogear]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-17754:
----------------------------------
Summary: For JBIDE 4.2.0.Beta3: Code Freeze + Branch [Aerogear]
Key: JBIDE-17754
URL: https://issues.jboss.org/browse/JBIDE-17754
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: aerogear-hybrid
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.Beta3 [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), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3
[Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], 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.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Beta3-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT;
{code}
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)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.2.0.Beta3x
git push origin jbosstools-4.2.0.Beta3x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Beta3-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and
* *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Aerogear task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17755) For JBIDE 4.2.0.Beta3: Code Freeze + Branch [JST]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-17755:
----------------------------------
Summary: For JBIDE 4.2.0.Beta3: Code Freeze + Branch [JST]
Key: JBIDE-17755
URL: https://issues.jboss.org/browse/JBIDE-17755
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.2.0.Beta3 [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), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3
[Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], 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.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Beta3-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT;
{code}
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)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.2.0.Beta3x
git push origin jbosstools-4.2.0.Beta3x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Beta3-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and
* *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17741) Embeddable cartridges description is not decorated
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17741?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-17741:
----------------------------------
Issue Type: Enhancement (was: Bug)
> Embeddable cartridges description is not decorated
> --------------------------------------------------
>
> Key: JBIDE-17741
> URL: https://issues.jboss.org/browse/JBIDE-17741
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.2.0.Beta3
> Reporter: Marián Labuda
> Attachments: cartridges_decorator.png
>
>
> Description label of the embeddable cartridges are not styled (decorated). This text should be styled (decorated) as it was in the previous versions, bcs. it is only description, not the cartridge name (or at least, it's internal cartridge name and it is not appropriate to show it to the users like this).
> !cartridges_decorator.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBDS-3081) For JBDS 8.0.0.Beta3: Code Freeze + Branch
by Nick Boldt (JIRA)
Nick Boldt created JBDS-3081:
--------------------------------
Summary: For JBDS 8.0.0.Beta3: Code Freeze + Branch
Key: JBDS-3081
URL: https://issues.jboss.org/browse/JBDS-3081
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Security Level: Public (Everyone can see)
Components: installer
Reporter: Nick Boldt
Priority: Blocker
Fix For: 8.0.0.Beta3
For JBDS 8.0.0.Beta3: 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), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.Beta3
[Unresolved JIRAs with fixVersion = 4.2.0.Beta3, 8.0.0.Beta3|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], 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.
{code}
mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.17.0:set-version -DnewVersion=1.0.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.2.0.Beta3-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Beta3-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.Beta3-SNAPSHOT;
{code}
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)
{code}
4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.2.0.Beta3x
git push origin jbosstools-4.2.0.Beta3x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
{code}
git checkout master
git pull origin master
{code}
6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.Beta3-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.2.0.Beta3-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.0.Beta3x{color}* branch, and
* *{color:orange}4.2.0.Beta3-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
7. Close (do not resolve) this JIRA when done.
8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months