[JBoss JIRA] (JBDS-3404) Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3404?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3404:
-------------------------------------
Pavol, to get it working you have to add latest central to list of update sites. This central p2 repo should contain JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha2-SOMETHING that requires the same Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822.
That I guess because Tern Project Adapter declared as inclusion in JBoss Tools Java Standard Tools AngularJS where it should be dependency with Equal or Greater match rule. I'll send PR for that later today.
> Cannot update from JBDS 9.0.0.Alpha1 to Alpha2 (nightly)
> --------------------------------------------------------
>
> Key: JBDS-3404
> URL: https://issues.jboss.org/browse/JBDS-3404
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: build
> Affects Versions: 9.0.0.Alpha1
> Reporter: Pavol Srna
> Priority: Blocker
> Fix For: 9.0.0.Alpha2
>
> Attachments: Screenshot 2015-04-13 14.03.50.png, Screenshot 2015-04-13 14.12.04.png, Screenshot 2015-04-16 15.36.03.png, Screenshot 2015-04-16 15.36.38.png
>
>
> When you do Check for update, only thym update is offered:
> !Screenshot 2015-04-13 14.03.50.png!
> Output when you do Install/Check All
> {code}
> Your original request has been modified.
> "Java EE Batch Configuration Tools" is already installed, so an update will be performed instead.
> "JBoss JAX-RS Tools" is already installed, so an update will be performed instead.
> "JBoss Maven Hibernate Configurator" is already installed, so an update will be performed instead.
> "Apache Deltaspike Tools" is already installed, so an update will be performed instead.
> "JBoss Developer Studio (Core Features)" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation" is already installed, so an update will be performed instead.
> "JBoss Tools JDT Extensions" is already installed, so an update will be performed instead.
> "JBoss Maven CDI Configurator" is already installed, so an update will be performed instead.
> "JBoss Maven Portlet Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools RichFaces" is already installed, so an update will be performed instead.
> "JBoss Maven Endorsed Libraries Configurator" is already installed, so an update will be performed instead.
> "JBoss Tools Foundation Security for Linux" is already installed, so an update will be performed instead.
> "JBoss Maven Project Examples" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools Tern.java Adapter" is already installed, so an update will be performed instead.
> "JMX Console" is already installed, so an update will be performed instead.
> "JBoss OpenShift v2 Tools" is already installed, so an update will be performed instead.
> "JBoss Tools JSF" is already installed, so an update will be performed instead.
> "Seam Tools" is already installed, so an update will be performed instead.
> "Hybrid Mobile Application Development Tools" is already installed, so an update will be performed instead.
> "JBoss Archives Tools" is already installed, so an update will be performed instead.
> "JBoss Stacks Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Java Standard Tools" is already installed, so an update will be performed instead.
> "JBoss Tools Visual Page Editor" is already installed, so an update will be performed instead.
> "Project Examples" is already installed, so an update will be performed instead.
> "JBoss Maven Integration" is already installed, so an update will be performed instead.
> "JBoss Runtime Detection Core" is already installed, so an update will be performed instead.
> "JBoss Tools Apache Tomcat Integration" is already installed, so an update will be performed instead.
> "JBoss WebServices Tools" is already installed, so an update will be performed instead.
> "Hibernate Tools" is already installed, so an update will be performed instead.
> "JBoss Tools LiveReload" is already installed, so an update will be performed instead.
> "JBoss Tools Eclipse Thym Integration" is already installed, so an update will be performed instead.
> "JBoss Tools EGit Integration" is already installed, so an update will be performed instead.
> "JBoss Tools Maven Source Lookup" is already installed, so an update will be performed instead.
> "Forge Tools" is already installed, so an update will be performed instead.
> "Context and Dependency Injection Tools" is already installed, so an update will be performed instead.
> "JBossAS Tools" is already installed, so an update will be performed instead.
> Cannot complete the install because of a conflicting dependency.
> Software being installed: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> Software currently installed: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> Only one of the following can be installed at once:
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt 3.7.0.Alpha2-v20150322-0547-B822)
> JBoss Tools Java Standard Tools - Tern Project Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt 3.7.0.Alpha1-v20150213-0215-B3)
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools AngularJS 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.angularjs.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt.feature.feature.group [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha1-v20150213-0215-B3 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha1-v20150213-0215-B3)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha1-v20150213-0215-B3]
> Cannot satisfy dependency:
> From: JBoss Tools Java Standard Tools Tern.java Adapter 3.7.0.Alpha2-v20150322-0547-B822 (org.jboss.tools.jst.jsdt.feature.feature.group 3.7.0.Alpha2-v20150322-0547-B822)
> To: org.jboss.tools.jst.jsdt [3.7.0.Alpha2-v20150322-0547-B822]
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19615) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Base]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19615:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Base]
Key: JBIDE-19615
URL: https://issues.jboss.org/browse/JBIDE-19615
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core, usage
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha2 [Base]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.0.Alpha2
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.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.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha2x
git push origin jbosstools-4.3.0.Alpha2x
{code}
5. Close (do not resolve) this JIRA when done.
[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.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19616) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [OpenShift]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19616:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [OpenShift]
Key: JBIDE-19616
URL: https://issues.jboss.org/browse/JBIDE-19616
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha2 [OpenShift]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.0.Alpha2
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.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.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha2x
git push origin jbosstools-4.3.0.Alpha2x
{code}
5. Close (do not resolve) this JIRA when done.
[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.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19617) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [JavaEE]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19617:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [JavaEE]
Key: JBIDE-19617
URL: https://issues.jboss.org/browse/JBIDE-19617
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: jsf, cdi-extensions, seam2, cdi
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha2 [JavaEE]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.0.Alpha2
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.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.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha2x
git push origin jbosstools-4.3.0.Alpha2x
{code}
5. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JavaEE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19610) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [JBT Update Sites]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19610:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [JBT Update Sites]
Key: JBIDE-19610
URL: https://issues.jboss.org/browse/JBIDE-19610
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: updatesite
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha2 [JBT Update Sites]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.0.Alpha2
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.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.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha2x
git push origin jbosstools-4.3.0.Alpha2x
{code}
5. Close (do not resolve) this JIRA when done.
[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.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19611) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [VPE]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19611:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [VPE]
Key: JBIDE-19611
URL: https://issues.jboss.org/browse/JBIDE-19611
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: visual-page-editor-core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha2 [VPE]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.0.Alpha2
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.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.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha2x
git push origin jbosstools-4.3.0.Alpha2x
{code}
5. Close (do not resolve) this JIRA when done.
[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.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19612) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Central Discovery]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19612:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Central Discovery]
Key: JBIDE-19612
URL: https://issues.jboss.org/browse/JBIDE-19612
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: discovery
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha2 [Central Discovery]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.0.Alpha2
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.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.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha2x
git push origin jbosstools-4.3.0.Alpha2x
{code}
5. Close (do not resolve) this JIRA when done.
[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.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19613) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Server]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19613:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Server]
Key: JBIDE-19613
URL: https://issues.jboss.org/browse/JBIDE-19613
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: server
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha2 [Server]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.0.Alpha2
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.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.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha2x
git push origin jbosstools-4.3.0.Alpha2x
{code}
5. Close (do not resolve) this JIRA when done.
[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.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19614) For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Hibernate]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19614:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha2: Code Freeze + Branch [Hibernate]
Key: JBIDE-19614
URL: https://issues.jboss.org/browse/JBIDE-19614
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: hibernate
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha2 [Hibernate]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.0.Alpha2
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.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.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha2x
git push origin jbosstools-4.3.0.Alpha2x
{code}
5. Close (do not resolve) this JIRA when done.
[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.3.11#6341)
11 years
[JBoss JIRA] (JBDS-3412) For JBDS 9.0.0.Alpha2: Code Freeze + Branch
by Nick Boldt (JIRA)
Nick Boldt created JBDS-3412:
--------------------------------
Summary: For JBDS 9.0.0.Alpha2: Code Freeze + Branch
Key: JBDS-3412
URL: https://issues.jboss.org/browse/JBDS-3412
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Task
Components: installer
Reporter: Nick Boldt
Priority: Blocker
Fix For: 9.0.0.Alpha2
For JBDS 9.0.0.Alpha2: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.0.Alpha2
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha2, 9.0.0.Alpha2|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.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.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha2-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha2-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha2;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha2-SNAPSHOT # (if the TP is still a SNAPSHOT)
mvn clean verify -Dtpc.version=4.50.0.Alpha2 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha2x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha2x
git push origin jbosstools-4.3.0.Alpha2x
{code}
5. Close (do not resolve) this JIRA when done.
[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.3.11#6341)
11 years