[JBoss JIRA] (JBIDE-21267) For JBIDE 4.3.1.Beta1: 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-21267?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-21267 at 12/11/15 9:02 AM:
--------------------------------------------------------------
Ok, I was thinking about the CI jobs settings. So yes, they should be released for better consistency.
If you want to take care of it, the process is
# move to a non-SNAPSHOT version, push change
# run the CI job that publishes the SNAPSHOT, or use "mvn deploy" locally
# go to Nexus to approve and release the staging repo.
# Update parent pom to use the new release version
# Bump version to new snapshot
Edit by Nick to add one more:
# Update all the 4.3.mars jobs to use the new version
was (Author: mickael_istria):
Ok, I was thinking about the CI jobs settings. So yes, they should be released for better consistency.
If you want to take care of it, the process is
# move to a non-SNAPSHOT version, push change
# run the CI job that publishes the SNAPSHOT, or use "mvn deploy" locally
# go to Nexus to approve and release the staging repo.
# Update parent pom to use the new release version
# Bump version to new snapshot
> For JBIDE 4.3.1.Beta1: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21267
> URL: https://issues.jboss.org/browse/JBIDE-21267
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [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.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.1.Beta1, 9.1.0.Beta1|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 Beta1 (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.Beta1-SNAPSHOT.
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.2.Beta1 (or 4.50.2.Beta1-SNAPSHOT).
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.2.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch;
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> git checkout -b jbosstools-4.3.1.Beta1x
> git push origin jbosstools-4.3.1.Beta1x
> {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.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch, and
> * *{color:orange}4.3.1.Beta2-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, 4 months
[JBoss JIRA] (JBIDE-21301) Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21301?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-21301:
-------------------------------------
mmm it works for me but I don't know if it's because I'm on a mac or because Oomph preference recorder kicks and always restores that value.
> Preferences: path to OC binary is not shown on OpenShift 3 page if binary is on $PATH
> -------------------------------------------------------------------------------------
>
> Key: JBIDE-21301
> URL: https://issues.jboss.org/browse/JBIDE-21301
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Marián Labuda
> Priority: Minor
> Labels: openshift_v3, preferences
> Fix For: 4.3.1.Beta2
>
>
> In JBIDE-21183 was implemented auto-lookup of 'oc' binary on $PATH. This works ok, but in Workbench Preference dialog on OpenShift 3 preference page where location to oc is shown and stored is not this path displayed in this case. If 'oc' binary is located on $PATH it should be also visible on OpenShift 3 preference page.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21304) Add Show In Openshift / Docker for CDK server adapter
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-21304:
-------------------------------------------
Summary: Add Show In Openshift / Docker for CDK server adapter
Key: JBIDE-21304
URL: https://issues.jboss.org/browse/JBIDE-21304
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift, server
Reporter: Max Rydahl Andersen
Would be nice if the CDK server adapter had Show In > working to open it preselected in openshift and docker explorers.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-3249.
----------------------------
Resolution: Rejected
> As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3249
> URL: https://issues.jboss.org/browse/JBDS-3249
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, integration-platform, requirements, updatesite
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
> Fix For: 9.0.0.GA
>
>
> Today users can only install integration stack from jboss central which has some great advantages (uniform installation and only shows what is compatible/supported) but has the disadvantage of being an extra step on top of basic install plus harder to find.
> Suggestion been to at least have marketplace entry for Integration stack (JBTIS-355 and JBDS-3293) and an focused installer that includes integration-stack (JBDS-3276)
> From discussions from 12th December with Alan Santos we are targeting market place improvements for JBDS 8 and installers for JBDS 9.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3249:
-----------------------------
Status: New (was: New)
> As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3249
> URL: https://issues.jboss.org/browse/JBDS-3249
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, integration-platform, requirements, updatesite
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
> Fix For: 9.0.0.GA
>
>
> Today users can only install integration stack from jboss central which has some great advantages (uniform installation and only shows what is compatible/supported) but has the disadvantage of being an extra step on top of basic install plus harder to find.
> Suggestion been to at least have marketplace entry for Integration stack (JBTIS-355 and JBDS-3293) and an focused installer that includes integration-stack (JBDS-3276)
> From discussions from 12th December with Alan Santos we are targeting market place improvements for JBDS 8 and installers for JBDS 9.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-3249.
----------------------------
Resolution: Done
> As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3249
> URL: https://issues.jboss.org/browse/JBDS-3249
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, integration-platform, requirements, updatesite
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
> Fix For: 9.0.0.GA
>
>
> Today users can only install integration stack from jboss central which has some great advantages (uniform installation and only shows what is compatible/supported) but has the disadvantage of being an extra step on top of basic install plus harder to find.
> Suggestion been to at least have marketplace entry for Integration stack (JBTIS-355 and JBDS-3293) and an focused installer that includes integration-stack (JBDS-3276)
> From discussions from 12th December with Alan Santos we are targeting market place improvements for JBDS 8 and installers for JBDS 9.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-3249:
--------------------------------
> As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3249
> URL: https://issues.jboss.org/browse/JBDS-3249
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, integration-platform, requirements, updatesite
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
> Fix For: 9.0.0.GA
>
>
> Today users can only install integration stack from jboss central which has some great advantages (uniform installation and only shows what is compatible/supported) but has the disadvantage of being an extra step on top of basic install plus harder to find.
> Suggestion been to at least have marketplace entry for Integration stack (JBTIS-355 and JBDS-3293) and an focused installer that includes integration-stack (JBDS-3276)
> From discussions from 12th December with Alan Santos we are targeting market place improvements for JBDS 8 and installers for JBDS 9.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBDS-3249) As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3249?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3249:
-----------------------------
Fix Version/s: 9.0.0.GA
> As an Integration User I would like to easily install parts of IS without many unnecessary intermediate steps
> -------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3249
> URL: https://issues.jboss.org/browse/JBDS-3249
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, integration-platform, requirements, updatesite
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
> Fix For: 9.0.0.GA
>
>
> Today users can only install integration stack from jboss central which has some great advantages (uniform installation and only shows what is compatible/supported) but has the disadvantage of being an extra step on top of basic install plus harder to find.
> Suggestion been to at least have marketplace entry for Integration stack (JBTIS-355 and JBDS-3293) and an focused installer that includes integration-stack (JBDS-3276)
> From discussions from 12th December with Alan Santos we are targeting market place improvements for JBDS 8 and installers for JBDS 9.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21267) For JBIDE 4.3.1.Beta1: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21267?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-21267:
----------------------------------------
Ok, I was thinking about the CI jobs settings. So yes, they should be released for better consistency.
If you want to take care of it, the process is
# move to a non-SNAPSHOT version, push change
# run the CI job that publishes the SNAPSHOT, or use "mvn deploy" locally
# go to Nexus to approve and release the staging repo.
# Update parent pom to use the new release version
# Bump version to new snapshot
> For JBIDE 4.3.1.Beta1: Code Freeze + Branch [build, build-sites, build-ci, maven-plugins, dl.jb.org, devdoc, versionwatch]
> --------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21267
> URL: https://issues.jboss.org/browse/JBIDE-21267
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: task
> Fix For: 4.3.1.Beta1
>
>
> For JBIDE 4.3.1.Beta1 [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.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.1.Beta1, 9.1.0.Beta1|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 Beta1 (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.Beta1-SNAPSHOT.
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.2.Beta1 (or 4.50.2.Beta1-SNAPSHOT).
> {code}
> mvn clean verify -Dtpc.version=4.50.2.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.2.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing jbosstools-4.3.x branch into a new *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch;
> {code}
> git checkout jbosstools-4.3.x
> git pull origin jbosstools-4.3.x
> git checkout -b jbosstools-4.3.1.Beta1x
> git push origin jbosstools-4.3.1.Beta1x
> {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.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.1.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.1.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.1.Beta1x{color}* branch, and
> * *{color:orange}4.3.1.Beta2-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, 4 months
[JBoss JIRA] (JBTIS-523) Create a demonstration/ prototype installer for Fuse Tooling support
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-523?page=com.atlassian.jira.plugin.... ]
Paul Leacu closed JBTIS-523.
----------------------------
Resolution: Won't Do
The creation of a prototype JBDSIS stand-alone installer was successful and useful in usability testing. The general consensus from that testing and from developers was that creating a separate stand-alone JBDSIS installer does not provide enough user value-add to justify the added QE/ doc/ release overhead. Consequently, I'm closing this issue. I have retained the ability to build a JBDSIS stand-alone installer within a profile in the JBDSIS devstudio POM so we can turn this back on easily if we change our minds or circumstances dictate.
> 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, 4 months