[JBoss JIRA] (JBIDE-21498) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Hibernate]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21498?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-21498.
----------------------------------
Resolution: Done
> For JBIDE 4.3.1.Beta2: Code Freeze + Branch [Hibernate]
> -------------------------------------------------------
>
> Key: JBIDE-21498
> URL: https://issues.jboss.org/browse/JBIDE-21498
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: hibernate
> Reporter: Nick Boldt
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta2
>
>
> For JBIDE 4.3.1.Beta2 [Hibernate]: 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 Hibernate 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-21406) Create and use Mars.2 RC1 target platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21406?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-21406 at 1/21/16 4:23 PM:
-------------------------------------------------------------
egit mirror pulled: http://download.jboss.org/jbosstools/updates/requirements/egit/v4.1.1.201...
PR to replace 4.0.3 with 4.1.1 in 4.52.0.Beta2 TP:
https://github.com/jbosstools/jbosstools-target-platforms/pull/191
p2diff:
[^p2diff.egit.summary.txt]
PR applied. Building: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstoolstargetplat... >=507
was (Author: nickboldt):
egit mirror pulled: http://download.jboss.org/jbosstools/updates/requirements/egit/v4.1.1.201...
PR to replace 4.0.3 with 4.1.1 in 4.52.0.Beta2 TP:
https://github.com/jbosstools/jbosstools-target-platforms/pull/191
> Create and use Mars.2 RC1 target platform
> -----------------------------------------
>
> Key: JBIDE-21406
> URL: https://issues.jboss.org/browse/JBIDE-21406
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.3.1.Beta2
>
> Attachments: jbds-tp-p2diff-450-summary.txt, jbds-tp-p2diff-450.txt, jbds-tp-p2diff-summary.txt, jbds-tp-p2diff.txt, jbt-tp-p2diff-450-summary.txt, jbt-tp-p2diff-450.txt, jbt-tp-p2diff-summary.txt, jbt-tp-p2diff.txt, jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, p2diff.egit.summary.txt, rc1-rc1a.p2diff-filtered.txt, rc1-rc1a.p2diff.txt
>
>
> Prepare new 4.52.x TPs to use Mars.2 bits.
> https://wiki.eclipse.org/index.php?title=Mars/Simultaneous_Release_Plan#M...
> First RC1 bits should be available on Jan 20 (4.3.1.Beta2 TP freeze day), with EPP bundles needed for install tests on Jan 21 (code freeze day).
> Story points: 21 (fibonacci)
> * jbt tp,
> * jbds tp,
> * central tp;
> * jbt-build-sites,
> * jbds site build
> * update install/matrix jobs to use new Eclipse JEE/platform binary
> * mailing list announcements
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21406) Create and use Mars.2 RC1 target platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21406?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-21406:
-------------------------------
Attachment: p2diff.egit.summary.txt
> Create and use Mars.2 RC1 target platform
> -----------------------------------------
>
> Key: JBIDE-21406
> URL: https://issues.jboss.org/browse/JBIDE-21406
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.3.1.Beta2
>
> Attachments: jbds-tp-p2diff-450-summary.txt, jbds-tp-p2diff-450.txt, jbds-tp-p2diff-summary.txt, jbds-tp-p2diff.txt, jbt-tp-p2diff-450-summary.txt, jbt-tp-p2diff-450.txt, jbt-tp-p2diff-summary.txt, jbt-tp-p2diff.txt, jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, p2diff.egit.summary.txt, rc1-rc1a.p2diff-filtered.txt, rc1-rc1a.p2diff.txt
>
>
> Prepare new 4.52.x TPs to use Mars.2 bits.
> https://wiki.eclipse.org/index.php?title=Mars/Simultaneous_Release_Plan#M...
> First RC1 bits should be available on Jan 20 (4.3.1.Beta2 TP freeze day), with EPP bundles needed for install tests on Jan 21 (code freeze day).
> Story points: 21 (fibonacci)
> * jbt tp,
> * jbds tp,
> * central tp;
> * jbt-build-sites,
> * jbds site build
> * update install/matrix jobs to use new Eclipse JEE/platform binary
> * mailing list announcements
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21521) Port Forwarding: Caching of checkbox for free port does not work properly
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21521?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-21521:
-----------------------------------
Fix Version/s: 4.3.1.Beta2
4.4.0.Alpha1
Assignee: Viacheslav Kabanovich
Resolution: Done
Applied in master / 4.3.x. Thanks Slava!
> Port Forwarding: Caching of checkbox for free port does not work properly
> -------------------------------------------------------------------------
>
> Key: JBIDE-21521
> URL: https://issues.jboss.org/browse/JBIDE-21521
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Assignee: Viacheslav Kabanovich
> Labels: openshift_v3, port_forwarding_wizard
> Fix For: 4.3.1.Beta2, 4.4.0.Alpha1
>
>
> In JBIDE-21123 was fixed caching of the checkbox for usage of free ports in case of inactivity of port forwarding. But upon checking the checkbox to use free ports and start port forwarding, closing wizard and reopening port forwarding wizard, port forwarding is still active using free ports but the checkbox is unchecked.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21503) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [JST]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21503?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-21503.
----------------------------------
Resolution: Done
> For JBIDE 4.3.1.Beta2: Code Freeze + Branch [JST]
> -------------------------------------------------
>
> Key: JBIDE-21503
> URL: https://issues.jboss.org/browse/JBIDE-21503
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta2
>
>
> For JBIDE 4.3.1.Beta2 [JST]: 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 JST 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-21502) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [JavaEE]
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21502?page=com.atlassian.jira.plugi... ]
Alexey Kazakov closed JBIDE-21502.
----------------------------------
Resolution: Done
> For JBIDE 4.3.1.Beta2: Code Freeze + Branch [JavaEE]
> ----------------------------------------------------
>
> Key: JBIDE-21502
> URL: https://issues.jboss.org/browse/JBIDE-21502
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: cdi, cdi-extensions, jsf, seam2
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta2
>
>
> For JBIDE 4.3.1.Beta2 [JavaEE]: 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 JavaEE 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)
[ https://issues.jboss.org/browse/JBDS-3584?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-3584.
----------------------------
Assignee: Nick Boldt
Resolution: Done
> 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
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> 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-21496) For JBIDE 4.3.1.Beta2: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21496?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-21496.
------------------------------
Assignee: Nick Boldt
Resolution: Done
> For JBIDE 4.3.1.Beta2: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21496
> URL: https://issues.jboss.org/browse/JBIDE-21496
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta2
>
>
> For JBIDE 4.3.1.Beta2 [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]: 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 build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch 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 Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21377:
----------------------------------------
It all makes sense what Mickael is saying. But are we sure about that Yaml editor quality? JSON Editor is contributed to Elclipse SSE project and we now have much more control on it. We didn't include it into TP before that contribution (well we still wait for the next SSE build to include it).
So if this Yaml Editor is tested and looks good to us then I would +1 to install it by default. Otherwise it would be safer to keep it optional via a central connection until we test it.
But maybe [~maxandersen] has a different opinion.
> 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
[JBoss JIRA] (JBIDE-21406) Create and use Mars.2 RC1 target platform
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21406?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-21406:
------------------------------------
egit mirror pulled: http://download.jboss.org/jbosstools/updates/requirements/egit/v4.1.1.201...
PR to replace 4.0.3 with 4.1.1 in 4.52.0.Beta2 TP:
https://github.com/jbosstools/jbosstools-target-platforms/pull/191
> Create and use Mars.2 RC1 target platform
> -----------------------------------------
>
> Key: JBIDE-21406
> URL: https://issues.jboss.org/browse/JBIDE-21406
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.3.1.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.3.1.Beta2
>
> Attachments: jbds-tp-p2diff-450-summary.txt, jbds-tp-p2diff-450.txt, jbds-tp-p2diff-summary.txt, jbds-tp-p2diff.txt, jbt-tp-p2diff-450-summary.txt, jbt-tp-p2diff-450.txt, jbt-tp-p2diff-summary.txt, jbt-tp-p2diff.txt, jbtcentral-p2diff-summary.txt, jbtcentral-p2diff.txt, rc1-rc1a.p2diff-filtered.txt, rc1-rc1a.p2diff.txt
>
>
> Prepare new 4.52.x TPs to use Mars.2 bits.
> https://wiki.eclipse.org/index.php?title=Mars/Simultaneous_Release_Plan#M...
> First RC1 bits should be available on Jan 20 (4.3.1.Beta2 TP freeze day), with EPP bundles needed for install tests on Jan 21 (code freeze day).
> Story points: 21 (fibonacci)
> * jbt tp,
> * jbds tp,
> * central tp;
> * jbt-build-sites,
> * jbds site build
> * update install/matrix jobs to use new Eclipse JEE/platform binary
> * mailing list announcements
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months