[JBoss JIRA] (JBDS-3947) Some older versions of vagrant skip version validation
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3947?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3947:
--------------------------------
Fix Version/s: 10.2.0.AM2
(was: 10.2.0.AM1)
> Some older versions of vagrant skip version validation
> ------------------------------------------------------
>
> Key: JBDS-3947
> URL: https://issues.jboss.org/browse/JBDS-3947
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.0.0.GA
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM2
>
> Attachments: vagrant.png
>
>
> Some older versions (so far found 1.7.0, 1.6.5) will not have their version reckognized. As seen on the screenshot, it doesn't show the version it detected and the UI looks like it is going to be used. The installer tries to download and install its own though.
> !vagrant.png|thumbnail!
> The issue might be connected to the fact that with these versions the command
> {noformat}where vagrant{noformat}
> in fact returns 2 files
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3974) Support installation from Apple Disk Image
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3974?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3974:
--------------------------------
Fix Version/s: 10.2.0.AM3
(was: 10.2.0.AM1)
> Support installation from Apple Disk Image
> -------------------------------------------
>
> Key: JBDS-3974
> URL: https://issues.jboss.org/browse/JBDS-3974
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Story
> Components: platform-installer
> Affects Versions: 10.1.0.AM2
> Environment: Mac OS X
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM3
>
>
> Vagrant and Oracle Virtualbox are delivered as Apple Disk Images (usually .DMG file). Installer should provide support to mount image and install software package(s) it contains.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-4049) Cannot install Devstudio 10.1.0.GA into Eclipse Neon.1 RC3 (remediation required)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4049?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-4049:
----------------------------------
If you add https://devstudio.jboss.com/targetplatforms/jbdevstudiotarget/4.61.0.AM1-... to your list of available software sites, the snipmatch problem goes away.
So the issue here is that p2 is trying to install the version from our target platform on top of the version that's already in the Eclipse Javaee bundle. As soon as the newer 2.4.3 version is available in the TP composite, all is well.
> Cannot install Devstudio 10.1.0.GA into Eclipse Neon.1 RC3 (remediation required)
> ---------------------------------------------------------------------------------
>
> Key: JBDS-4049
> URL: https://issues.jboss.org/browse/JBDS-4049
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing, target-platform, updatesite, upstream
> Affects Versions: 10.1.0.GA
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.2.0.AM2
>
> Attachments: 4049-better-but-not-perfect.png, ds10.1_on_neon.1.RC3_remediation_needed.png
>
>
> Steps to repro:
> 1. Download eclipse-jee-neon-1-RC3-linux-gtk-x86_64.tar.gz, unpack and run
> 2. Help > Eclipse Marketplace... > Search for "jboss" and install Red Hat JBoss Developer Studio 10.1.0.GA
> 3. Remediation needed:
> {code}Cannot complete the install because of a conflicting dependency.
> Software being installed: Red Hat JBoss Developer Studio (Core Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.feature.feature.group 10.1.0.v20160902-1725)
> Software currently installed: JavaScript Development Tools 2.0.0.v201608301904 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201608301904)
> Only one of the following can be installed at once:
> JavaScript Development Tools Core 2.0.0.v201603171403 (org.eclipse.wst.jsdt.core 2.0.0.v201603171403)
> JavaScript Development Tools Core 1.3.401.v201511181529 (org.eclipse.wst.jsdt.core 1.3.401.v201511181529)
> JavaScript Development Tools Core 2.0.0.v201608251059 (org.eclipse.wst.jsdt.core 2.0.0.v201608251059)
> JavaScript Development Tools Core 2.0.0.v201604281930 (org.eclipse.wst.jsdt.core 2.0.0.v201604281930)
> JavaScript Development Tools Core 2.0.0.v201605251700 (org.eclipse.wst.jsdt.core 2.0.0.v201605251700)
> Cannot satisfy dependency:
> From: Red Hat JBoss Developer Studio (Core Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.feature.feature.group 10.1.0.v20160902-1725)
> To: com.jboss.devstudio.core.rpm.feature.feature.group [10.1.0.v20160902-1725]
> Cannot satisfy dependency:
> From: Red Hat JBoss Developer Studio (RPM Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.rpm.feature.feature.group 10.1.0.v20160902-1725)
> To: org.eclipse.wst.jsdt.feature.feature.group [2.0.0.v201605311817]
> Cannot satisfy dependency:
> From: JavaScript Development Tools 2.0.0.v201605311817 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201605311817)
> To: org.eclipse.wst.jsdt.core [2.0.0.v201605251700]
> Cannot satisfy dependency:
> From: JavaScript Development Tools 2.0.0.v201608301904 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201608301904)
> To: org.eclipse.wst.jsdt.core [2.0.0.v201608251059]
> {code} -- [^ds10.1_on_neon.1.RC3_remediation_needed.png]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3965) Add a note on how to launch cdk in last page of devsuite installer
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3965?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3965:
--------------------------------
Fix Version/s: 10.2.0.AM3
(was: 10.2.0.AM1)
> Add a note on how to launch cdk in last page of devsuite installer
> ------------------------------------------------------------------
>
> Key: JBDS-3965
> URL: https://issues.jboss.org/browse/JBDS-3965
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Affects Versions: 10.1.0.AM2
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Fix For: 10.2.0.AM3
>
>
> Recently, [~rick_wagner] gave us some feedback on how he tried to use the devsuite installer and then connect to the docker daemon running in cdk.
> This is described here: JBIDE-22734
> What happened was that Rick didn't know he was supposed to start CDK from the Servers view. Having some prior knowledge of CDK, he started it from CLI. Then he went to the Docker Explorer view and wanted to connect to cdk's docker daemon.
> Normally, the docker connection will be created for you automatically, but that assumes you start the cdk adapter in Servers View.
> So here's a proposal:
> Perhaps at the end of the devsuite installer, just before devstudio is launched, we could briefly note that to start using CDK, you can start it from the Server view, once devstudio is launched?
> Please note that the actual name of the server adapter is probably Container Runtime Environment, but I'm not 100 % sure, this needs to be verified.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3983) Development Suite Installer should work behind proxy
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3983?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3983:
--------------------------------
Fix Version/s: 10.2.0.AM2
(was: 10.2.0.AM1)
> Development Suite Installer should work behind proxy
> ----------------------------------------------------
>
> Key: JBDS-3983
> URL: https://issues.jboss.org/browse/JBDS-3983
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Affects Versions: 10.1.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: release_notes
> Fix For: 10.2.0.AM2
>
>
> DevSuite installer cannot download stack software form external links because it uses nodejs request module without proxy settings:
> CDK also requires proxy to be configured to have vagrant up working after installation, which could affect CDK Server Adapter Implementation.
> To make DevStudio Installer working behind proxy there should be variable HTTPS_PROXY in user environment which sets up URL to proxy server. URL examples for none auth proxy:
> * http(s)://servername.com:3128
> * http(s)://192.168.0.47:3128
> For auth proxy:
> * http(s)://username:password@servername.com:3128
> * http(s)://username:password@192.168.0.47:3128
> If you use email as username then replace @ with %40:
> * http(s)://username%40server.com:password@servername.com:3128
> * http(s)://username%40server.com:password@192.168.0.47:3128
> Additional details are here https://github.com/request/request#controlling-proxy-behaviour-using-envi....
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months
[JBoss JIRA] (JBDS-3983) Development Suite Installer should work behind proxy
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3983?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3983:
--------------------------------
Description:
DevSuite installer cannot download stack software form external links because it uses nodejs request module without proxy settings:
CDK also requires proxy to be configured to have vagrant up working after installation, which could affect CDK Server Adapter Implementation.
To make DevStudio Installer working behind proxy there should be variable HTTPS_PROXY in user environment which sets up URL to proxy server. URL examples for none auth proxy:
* http(s)://servername.com:3128
* http(s)://192.168.0.47:3128
For auth proxy:
* http(s)://username:password@servername.com:3128
* http(s)://username:password@192.168.0.47:3128
If you use email as username then replace @ with %40:
* http(s)://username%40server.com:password@servername.com:3128
* http(s)://username%40server.com:password@192.168.0.47:3128
Additional details are here https://github.com/request/request#controlling-proxy-behaviour-using-envi....
was:
DevSuite installer cannot download stack software form external links because it uses nodejs request module without proxy settings:
CDK also requires proxy to be configured to have vagrant up working after installation, which could affect CDK Server Adapter Implementation.
To make DevStudio Installer working behind proxy there should be variable HTTPS_PROXY in user environment which sets up URL to proxy server. URL examples for none auth proxy:
* http(s)://servername.com:3128
* http(s)://192.168.0.47:3128
For auth proxy:
* http(s)://username:password@servername.com:3128
* http(s)://username:password@192.168.0.47:3128
If you use email as username then replace @ with %40:
* http(s)://username%40server.com:password@servername.com:3128
* http(s)://username%40server.com:password@192.168.0.47:3128
Additional details are here https://github.com/request/request#controlling-proxy-behaviour-using-envi....
> Development Suite Installer should work behind proxy
> ----------------------------------------------------
>
> Key: JBDS-3983
> URL: https://issues.jboss.org/browse/JBDS-3983
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Epic
> Components: platform-installer
> Affects Versions: 10.1.0.AM1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: release_notes
> Fix For: 10.2.0.AM2
>
>
> DevSuite installer cannot download stack software form external links because it uses nodejs request module without proxy settings:
> CDK also requires proxy to be configured to have vagrant up working after installation, which could affect CDK Server Adapter Implementation.
> To make DevStudio Installer working behind proxy there should be variable HTTPS_PROXY in user environment which sets up URL to proxy server. URL examples for none auth proxy:
> * http(s)://servername.com:3128
> * http(s)://192.168.0.47:3128
> For auth proxy:
> * http(s)://username:password@servername.com:3128
> * http(s)://username:password@192.168.0.47:3128
> If you use email as username then replace @ with %40:
> * http(s)://username%40server.com:password@servername.com:3128
> * http(s)://username%40server.com:password@192.168.0.47:3128
> Additional details are here https://github.com/request/request#controlling-proxy-behaviour-using-envi....
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 6 months