[JBoss JIRA] (JBIDE-21497) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Server]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21497:
----------------------------------
Summary: For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Server]
Key: JBIDE-21497
URL: https://issues.jboss.org/browse/JBIDE-21497
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: server
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.Beta2 [Server]: Please perform the following tasks:
0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
[Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|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 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
*NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta2-SNAPSHOT</version>
</parent>
{code}
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
{code}
4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
git checkout -b jbosstools-4.3.1.Beta2x
git push origin jbosstools-4.3.1.Beta2x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
{code}
6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.CR1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
* *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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 Server task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3584) For JBDS 9.1.0.Beta2: Code Freeze + Branch
by Nick Boldt (JIRA)
Nick Boldt created JBDS-3584:
--------------------------------
Summary: For JBDS 9.1.0.Beta2: Code Freeze + Branch
Key: JBDS-3584
URL: https://issues.jboss.org/browse/JBDS-3584
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: installer
Reporter: Nick Boldt
Priority: Blocker
Fix For: 9.1.0.Beta2
For JBDS 9.1.0.Beta2: Please perform the following tasks:
0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
[Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|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 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
*NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta2-SNAPSHOT</version>
</parent>
{code}
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
{code}
4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
git checkout -b jbosstools-4.3.1.Beta2x
git push origin jbosstools-4.3.1.Beta2x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
{code}
6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.CR1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
* *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21491) For JBIDE 4.3.1.Beta2: Code Freeze + Branch
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21491:
----------------------------------
Summary: For JBIDE 4.3.1.Beta2: Code Freeze + Branch
Key: JBIDE-21491
URL: https://issues.jboss.org/browse/JBIDE-21491
Project: Tools (JBoss Tools)
Issue Type: Task
Components: build
Reporter: Nick Boldt
Priority: Blocker
Fix For: 4.3.1.Beta2
For JBIDE 4.3.1.Beta2: Please perform the following tasks:
0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
[Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|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 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
*NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta2-SNAPSHOT</version>
</parent>
{code}
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
{code}
4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
git checkout -b jbosstools-4.3.1.Beta2x
git push origin jbosstools-4.3.1.Beta2x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
{code}
6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.CR1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
* *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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-3584
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21492) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Aerogear]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21492:
----------------------------------
Summary: For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Aerogear]
Key: JBIDE-21492
URL: https://issues.jboss.org/browse/JBIDE-21492
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: aerogear-hybrid, cordovasim
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.Beta2 [Aerogear]: Please perform the following tasks:
0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
[Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|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 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
*NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta2-SNAPSHOT</version>
</parent>
{code}
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
{code}
4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
git checkout -b jbosstools-4.3.1.Beta2x
git push origin jbosstools-4.3.1.Beta2x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
{code}
6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.CR1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
* *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21493) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Central Discovery]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21493:
----------------------------------
Summary: For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Central Discovery]
Key: JBIDE-21493
URL: https://issues.jboss.org/browse/JBIDE-21493
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: discovery
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.Beta2 [Central Discovery]: Please perform the following tasks:
0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
[Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|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 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
*NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta2-SNAPSHOT</version>
</parent>
{code}
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
{code}
4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
git checkout -b jbosstools-4.3.1.Beta2x
git push origin jbosstools-4.3.1.Beta2x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
{code}
6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.CR1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
* *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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 Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21494) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [VPE]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-21494:
----------------------------------
Summary: For JBIDE 4.3.1.Beta2: Code Freeze + Branch [VPE]
Key: JBIDE-21494
URL: https://issues.jboss.org/browse/JBIDE-21494
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: visual-page-editor-core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.1.Beta2 [VPE]: Please perform the following tasks:
0. If nothing has changed in your component since the release of JBoss Tools 4.3.0.Final (eg., Portal, Freemarker?), *{color:red}Reject this JIRA{color}*.
Otherwise:
0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.1.Beta2
[Unresolved JIRAs with fixVersion = 4.3.1.Beta2, 9.1.0.Beta2|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 4.3.0 to 4.3.1, 1.2.3 to 1.2.100, or 2.3.100 to 2.3.101
*NOTE:* If you already did this earlier when we were preparing for Beta2 (after 4.3.0.Final was released), 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.3.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.24.0:set-version -DnewVersion=4.3.1-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.1.Beta2-SNAPSHOT.
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.Beta2-SNAPSHOT</version>
</parent>
{code}
3a. Ensure you've *built your code* using the latest *minimum* target platform version 4.50.2.Beta2-SNAPSHOT (4.50 = Eclipse Mars.0)
{code}
mvn clean verify -Dtpc.version=4.50.2.Beta2-SNAPSHOT
{code}
3b. Ensure you've *run your tests* using the latest *maximum* target platform version 4.52.0.Beta2-SNAPSHOT (4.52 = Eclipse Mars.2)
{code}
mvn clean verify -Dtpc.version=4.52.0.Beta2-SNAPSHOT
{code}
4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch;
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
git checkout -b jbosstools-4.3.1.Beta2x
git push origin jbosstools-4.3.1.Beta2x
{code}
5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}jbosstools-4.3.x branch{color}*.
{code}
git checkout jbosstools-4.3.x
git pull origin jbosstools-4.3.x
{code}
6. Update your *{color:orange}jbosstools-4.3.x branch{color}* parent pom to use the latest version, *{color:orange}4.3.1.CR1-SNAPSHOT{color}*:
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.1.CR1-SNAPSHOT</version>
</parent>
{code}
Now, your root pom will use parent pom version:
* *{color:blue}4.3.1.Beta2-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta2x{color}* branch, and
* *{color:orange}4.3.1.CR1-SNAPSHOT{color}* in your *{color:orange}jbosstools-4.3.x{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 VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21377) Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21377:
-------------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-central/pull/371, https://github.com/jbosstools/jbosstools-central/pull/370, https://github.com/jbdevstudio/jbdevstudio-product/pull/361, https://github.com/jbdevstudio/jbdevstudio-product/pull/362, https://github.com/jbosstools/jbosstools-build-sites/pull/213, https://github.com/jbosstools/jbosstools-build-sites/pull/214
Ye Olde PRs What Require Review:
https://github.com/jbosstools/jbosstools-central/pull/371 (master)
https://github.com/jbosstools/jbosstools-central/pull/370 (4.3.x)
https://github.com/jbdevstudio/jbdevstudio-product/pull/361 (master)
https://github.com/jbdevstudio/jbdevstudio-product/pull/362 (4.3.x)
https://github.com/jbosstools/jbosstools-build-sites/pull/213 (master)
https://github.com/jbosstools/jbosstools-build-sites/pull/214 (4.3.x)
> Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21377
> URL: https://issues.jboss.org/browse/JBIDE-21377
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: updatesite
> Affects Versions: 4.3.1.Beta1
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
> Attachments: jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, jbtcentral-p2diff_460.txt
>
>
> There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default.
> This would require adding it to the TP and adding a dependency from a JBT feature to it.
> On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny])
> --
> Story points - 8 (fibonacci):
> * update Central TP,
> * update JBT/JBDS TPs,
> * update JBT/JBDS category.xml files,
> * update JBDS feature.xml,
> * send announcement email re: TP changes
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months