[JBoss JIRA] (JBIDE-24048) Import application: would like to get a workspace project that's using the context-dir and branch used in OpenShift
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24048?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-24048.
------------------------------
Verified in JBT 4.4.4.AM2. Closing.
> Import application: would like to get a workspace project that's using the context-dir and branch used in OpenShift
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24048
> URL: https://issues.jboss.org/browse/JBIDE-24048
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.4.4.AM1
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Labels: import_wizard, openshift_v3
> Fix For: 4.4.4.AM2, 4.5.0.AM1
>
> Attachments: CONTEXT_DIR.png, SOURCE_REPOSITORY_REF.png, jboss-eap-quickstarts.png, jboss-kitchensink.png
>
>
> We're missing the ability to provide a context dir within a git repo when importing an application from OpenShift. The application wizard allows the user to set a context dir, which is used when importing right after the successfull creation. The (standalone) import is lacking this.
> steps to reproduce:
> # EXEC: launch openshift application wizard and pick "eap64-basic-s2i"
> # ASSERT: in the next page make sure there is "kitchensink" set to the CONTEXT_DIR template parameter
> !CONTEXT_DIR.png!
> # ASSERT: in the parameters, make sure that the SOURCE_REPOSITORY_REF is set to "6.4.x"
> !SOURCE_REPOSITORY_REF.png!
> # EXEC: finish the wizard and once the resources are created, simply confirm the import dialog that pops up
> # ASSERT: you get a "jboss-kitchensink" in your workspace. The import actually cloned the whole repo "jboss-eap-quickstarts" and imported the project within the "kitchensink" (the CONTEXT_DIR) folder as a workspace project
> !jboss-kitchensink.png!
> # EXEC: switch the branch in the git repo that already exists (ex. switch to master)
> # EXEC: in OpenShift Explorer: kill your workspace project, select the "eap-app" service and choose "Import Application" in the context-menu.
> # EXEC: in the upcoming import wizard, check "reuse existing repository" and then hit "Finish"
> Result:
> You get a project "jboss-eap-quickstart".
> !jboss-eap-quickstarts.png!
> There was no way to provide a context dir. To get the kitchensink project you need to remove the jboss-eap-quickstart" project, checkout the correct branch and reimport "kitchensink" (kitchensink only exists in the 6.4.x branch, not in the 7.x branches) manually as an existing maven project.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBDS-4349) Installer ignores Hyper-v
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-4349?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-4349:
-----------------------------------
The thing is, this command always returns False for me:
{noformat}powershell.exe -command "(GWMI Win32_Processor).VirtualizationFirmwareEnabled"{noformat}
I have enabled just about every virtualization option I could find in BIOS and Windows. [~dgolovin], any idea what is wrong?
> Installer ignores Hyper-v
> -------------------------
>
> Key: JBDS-4349
> URL: https://issues.jboss.org/browse/JBDS-4349
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.4.0.AM2
> Reporter: Jan Richter
>
> I have enabled Hyper-v. On confirmation page, Hyper-v is not present, instead it still offers to install Virtualbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-24215) CDK Server adapter editor: using symlink for "Minishift Location" stores the referenced binary, not the symlink
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24215?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-24215:
-------------------------------------
Steps to Reproduce:
# ASSERT: have 2 different cdk3 binaries (ex. Beta and Beta3), have a symlink pointing to one of them
# ASSERT: have a cdk3 server adapter pointing to binary that the symlink doesnt point to
# EXEC: open CDK3 server adapter editor and hit "Browse" for the "Minishift Location"
# EXEC: choose the symlink
Result:
"Minishift Location" shows the binary that the symlink points to, not the symlink file. This means that I can't change the symlink and have the adapter using the new binary. This basically voids the purpose of symlinks.
was:
# ASSERT: have 2 different cdk3 binaries (ex. Beta and Beta3), have a symlink pointing to one of them
# ASSERT: have a cdk3 server adapter pointing to binary that the symlink doesnt point to
# EXEC: open CDK3 server adapter editor and hit "Browse" for the "Minishift Location"
# EXEC: choose the symlink
Result:
"Minishift Location" will show the binary that the symlink points to, not the symlink file. This means that I cant change the symlink and have the adapter using the new binary with voids the purpose of symlinks
> CDK Server adapter editor: using symlink for "Minishift Location" stores the referenced binary, not the symlink
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-24215
> URL: https://issues.jboss.org/browse/JBIDE-24215
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.4.4.AM2
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Jeff MAURY reassigned JBIDE-23422:
----------------------------------
Assignee: Jeff MAURY (was: Andre Dietisheim)
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.4.4.AM3
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-23422:
-------------------------------
Sprint: devex #130 April 2017
> Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-23422
> URL: https://issues.jboss.org/browse/JBIDE-23422
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, openshift
> Affects Versions: 4.4.2.AM2
> Environment: windows 10
> Fedora 24
> Reporter: Ilya Buziuk
> Assignee: Jeff MAURY
> Priority: Critical
> Labels: nodejs, openshift_v3, server_adapter
> Fix For: 4.4.4.AM3
>
>
> We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout.
> The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)).
> We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years