[JBoss JIRA] (JBDS-4227) JVM crash in development when launching the CDK server
by Aurélien Pupier (JIRA)
Aurélien Pupier created JBDS-4227:
-------------------------------------
Summary: JVM crash in development when launching the CDK server
Key: JBDS-4227
URL: https://issues.jboss.org/browse/JBDS-4227
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Feature Request
Components: cdk, openshift
Affects Versions: 10.2.0.GA
Reporter: Aurélien Pupier
Assignee: Alexey Kazakov
Attachments: hs_err_pid13472.log, hs_err_pid7936.log
When I'm trying to develop new features and i'm using the CDK server adapter, every time i try to launch the CDK server, the JVm is crashing
{noformat}
Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
j org.eclipse.cdt.utils.pty.PTY.openMaster(Z)Ljava/lang/String;+0
j org.eclipse.cdt.utils.pty.PTY.<init>(Z)V+39
j org.eclipse.cdt.utils.pty.PTY.<init>(Lorg/eclipse/cdt/utils/pty/PTY$Mode;)V+13
j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callProcess(Ljava/lang/String;[Ljava/lang/String;Ljava/io/File;Ljava/util/Map;Z)Ljava/lang/Process;+84
j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunchConfiguration;)Ljava/lang/Process;+31
j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/Process;+18
j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+489
j org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+10
j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;ZZ)Lorg/eclipse/debug/core/ILaunch;+847
j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;Z)Lorg/eclipse/debug/core/ILaunch;+5
j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/debug/core/ILaunch;+4
j org.eclipse.wst.server.core.internal.Server.startImpl2(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)V+91
j org.eclipse.wst.server.core.internal.Server.startImpl(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+87
j org.eclipse.wst.server.core.internal.Server$StartJob.run(Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+9
j org.eclipse.core.internal.jobs.Worker.run()V+23
{noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (JBIDE-23587) Integration tests global refactoring: org.jboss.tools.maven.ui.bot.test
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23587?page=com.atlassian.jira.plugi... ]
Josef Kopriva closed JBIDE-23587.
---------------------------------
Closing. PR merged.
> Integration tests global refactoring: org.jboss.tools.maven.ui.bot.test
> -----------------------------------------------------------------------
>
> Key: JBIDE-23587
> URL: https://issues.jboss.org/browse/JBIDE-23587
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: maven
> Affects Versions: 4.4.2.Final
> Reporter: Jeff MAURY
> Assignee: Dmitrii Bocharov
> Labels: integration, integration_tests, maven
> Fix For: 4.4.3.AM1
>
>
> Maven command from CLI:
> {code}
> mvn clean verify -Dtest.module=org.jboss.tools.maven.ui.bot.test -DskipTests=false
> {code}
> Launching in Eclipse needs the following parameters:
> {code}
> -Dusage_reporting_enabled=false -Drd.config=resources/servers -Djbosstools.test.seam.2.1.0.home=/home/dbocharo/jboss-seam/jboss-seam-2.1.2 -Djbosstools.test.seam.2.3.0.home=/home/dbocharo/jboss-seam/jboss-seam-2.3.0.CR1 -Djbosstools.test.seam.2.2.0.home=/home/dbocharo/jboss-seam/jboss-seam-2.2.0.GA -Djbosstools.test.wildfly8.home=/home/dbocharo/wildfly-8.2.1.Final -Dmaven.settings.path=/home/dbocharo/dev/openshift/jbosstools-integration-tests/tests/org.jboss.tools.maven.ui.bot.test/target/classes/usersettings/settings.xml
> {code}
> Corresponding directories must contain Seam and Wildfly
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (ERT-476) User can install software from market without acceptation license agreements [EBZ#509500]
by Friendly Jira Robot (JIRA)
Friendly Jira Robot created ERT-476:
---------------------------------------
Summary: User can install software from market without acceptation license agreements [EBZ#509500]
Key: ERT-476
URL: https://issues.jboss.org/browse/ERT-476
Project: Eclipse Release Train
Issue Type: Task
Components: Community
Reporter: Friendly Jira Robot
Created attachment 265962
The "Review Licenses" window where the "Finish" button is available though the licence is not accepted.
User can install Red Hat JBoss Developer Studio from Eclipse Marketplace without acceptation terms of the licence agreements.
Step to reproduce:
1) Download, unpack and start Eclipse Neon 1
http://www.eclipse.org/downloads/download.php?file=/technology/epp/downlo...
2) Help -> Eclipse Marketplace -> Search for "Red Hat JBoss Developer Studio 10.2.0.GA" -> Install
3) The window "Review Licenses" looks like on the attached screenshot
4) Notice that "I do not accept..." is selected but Finish button is enabled and user is able to install Developer Studio.
When I click "I accept..." radio button and then switch back to "I do not accept..." it starts work correctly. So, the availability of the 'Finish' button is evaluated badly only in initial state.
I tried to remove ~/.eclipse directory and start Eclipse with new workspace but it didn't solve my problem.
This problem doesn't occur when installing JBoss Tools.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (JBDS-3867) CDK file name should include version, match file name on RHCP
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3867?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-3867:
--------------------------------
Sprint: (was: devex #124 December 2017)
> CDK file name should include version, match file name on RHCP
> -------------------------------------------------------------
>
> Key: JBDS-3867
> URL: https://issues.jboss.org/browse/JBDS-3867
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.Beta1
> Environment: Windows 7/64 bit
> Reporter: Robert Terzi
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 10.3.0.AM2
>
>
> The platform installer uses a file name for the CDK box with no version information making it difficult to tell if you have the latest CDK box or not.
> The downloaded box file is saved in \cdk\boxes\rhel-vagrant-virtualbox.box.
> It should use the same file name as the Red Hat Customer Portal to make it easy to identify that it is the same file: rhel-cdk-kubernetes-7.2-23.x86_64.vagrant-virtualbox.box
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (JBDS-4010) DevSuite installer should check if virtualization extension is enabled
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4010?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4010:
--------------------------------
Sprint: (was: devex #124 December 2017)
> DevSuite installer should check if virtualization extension is enabled
> ----------------------------------------------------------------------
>
> Key: JBDS-4010
> URL: https://issues.jboss.org/browse/JBDS-4010
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: ui
> Fix For: 10.3.0.AM2
>
>
> Oracle Virtualbox wont work w/o virtualization enabled in BIOS, so we should tell people to enable it for virtualbox to work after installation. Fortunately there is easy way to check it with powershell under windows.
> {code}PS C:\Users\eskimo> Get-WmiObject -class win32_processor -Property "VirtualizationFirmwareEnabled","SecondLevelAddressTr
> anslationExtensions"
> __GENUS : 2
> __CLASS : Win32_Processor
> __SUPERCLASS :
> __DYNASTY :
> __RELPATH :
> __PROPERTY_COUNT : 2
> __DERIVATION : {}
> __SERVER :
> __NAMESPACE :
> __PATH :
> SecondLevelAddressTranslationExtensions : True
> VirtualizationFirmwareEnabled : True
> PSComputerName :{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (JBDS-4207) Request for administrator credentials should say DevSuite Installer not osascript
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4207?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4207:
--------------------------------
Sprint: (was: devex #124 December 2017)
> Request for administrator credentials should say DevSuite Installer not osascript
> ---------------------------------------------------------------------------------
>
> Key: JBDS-4207
> URL: https://issues.jboss.org/browse/JBDS-4207
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 10.2.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: known_issue
> Fix For: 10.3.0.AM2
>
> Attachments: osascript.png
>
>
> Current implementation use osascript (AppleScript Engine) to run installation for vagrant and virtualbox as administrator. The consequence is osascript name in standard login/password dialog.
> !osascript.png!
> It should say Red Hat Development Suite Installer" instead
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months