[JBoss JIRA] (JBIDE-20976) Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20976?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-20976:
---------------------------------------------
I understand the use of M2 is to ensure we at least have the eclipse platform version higher than our previous release.
What is the reason for updating angularjs ? Have it been requested and verified it does not break our current integration or is this update to perform that work/test ?
> Create and use Neon M2 target platform (was: Versions of 3rd party plugins in JBDS 10 are LESS than in JBDS 9)
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20976
> URL: https://issues.jboss.org/browse/JBIDE-20976
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform, upstream
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.4.0.Alpha1
>
> Attachments: JBIDE20976_NeonM2.png, JBIDE20976_NeonM2_sapphire.png, p2diff-all.txt, p2diff-summary.txt, p2diff.central.summary.txt, p2diff.central.txt, p2diff.ea.summary.txt, p2diff.ea.txt, versionwatch-features.png, versionwatch-plugins.png
>
>
> Opened in JBIDE (not JBDS) because the TPs are essentially the same, so this affects both JBT and JBDS.
> Could be a problem w/ the .target files, or a problem upstream w/ Eclipse projects in Neon not being updated from Mars.0 to their Mars.1 version (or newer).
> Details in these logs:
> http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers...
> http://download.jboss.org/jbosstools/10.0/snapshots/builds/devstudio.vers...
> Affected IUs (now sorted alphabetically):
> {code}
> org.eclipse.core.runtime 3.11.1.v20150903-1804
> org.eclipse.egit 4.0.2.201509141540-r
> org.eclipse.egit.core 4.0.2.201509141540-r
> org.eclipse.egit.doc 4.0.2.201509141540-r
> org.eclipse.egit.ui 4.0.2.201509141540-r
> org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318
> org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318
> org.eclipse.jdt 3.11.1.v20150904-0015
> org.eclipse.jdt.doc.user 3.11.1.v20150819-1130
> org.eclipse.jetty.webapp 9.2.13.v20150730
> org.eclipse.jetty.xml 9.2.13.v20150730
> org.eclipse.jgit 4.0.2.201509141540-r
> org.eclipse.jgit.archive 4.0.2.201509141540-r
> org.eclipse.jst.common.frameworks 1.1.701.v201509021802
> org.eclipse.jst.server.tomcat.core 1.1.701.v201508232356
> org.eclipse.jst.web_core.feature 3.7.1.v201509021802
> org.eclipse.jst.web_ui.feature 3.7.1.v201509021802
> org.eclipse.jst.webpageeditor.feature 2.7.1.v201508270443
> org.eclipse.pde 3.11.1.v20150904-0345
> org.eclipse.pde.doc.user 3.11.1.v20150903-1352
> org.eclipse.platform 4.5.1.v20150904-0015
> org.eclipse.platform.doc.user 4.5.1.v20150819-1130
> org.eclipse.rcp 4.5.1.v20150904-0015
> org.eclipse.sapphire 9.0.1.201509151939
> org.eclipse.sapphire.java 9.0.1.201509151939
> org.eclipse.sapphire.java.jdt 9.0.1.201509151939
> org.eclipse.sapphire.java.jdt.ui 9.0.1.201509151939
> org.eclipse.sapphire.modeling 9.0.1.201509151939
> org.eclipse.sapphire.modeling.xml 9.0.1.201509151939
> org.eclipse.sapphire.osgi 9.0.1.201509151939
> org.eclipse.sapphire.osgi.fragment 9.0.1.201509151939
> org.eclipse.sapphire.platform 9.0.1.201509151939
> org.eclipse.sapphire.ui 9.0.1.201509151939
> org.eclipse.sapphire.ui.swt.gef 9.0.1.201509151939
> org.eclipse.sapphire.ui.swt.xml.editor 9.0.1.201509151939
> org.eclipse.sapphire.workspace 9.0.1.201509151939
> org.eclipse.sapphire.workspace.ui 9.0.1.201509151939
> org.eclipse.swt 3.104.1.v20150825-0743
> org.eclipse.wst.common_core.feature 3.7.1.v201508262220
> org.eclipse.wst.common_ui.feature 3.7.1.v201508262220
> org.eclipse.wst.jsdt.feature 1.6.201.v201508262249
> org.eclipse.wst.server.core 1.7.0.v201508271522
> org.eclipse.wst.server.discovery 1.1.0.v201508271522
> org.eclipse.wst.server.ui 1.5.201.v201509022125
> org.eclipse.wst.server_core.feature 3.3.600.v201508271522
> org.eclipse.wst.server_ui.feature 3.3.600.v201509022125
> org.eclipse.wst.validation 1.2.700.v201508251749
> org.eclipse.wst.web_core.feature 3.7.1.v201508271605
> org.eclipse.wst.web_ui.feature 3.7.1.v201509022125
> org.eclipse.wst.ws_ui.feature 3.7.1.v201508271926
> org.eclipse.wst.xml_ui.feature 3.7.1.v201508271605
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20951) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests]
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20951?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-20951:
---------------------------------------
[~nickboldt], how about this? :) https://github.com/jbosstools/jbosstools-integration-tests/pull/1210
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Integration Tests]
> -------------------------------------------------------------------
>
> Key: JBIDE-20951
> URL: https://issues.jboss.org/browse/JBIDE-20951
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: qa
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Integration Tests]: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, 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 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Integration Tests 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-20963) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Webservices]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20963?page=com.atlassian.jira.plugi... ]
Xavier Coulon closed JBIDE-20963.
---------------------------------
Resolution: Done
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Webservices]
> -------------------------------------------------------------
>
> Key: JBIDE-20963
> URL: https://issues.jboss.org/browse/JBIDE-20963
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: webservices
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Webservices]: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, 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 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices 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-20967) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [LiveReload]
by Xavier Coulon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20967?page=com.atlassian.jira.plugi... ]
Xavier Coulon closed JBIDE-20967.
---------------------------------
Resolution: Done
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [LiveReload]
> ------------------------------------------------------------
>
> Key: JBIDE-20967
> URL: https://issues.jboss.org/browse/JBIDE-20967
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: livereload
> Reporter: Nick Boldt
> Assignee: Xavier Coulon
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [LiveReload]: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, 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 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for LiveReload 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-3516) Need better doc on using Central zip (online/offline modes) [was: Install all from central zip fails on CordovaSim]
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-3516?page=com.atlassian.jira.plugin.... ]
Misha Ali updated JBDS-3516:
----------------------------
Sprint: 12-Oct >> 25-Oct 2015-JBDS/JBT
Added to current sprint and drafting this information in google docs. Will paste the link here for review soon.
> Need better doc on using Central zip (online/offline modes) [was: Install all from central zip fails on CordovaSim]
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3516
> URL: https://issues.jboss.org/browse/JBDS-3516
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central, documentation, updatesite
> Affects Versions: 9.0.0.CR1
> Environment: jboss-devstudio-9.0.0.CR1-v20150912-1100-B100
> jboss-devstudio-9.0.0.CR1-updatesite-central.zip from https://devstudio.redhat.com/9.0/staging/updates/core/jboss-devstudio-9.0...
> Reporter: Jan Richter
> Assignee: Misha Ali
> Fix For: 9.0.1.Beta1
>
>
> This is what comes up when I try to install everything from the central zip:
> {noformat}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Tools Apache Cordova Simulator 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.CR1-v20150911-0408-B28)
> Missing requirement: Eclipse integrations of BrowserSim 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.eclipse 3.7.0.CR1-v20150911-0408-B28) requires 'bundle org.eclipse.thym.core 0.3.0' but it could not be found
> Cannot satisfy dependency:
> From: JBoss Tools Apache Cordova Simulator 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.CR1-v20150911-0408-B28)
> To: org.jboss.tools.cordovasim.eclipse [3.7.0.CR1-v20150911-0408-B28]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-20948) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Aerogear]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20948?page=com.atlassian.jira.plugi... ]
Gorkem Ercan closed JBIDE-20948.
--------------------------------
Resolution: Done
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Aerogear]
> ----------------------------------------------------------
>
> Key: JBIDE-20948
> URL: https://issues.jboss.org/browse/JBIDE-20948
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: aerogear-hybrid, cordovasim
> Reporter: Nick Boldt
> Assignee: Gorkem Ercan
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Aerogear]: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, 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 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [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-20953) For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Server]
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20953?page=com.atlassian.jira.plugi... ]
Rob Stryker closed JBIDE-20953.
-------------------------------
Resolution: Done
done
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1 [Server]
> --------------------------------------------------------
>
> Key: JBIDE-20953
> URL: https://issues.jboss.org/browse/JBIDE-20953
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: server
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [Server]: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, 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 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [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] (JBIDE-20947) For JBIDE 4.3.1.Beta1: Prepare for future Beta1
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20947?page=com.atlassian.jira.plugi... ]
Rob Stryker reassigned JBIDE-20947:
-----------------------------------
Assignee: Rob Stryker
> For JBIDE 4.3.1.Beta1: Prepare for future Beta1
> -----------------------------------------------
>
> Key: JBIDE-20947
> URL: https://issues.jboss.org/browse/JBIDE-20947
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: build
> Reporter: Nick Boldt
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1: Please perform the following tasks:
> If you expect to be doing 4.3.x maintenance work in your component:
> 1a. In your *{color:blue}4.3.x branch{color}*, 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 (if planning minor changes).
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.23.1:set-version -DnewVersion=4.3.1-SNAPSHOT
> {code}
> 1b. Make sure your *{color:orange}master branch{color}* has a higher version (eg., 4.3.100 or 4.4.0) than what you set in the previous step. If you already bumped your *{color:orange}master branch{color}* for 4.4.0.Alpha1 prep, DO NOT bump it again. (This is just a reminder.)
> 2a. In your *{color:blue}4.3.x branch{color}* ONLY, update your root pom to use parent pom version *{color:blue}4.3.1.Beta1-SNAPSHOT{color}*;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 2b. If your project has an *all-tests/pom.xml* (Aerogear, Base, Central, JavaEE, Server) please ensure you have bumped that file too, and that it refers to the correct parent pom version you used above.
> 3. In your *{color:blue}4.3.x branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:blue}4.51.1.CR1-SNAPSHOT{color}*;
> {code}
> mvn clean verify -Dtpc.version=4.51.1.CR1-SNAPSHOT
> {code}
> 4. Close (do not resolve) this JIRA when done.
> If, on the other hand, you do NOT expect to be doing maintenance in your component, please let Nick know via @-mention in this JIRA so he can pull a stable release of your component to use in future 4.3.x builds INSTEAD of including new CI builds.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
> See also: JBDS-3545
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBTIS-523) Create a demonstration/ prototype installer for Fuse Tooling support
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-523?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-523:
-------------------------------------------
If the Fuse perspective would actually have the editor area default available so Central should show up which actually can guide/help the user then i don't see much problems.
EVeryone just need to be aware this will only work for the Fuse Installer, not for everywhere else users will install from.
This is why I think the idea we've talked about in the past to actually have Central know about what kind of user your are and reorder its wizards/quickstarts based on your priorities/profile. i.e. are you a 80% Fuse 20% EAP then you dont get to see Teiid, or if you are 100% Teiid then all EAP and Fuse is shown last if at all.
But even before that - make Fuse quickstarts available from central. That would be much better since Fuse IDE don't support multiple versions of quickstarts, but central does.
> Create a demonstration/ prototype installer for Fuse Tooling support
> --------------------------------------------------------------------
>
> Key: JBTIS-523
> URL: https://issues.jboss.org/browse/JBTIS-523
> Project: JBoss Tools Integration Stack
> Issue Type: Enhancement
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Priority: Optional
> Attachments: sai1.png
>
>
> The PM management team (Ken Johnson, [~crobson] [~john.graham]) has asked for an install scenario that's tailored to a specific product set (i.e. Fuse Tooling) with the fewest number of decision points possible. Further they'd like the install experience to leave the user with the product-specific Eclipse perspective (ready-to-go).
> Clearly the new prototype stand-alone JBDSIS installer seems like a good place to start. The latest prototype:
> https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> Provides a one-stop experience to get both the JBDS core and JBDS IS (including the Fuse Tooling product components as Early Access). To reduce the installation steps by one, there exists:
> https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> This installer has the Fuse Tooling pre-selected. A future option here would be to create an installer with *just* the Fuse Tooling components available. Another future option would be to change the default perspective to the component-specific perspective (i.e. Fuse Integration perspective) in the generated installer.
> Here's a usability scenario targeting Fuse Tooling:
> {code}
> Test scenario A:
>
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDS installer jar. wget https://devstudio.redhat.com/9.0/stable/builds/installer/9.0.0.GA/jboss-d...
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/jboss-devstudio-*.jar`
> 4. Select the Software/Update tab in the JBoss Central view.
> 5. Select the checkbox to Enable Early Access, and click Yes to accept the warning.
> 6. Scroll down the list of available features, looking for the JBoss Developer Studio Integration Stack section.
> Select the following item:
> JBoss Fuse Development
> 7. Accept/ respond 'Yes' and restart
> 8. Select Window > Perspective > Open Perspective > Fuse Integration
> -----------------------------------------------------------------------------
> Test scenario B:
>
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window. See !sai1.png|thumbnail!
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> -----------------------------------------------------------------------------
> Test scenario C:
>
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar`
> 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Other... > Fuse Integration
> -----------------------------------------------------------------------------
> Test scenario D: (future - not available currently)
> 1. If you don't already have one installed, you will need to download and install Oracle or Open JDK 8. (make sure you have Java 1.8 installed)
> 2. Download the JBDSIS installer jar. wget https://devstudio.redhat.com/9.0/snapshots/updates/integration-stack/9.0....
> 3. Double-click the installer file to run it, or open a terminal and type `java -jar /path/to/installer-*-proto2.jar`
> 4. 'JBoss Fuse Development' is pre-selected - just 'next' through the installer
> 5. Accept/ respond 'Yes' and restart
> JBDS comes up in the Fuse Integration perspective - read to go.
> {code}
> Comments welcome!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months