[JBoss JIRA] (JBIDE-22113) CDK shutdown always goes to Forcing shutdown of VM on Windows
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22113?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-22113.
---------------------------------
> CDK shutdown always goes to Forcing shutdown of VM on Windows
> -------------------------------------------------------------
>
> Key: JBIDE-22113
> URL: https://issues.jboss.org/browse/JBIDE-22113
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.CR1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.2.Final
>
>
> On OS X, when I stop CDK in JBDS, I get this in the console:
> ==> default: Unregistering box with vagrant-registration...
> ==> default: Attempting graceful shutdown of VM...
> And a few seconds later, the server adapter shows "Stopped".
> Today while testing on Windows I noticed that it behaves differently.
> It first displays these two lines, but it keeps "Stopping". And eventually there is another line in the console which says:
> ==> default: Forcing shutdown of VM...
> After this, the server adapter shows "Stopped".
> So for some unknown reason, on Windows the graceful shutdown fails to work.
> This is JBDS+CDK installed from the latest windows installer (built April 4th).
> It would be good to see if others see this on Windows as well or not.
> Interestingly, when I just tried "vagrant halt" from cygwin instead of in JBDS, it stops normally - graceful shutdown.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23471) Cannot launch central after devstudio install - unable to open jbosstools-central-webpage.zip
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23471?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-23471.
---------------------------------
> Cannot launch central after devstudio install - unable to open jbosstools-central-webpage.zip
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-23471
> URL: https://issues.jboss.org/browse/JBIDE-23471
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.2.AM3
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Fix For: 4.4.2.Final
>
> Attachments: central-error.png
>
>
> I just installed devstudio 10.2.0.AM3 [1] and launched it and I saw this error pop up immediately:
> {code}
> Unable to open /Users/rasp/jbossqa/JBDS/10.0.0/devstudio-10.2.0.AM3-6372/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.tools.central_2.1.2.v20160922-1945/resources/jbosstools-central-webpage.zip
> /Users/rasp/jbossqa/JBDS/10.0.0/workspace-10.2.0.AM3-6372/.metadata/.plugins/org.jboss.tools.central/central/dff8cd5/index.html can not be found
> {code}
> !central-error.png!
> JBoss Central page could not be loaded.
> Unfortunately I seem to be the only one seeing this. Radim and Ondrej both said it works for them. Rasto said he saw something similar in Error Log last week.
> [1] devstudio-10.2.0.AM3-v20161104-1659-B6372-installer-eap.jar
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23471) Cannot launch central after devstudio install - unable to open jbosstools-central-webpage.zip
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23471?page=com.atlassian.jira.plugi... ]
Martin Malina resolved JBIDE-23471.
-----------------------------------
Fix Version/s: 4.4.2.Final
Resolution: Cannot Reproduce
[~fbricon], I tried as you suggested, but still could not reproduce. So closing this issue.
> Cannot launch central after devstudio install - unable to open jbosstools-central-webpage.zip
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-23471
> URL: https://issues.jboss.org/browse/JBIDE-23471
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.2.AM3
> Reporter: Martin Malina
> Assignee: Fred Bricon
> Fix For: 4.4.2.Final
>
> Attachments: central-error.png
>
>
> I just installed devstudio 10.2.0.AM3 [1] and launched it and I saw this error pop up immediately:
> {code}
> Unable to open /Users/rasp/jbossqa/JBDS/10.0.0/devstudio-10.2.0.AM3-6372/studio/devstudio.app/Contents/Eclipse/plugins/org.jboss.tools.central_2.1.2.v20160922-1945/resources/jbosstools-central-webpage.zip
> /Users/rasp/jbossqa/JBDS/10.0.0/workspace-10.2.0.AM3-6372/.metadata/.plugins/org.jboss.tools.central/central/dff8cd5/index.html can not be found
> {code}
> !central-error.png!
> JBoss Central page could not be loaded.
> Unfortunately I seem to be the only one seeing this. Radim and Ondrej both said it works for them. Rasto said he saw something similar in Error Log last week.
> [1] devstudio-10.2.0.AM3-v20161104-1659-B6372-installer-eap.jar
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months
[JBoss JIRA] (JBIDE-23636) Update supported configuration docs / test plans / platforms for jbosstools 4.4.3 / devstudio 10.3
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23636?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-23636:
----------------------------------
Description:
It's time to review the available platforms on which we test devstudio / jbt.
Ubuntu:
We will probably want 16.04.1 LTS and 16.10, but should check https://wiki.ubuntu.com/Releases
Fedora:
We will want to support Fedora 24 and 25, but 25 currently has some issues with Wayland - JBDS-4204 among others.
Here's the support matrix document:
https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio...
was:
It's time to review the available platforms on which we test devstudio / jbt.
Specifically, we list Ubuntu 14.04 LTS and 16.04 LTS, but there will be newer versions available [0] when 10.2 / 4.4.2 is released in Dec 2016.
[0] https://wiki.ubuntu.com/Releases
* Should we move to 16.04.1 LTS and 16.10?
* Should we move to 14.04.5 LTS and 16.04.1 LTS ?
* Should we move to 14.04.5 LTS and 16.10?
Also, it was decided today in the 5x5 call that we should be supporting Fedora 23 and 24 (where currently we support 22 and 23) [1].
[1] https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio...
But Fedora 25 will be out on Nov 15 [2], which is 2 weeks before the 10.2 final code freeze on Nov 29, so we probably have time to contain & support that, right?
[2] https://fedoraproject.org/wiki/Releases/25/Schedule
* Should we move to F24 and F25?
> Update supported configuration docs / test plans / platforms for jbosstools 4.4.3 / devstudio 10.3
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23636
> URL: https://issues.jboss.org/browse/JBIDE-23636
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.4.2.Final
> Reporter: Nick Boldt
> Assignee: Martin Malina
> Labels: releasework
> Fix For: 4.4.3.AM2
>
>
> It's time to review the available platforms on which we test devstudio / jbt.
> Ubuntu:
> We will probably want 16.04.1 LTS and 16.10, but should check https://wiki.ubuntu.com/Releases
> Fedora:
> We will want to support Fedora 24 and 25, but 25 currently has some issues with Wayland - JBDS-4204 among others.
> Here's the support matrix document:
> https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio...
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 4 months