[JBoss JIRA] (JBDS-4406) DevSuite 1.4 Installer should indicate choose 1 hypervisor
by Robert Terzi (JIRA)
Robert Terzi created JBDS-4406:
----------------------------------
Summary: DevSuite 1.4 Installer should indicate choose 1 hypervisor
Key: JBDS-4406
URL: https://issues.jboss.org/browse/JBDS-4406
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: installer
Environment: DevSuite 1.4 installer, Windows 10 Pro/64
Reporter: Robert Terzi
Priority: Minor
The installer (on Windows) should indicate that only one hypervisor, Hyper-V OR Virtualbox, is needed. A user could get the wrong impression that both are needed.
In my case, it selected to install VirtualBox because Hyper-V was present but not enabled.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4405) DevSuite 1.4 installer links to CDK 2.4 docs for Hyper-V info
by Robert Terzi (JIRA)
Robert Terzi created JBDS-4405:
----------------------------------
Summary: DevSuite 1.4 installer links to CDK 2.4 docs for Hyper-V info
Key: JBDS-4405
URL: https://issues.jboss.org/browse/JBDS-4405
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: installer
Environment: DevSuite 1.4 installer, Windows 10 Pro/64
Reporter: Robert Terzi
Priority: Minor
The link for information about enabling Hyper-V in the installer brings up the CDK 2.4 documentation instead of the CDK 3.0 documentation.
Understand that this was probably necessary during development while the CDK 3.0 docs didn't exist. The problem is the link opens in a section describing CDK 2.4 software requirements which are inaccurate for CDK 3.0.
Is there any documentation for the DevSuite installer?
(Are there any other CDK 2.4 links that need to be updated in the installer?)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4402) Devsuite 1.4 Windows re-runs installed component checks on expose events
by Robert Terzi (JIRA)
[ https://issues.jboss.org/browse/JBDS-4402?page=com.atlassian.jira.plugin.... ]
Robert Terzi commented on JBDS-4402:
------------------------------------
It seems to me the conventional way this is done, at least on windows, is the 'back' and 'foward' buttons as part of the installer path.
Re-running the scan gets pretty tedious. While I've seen it complete in as little as a few seconds, I've often seen it take 15 seconds (timed) to complete which feels like an eternity. This is compounded by being impatient and switching windows to try to see what's going on.
> Devsuite 1.4 Windows re-runs installed component checks on expose events
> ------------------------------------------------------------------------
>
> Key: JBDS-4402
> URL: https://issues.jboss.org/browse/JBDS-4402
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: installer
> Environment: Windows 10 64-bit Pro, DevSuite 1.4 GA installer
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 11.0.0.AM2
>
>
> The DevSuite Windows installer re-runs the search for installed components every time there is a window event like restore/bring to front, minimize, etc. Considering how long it can take this can be quite annoying.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBDS-4404) DevSuite 1.4 Installer hung during install waiting for cygwin
by Robert Terzi (JIRA)
Robert Terzi created JBDS-4404:
----------------------------------
Summary: DevSuite 1.4 Installer hung during install waiting for cygwin
Key: JBDS-4404
URL: https://issues.jboss.org/browse/JBDS-4404
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Bug
Components: installer
Environment: Windows 10 Pro/64, DevSuite 1.4 installer
Reporter: Robert Terzi
Attachments: install.log
Attempting to install DevSuite 1.4 never completed, got stuck on waiting for Cygwin.
Attaching C:\DevelopmentSuite\installer.log, but it doesn't seem like it's got the info. Some of the last messages are Dev Studio installed correctly.
Cygwin was previously installed in C:\cygwin but not detected by installer so was installing it's own copy in \DevelopmentSuite.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24184) Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24184?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24184:
-------------------------------------
Story Points: 24 (was: 16)
> Server adapter: DEV_MODE, DEBUG_MODE, DEBUG_PORT keys (and default values) are hard-coded, not read from docker image
> ---------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24184
> URL: https://issues.jboss.org/browse/JBIDE-24184
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.4.AM2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.0.AM1
>
>
> to turn on/off debugging and dev_mode for an app, one needs to set env variables. The keys that are used to set the values are all defined in the docker image labels (inspectable by doing {code}docker inspect <docker-image-id>{code}:
> * nodejs
> {code}
> "Labels": {
> ...
> "com.redhat.dev-mode": "DEV_MODE:false",
> "com.redhat.dev-mode.port": "DEBUG_PORT:5858",
> ...
> {code}
> * eap
> {code}
> "Labels": {
> ...
> "com.redhat.dev-mode": "DEBUG:true",
> "com.redhat.dev-mode.port": "DEBUG_PORT:8787",
> ...
> {code}
> Our code on the other hand is hard-coding these, not reading the keys from the docker image:
> {code}
> public class OpenShiftDebugUtils {
> private static final String DEBUG_KEY = "DEBUG";
> private static final String DEBUG_PORT_KEY = "DEBUG_PORT";
> ...
> {code}
> {code}
> public class OpenShiftLaunchController extends AbstractSubsystemController
> implements ISubsystemController, ILaunchServerController {
> ...
> private static final String DEV_MODE = "DEV_MODE"; //$NON-NLS-1$
> ...
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24505) Isolate usage GA specific code though a separate provider
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24505:
----------------------------------
Summary: Isolate usage GA specific code though a separate provider
Key: JBIDE-24505
URL: https://issues.jboss.org/browse/JBIDE-24505
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: usage
Affects Versions: 4.4.4.Final
Reporter: Jeff MAURY
Fix For: 4.5.0.Final
In order to prepare to the switch from GA to segment.io, make the code more evolutive and isolate in a separate provider all GA specific
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months
[JBoss JIRA] (JBIDE-24504) Switch usage from GA to segment.io
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-24504:
----------------------------------
Summary: Switch usage from GA to segment.io
Key: JBIDE-24504
URL: https://issues.jboss.org/browse/JBIDE-24504
Project: Tools (JBoss Tools)
Issue Type: Epic
Components: usage
Affects Versions: 4.4.4.Final
Reporter: Jeff MAURY
Fix For: 4.5.0.Final
In order to standardize our analytics processes, switch JBT/DevStudio reporting data from GA to segment.io
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 10 months