[JBoss JIRA] (JBTIS-674) Deprecate 'SOA 5.x Compatibility' tooling
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-674?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-674:
-----------------------------
Description:
The SOA 5.x Development tooling shall be marked as deprecated starting with 9.0.0.GA. It shall be removed at JBDSIS 10.0.0.GA (Neon). It consists of:
org.guvnor.tools.feature
org.jboss.tools.esb.feature
org.jboss.tools.jbpm3.feature
org.jboss.tools.jbpm.common.feature
org.jboss.tools.jbpm.convert.feature
The runtime detector features will not be deprecated:
org.jboss.tools.runtime.drools.detector.feature
org.jboss.tools.runtime.esb.detector.feature
org.jboss.tools.runtime.jbpm.detector.feature
FYI - [~apodhrad] [~bbrodt] [~maxandersen] [~ganandan-Redhat]
was:
The SOA 5.x Development tooling shall be marked as deprecated starting with 9.0.0.GA. It shall be removed at JBDSIS 10.0.0.GA (Neon). It consists of:
org.guvnor.tools.feature
org.jboss.tools.esb.feature
org.jboss.tools.jbpm3.feature
org.jboss.tools.jbpm.common.feature
org.jboss.tools.jbpm.convert.feature
The runtime detector features will not be deprecated:
org.jboss.tools.runtime.drools.detector.feature
org.jboss.tools.runtime.esb.detector.feature
org.jboss.tools.runtime.jbpm.detector.feature
> Deprecate 'SOA 5.x Compatibility' tooling
> -----------------------------------------
>
> Key: JBTIS-674
> URL: https://issues.jboss.org/browse/JBTIS-674
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.0.GA
>
>
> The SOA 5.x Development tooling shall be marked as deprecated starting with 9.0.0.GA. It shall be removed at JBDSIS 10.0.0.GA (Neon). It consists of:
> org.guvnor.tools.feature
> org.jboss.tools.esb.feature
> org.jboss.tools.jbpm3.feature
> org.jboss.tools.jbpm.common.feature
> org.jboss.tools.jbpm.convert.feature
> The runtime detector features will not be deprecated:
> org.jboss.tools.runtime.drools.detector.feature
> org.jboss.tools.runtime.esb.detector.feature
> org.jboss.tools.runtime.jbpm.detector.feature
> FYI - [~apodhrad] [~bbrodt] [~maxandersen] [~ganandan-Redhat]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Aileen Cunningham (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Aileen Cunningham commented on JBTIS-654:
-----------------------------------------
This is what i see when I run the Installer: no option to select Fuse.
What am I missing?
------------------
This document can be seen online at http://www.redhat.com/licenses/jboss_eula.html. Archived 2014-07-31 18:00 GMT.
press 1 to accept, 2 to reject, 3 to redisplay
1
[ Starting to unpack ]
[ Processing package: P2 Director Application (1/3) ]
[ Processing package: Red Hat JBoss Developer Studio 9.1.0.GA (2/3) ]
[ Processing package: Red Hat JBoss Developer Studio 9.1.0.GA Metadata Generation (3/3) ]
[ Unpacking finished ]
[ Console installation done ]
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: inst1.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 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. i.e. 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-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBTIS-674) Deprecate 'SOA 5.x Compatibility' tooling
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-674:
--------------------------------
Summary: Deprecate 'SOA 5.x Compatibility' tooling
Key: JBTIS-674
URL: https://issues.jboss.org/browse/JBTIS-674
Project: JBoss Tools Integration Stack
Issue Type: Feature Request
Components: distribution
Affects Versions: 9.0.0.GA
Reporter: Paul Leacu
Assignee: Paul Leacu
Fix For: 9.0.0.GA
The SOA 5.x Development tooling shall be marked as deprecated starting with 9.0.0.GA. It shall be removed at JBDSIS 10.0.0.GA (Neon). It consists of:
org.guvnor.tools.feature
org.jboss.tools.esb.feature
org.jboss.tools.jbpm3.feature
org.jboss.tools.jbpm.common.feature
org.jboss.tools.jbpm.convert.feature
The runtime detector features will not be deprecated:
org.jboss.tools.runtime.drools.detector.feature
org.jboss.tools.runtime.esb.detector.feature
org.jboss.tools.runtime.jbpm.detector.feature
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBDS-3738) Getting Started / Readme for new users after Dev Platform install is complete
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3738?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3738:
---------------------------------
Priority: Blocker (was: Major)
> Getting Started / Readme for new users after Dev Platform install is complete
> -----------------------------------------------------------------------------
>
> Key: JBDS-3738
> URL: https://issues.jboss.org/browse/JBDS-3738
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, installer
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Assignee: Misha Ali
> Priority: Blocker
> Labels: Havoc
> Fix For: 9.1.0.GA
>
>
> Per discussion today, we need some sort of README / Getting Started Guide for new CDK users.
> This could be a link from the last page of the Dev Platform installer to a remote HTML page, but we could also include a copy of that HTML page in the c:\devplatform folder so people can refer to it offline.
> Need to decide where to locate the page online. If the doc can be available before April 12, it could potentially be included in the output of the installer for offline use too.
> URL: http://developers.redhat.com/devstudio-preview
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBDS-3738) Getting Started / Readme for new users after Dev Platform install is complete
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3738?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3738:
--------------------------------------
[~mhusnain] are you working on this one?
> Getting Started / Readme for new users after Dev Platform install is complete
> -----------------------------------------------------------------------------
>
> Key: JBDS-3738
> URL: https://issues.jboss.org/browse/JBDS-3738
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation, installer
> Affects Versions: 9.1.0.CR1
> Reporter: Nick Boldt
> Assignee: Misha Ali
> Priority: Blocker
> Labels: Havoc
> Fix For: 9.1.0.GA
>
>
> Per discussion today, we need some sort of README / Getting Started Guide for new CDK users.
> This could be a link from the last page of the Dev Platform installer to a remote HTML page, but we could also include a copy of that HTML page in the c:\devplatform folder so people can refer to it offline.
> Need to decide where to locate the page online. If the doc can be available before April 12, it could potentially be included in the output of the installer for offline use too.
> URL: http://developers.redhat.com/devstudio-preview
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBTIS-654) JBDSIS stand-alone installer
by Aileen Cunningham (JIRA)
[ https://issues.jboss.org/browse/JBTIS-654?page=com.atlassian.jira.plugin.... ]
Aileen Cunningham commented on JBTIS-654:
-----------------------------------------
Java 1.8, fedora 22. Will try again later and post the install log.
> JBDSIS stand-alone installer
> ----------------------------
>
> Key: JBTIS-654
> URL: https://issues.jboss.org/browse/JBTIS-654
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.1.GA
>
> Attachments: inst1.png
>
>
> Establish a stand-alone installer for JBDSIS that will contain JBDS and will enable easier installation of JBDSIS components - specifically Fuse Tooling. This Jira is specifically related to the JBDSIS installer. Other usability issues will be handled in other Jira.
> Installation scenario:
> {code}
> 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. i.e. 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-*.jar`
> 4. Select 'JBoss Fuse Development' from the 'Select Additional Features to Install' installer window.
> 5. Accept/ respond 'Yes' and restart
> 6. Select Window > Perspective > Open Perspective > Fuse Integration
> {code}
> A prototype installer has already been created - see:
> https://github.com/jbosstools/jbosstools-integration-stack/tree/master/de...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-22195) Docker-machine look-up does not work
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22195?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-22195:
---------------------------------------
I see the same on OS X. But today I installed Windows 10 and tried it there.
On Windows, when I first open the New Docker Connection wizard (with a docker machine already running), I get this popup:
You need to set the preferences for Docker Machine.
OK Cancel
I click ok, Docker Machine preference page opens. But it shows a warning: docker-machine could not be located in the directory.
The directory is set correctly to C:\Program Files\Docker Toolbox.
Once I click to edit the path, the warning disappears. But I still can't press OK.
When I click Cancel, I'm back in the new connection wizard and get a popup: No connections were found.
If I click again the Search button, I get the popup again: "You need to set the preferences for Docker Machine."
And from here I can go in circles.
So apparently this is broken on Windows.
I tested this with JBoss Tools 4.3.1.Final.
> Docker-machine look-up does not work
> ------------------------------------
>
> Key: JBIDE-22195
> URL: https://issues.jboss.org/browse/JBIDE-22195
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker
> Affects Versions: 4.3.1.CR1
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.4.0.Alpha1
>
>
> The {{Search...}} dialog for Docker Machines in the New Connection wizard in the Docker tooling does not work: a warning message appears in the Error Log view, saying :
> {quote}
> The 'docker-machine' command could not be located in /usr/bin:/bin:/usr/sbin:/sbin
> {quote}
> even though the preferences show that the {{docker-machine}} command is located in {{/usr/local/bin}}.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months