[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18696:
------------------------------------------
[~cathat] can you maybe try to install a fresh IDE/JBDS? The other think that we could change is you to access it via a different network, but I dont see how we could achieve this.
> Application wizard: Can not show quickstarts list
> -------------------------------------------------
>
> Key: JBIDE-18696
> URL: https://issues.jboss.org/browse/JBIDE-18696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Final
> Environment: Windows 8 + Eclipse Luna (4.4)
> Reporter: Chunyun Chen
> Attachments: quickstarts-listed-win8.png, Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log
>
>
> The quickstarts are unable to be shown, so any quickstarts can not be chosen to create.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (JBIDE-18697) Error deploying exploded war on windows; fs / copy error
by Cássio Mazzochi Molin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18697?page=com.atlassian.jira.plugi... ]
Cássio Mazzochi Molin edited comment on JBIDE-18697 at 10/27/14 7:40 AM:
-------------------------------------------------------------------------
[~rob.stryker], the error no longer occurred after changing the permissions.
So, I think it's a good idea updating the error message.
PS.: The latest JBoss Tools version is amazing! And I am really impressed with the quick responses I have on JBoss Developer.
was (Author: cassiomolin):
[~rob.stryker], the error no longer occurred after changing the permissions.
So, I think it's a good idea changing the error message.
PS.: The latest JBoss Tools version is amazing! And I am really impressed with the quick responses I have on JBoss Developer.
> Error deploying exploded war on windows; fs / copy error
> --------------------------------------------------------
>
> Key: JBIDE-18697
> URL: https://issues.jboss.org/browse/JBIDE-18697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Final
> Reporter: Rob Stryker
> Fix For: 4.2.1.Final
>
>
> https://developer.jboss.org/message/907562
> A user has reported that on windows, deploying a simple exploded war has failed with a copy error. This should be investigated
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (JBIDE-18572) NPE while calling a diff between 2 versions of a JS file
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18572?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-18572:
------------------------------------------------
{quote}Thus this is probably happening on systems where a browser is not available - like windows 64bit windows like Andrei.{quote}
But browser is available everywhere, it's not VPE. But maybe it was still not initialized. Anyway, look through the code/trace and found that this error happens in unuseful code. To be sure that removing this code will not do any harm I need detailed steps to reproduce. Xavier, Andrei, please help me with it.
> NPE while calling a diff between 2 versions of a JS file
> --------------------------------------------------------
>
> Key: JBIDE-18572
> URL: https://issues.jboss.org/browse/JBIDE-18572
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.CR1
> Reporter: Xavier Coulon
> Assignee: Konstantin Marmalyukov
> Priority: Blocker
> Fix For: 4.2.1.Final
>
>
> Not sure if the error is related {{summarry}}, but here's the stacktrace:
> I did compare my current JS file with the first version in my history, which was an empty file, then I called the diff with the next version and I got this error. I kept having this error when comparing the current version with any other version of the file (if that can help to reproduce/identify the problem)
> {code}
> java.lang.NullPointerException
> at org.jboss.tools.vpe.preview.editor.VpvEditor.formRequestToServer(VpvEditor.java:572)
> at org.jboss.tools.vpe.preview.editor.VpvEditor.access$0(VpvEditor.java:551)
> at org.jboss.tools.vpe.preview.editor.VpvEditor$EditorListener.partInputChanged(VpvEditor.java:674)
> at org.eclipse.ui.internal.WorkbenchPage$28.run(WorkbenchPage.java:5151)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.WorkbenchPage.firePartInputChanged(WorkbenchPage.java:5148)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart$4.propertyChanged(CompatibilityPart.java:369)
> at org.eclipse.ui.part.WorkbenchPart.firePropertyChange(WorkbenchPart.java:132)
> at org.eclipse.compare.internal.CompareEditor.doSetInput(CompareEditor.java:313)
> at org.eclipse.compare.internal.CompareEditor.setInput(CompareEditor.java:254)
> at org.eclipse.compare.internal.CompareUIPlugin$1.run(CompareUIPlugin.java:546)
> at org.eclipse.compare.internal.CompareUIPlugin.syncExec(CompareUIPlugin.java:1413)
> at org.eclipse.compare.internal.CompareUIPlugin.internalOpenEditor(CompareUIPlugin.java:567)
> at org.eclipse.compare.internal.CompareUIPlugin.openEditorInBackground(CompareUIPlugin.java:537)
> at org.eclipse.compare.internal.CompareUIPlugin.openCompareEditor(CompareUIPlugin.java:526)
> at org.eclipse.compare.CompareUI.reuseCompareEditor(CompareUI.java:199)
> at org.eclipse.compare.CompareUI.reuseCompareEditor(CompareUI.java:180)
> at org.eclipse.team.internal.ui.actions.CompareRevisionAction.openInCompare(CompareRevisionAction.java:139)
> at org.eclipse.team.internal.ui.actions.CompareRevisionAction.run(CompareRevisionAction.java:102)
> at org.eclipse.team.internal.ui.history.LocalHistoryPage$9.open(LocalHistoryPage.java:414)
> at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:48)
> at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:853)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:178)
> at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:850)
> at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1142)
> at org.eclipse.jface.viewers.StructuredViewer$6.handleOpen(StructuredViewer.java:1249)
> at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:278)
> at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:272)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:313)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4188)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1467)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1490)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1475)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1279)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4031)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3658)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:484)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-18696 at 10/27/14 7:24 AM:
--------------------------------------------------------------------
I tried to replicate this using win8 and the exact same devenv (ec2-54-91-37-89.compute-1.amazonaws.com). I couldnt, I got the quickstarts right ahead (no restarting Eclipse/JBDS required):
# ASSERT: make sure you have "-Djsse.enableSNIExtension=false" in your eclipse.ini (or jbdevstudio.ini)
# EXEC: launch JBDS/Eclipse
# EXEC: File->New->OpenShift->New Application
# EXEC: New Connection, point it to ec2-54-91-37-89.compute-1.amazonaws.com and use some random credentials
# EXEC: Look at the quickstart cathegory
Result:
It's fully popullated with entries (for me)
!quickstarts-listed-win8.png!
was (Author: adietish):
I tried to replicate this using win8 and the exact same devenv (ec2-54-91-37-89.compute-1.amazonaws.com). I couldnt, I got the quickstarts right ahead:
# ASSERT: make sure you have "-Djsse.enableSNIExtension=false" in your eclipse.ini (or jbdevstudio.ini)
# EXEC: launch JBDS/Eclipse
# EXEC: File->New->OpenShift->New Application
# EXEC: New Connection, point it to ec2-54-91-37-89.compute-1.amazonaws.com and use some random credentials
# EXEC: Look at the quickstart cathegory
Result:
It's fully popullated with entries (for me)
!quickstarts-listed-win8.png!
> Application wizard: Can not show quickstarts list
> -------------------------------------------------
>
> Key: JBIDE-18696
> URL: https://issues.jboss.org/browse/JBIDE-18696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Final
> Environment: Windows 8 + Eclipse Luna (4.4)
> Reporter: Chunyun Chen
> Attachments: quickstarts-listed-win8.png, Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log
>
>
> The quickstarts are unable to be shown, so any quickstarts can not be chosen to create.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-18696 at 10/27/14 7:24 AM:
--------------------------------------------------------------------
I tried to replicate this using win8 and the exact same devenv (ec2-54-91-37-89.compute-1.amazonaws.com). I couldnt, I got the quickstarts right ahead:
# ASSERT: make sure you have "-Djsse.enableSNIExtension=false" in your eclipse.ini (or jbdevstudio.ini)
# EXEC: launch JBDS/Eclipse
# EXEC: File->New->OpenShift->New Application
# EXEC: New Connection, point it to ec2-54-91-37-89.compute-1.amazonaws.com and use some random credentials
# EXEC: Look at the quickstart cathegory
Result:
It's fully popullated with entries (for me)
!quickstarts-listed-win8.png!
was (Author: adietish):
I tried to replicate this using win8 and the exact same devenv (ec2-54-91-37-89.compute-1.amazonaws.com). I couldnt, I got the quickstarts right ahead:
# ASSERT: make sure you have "-Djsse.enableSNIExtension=false" in your eclipse.ini (or jbdevstudio.ini)
# EXEC: File->New->OpenShift->New Application
# EXEC: New Connection, point it to ec2-54-91-37-89.compute-1.amazonaws.com and use some random credentials
# EXEC: Look at the quickstart cathegory
Result:
It's fully popullated with entries (for me)
!quickstarts-listed-win8.png!
> Application wizard: Can not show quickstarts list
> -------------------------------------------------
>
> Key: JBIDE-18696
> URL: https://issues.jboss.org/browse/JBIDE-18696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Final
> Environment: Windows 8 + Eclipse Luna (4.4)
> Reporter: Chunyun Chen
> Attachments: quickstarts-listed-win8.png, Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log
>
>
> The quickstarts are unable to be shown, so any quickstarts can not be chosen to create.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (JBIDE-18696) Application wizard: Can not show quickstarts list
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18696?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-18696:
------------------------------------------
I tried to replicate this using win8 and the exact same devenv (ec2-54-91-37-89.compute-1.amazonaws.com). I couldnt, I got the quickstarts right ahead:
# ASSERT: make sure you have "-Djsse.enableSNIExtension=false" in your eclipse.ini (or jbdevstudio.ini)
# EXEC: File->New->OpenShift->New Application
# EXEC: New Connection, point it to ec2-54-91-37-89.compute-1.amazonaws.com and use some random credentials
# EXEC: Look at the quickstart cathegory
Result:
It's fully popullated with entries (for me)
!quickstarts-listed-win8.png!
> Application wizard: Can not show quickstarts list
> -------------------------------------------------
>
> Key: JBIDE-18696
> URL: https://issues.jboss.org/browse/JBIDE-18696
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Final
> Environment: Windows 8 + Eclipse Luna (4.4)
> Reporter: Chunyun Chen
> Attachments: Screenshot1.png, Screenshot3.png, trace_after_restart.log, trace_before_restart.log
>
>
> The quickstarts are unable to be shown, so any quickstarts can not be chosen to create.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (JBIDE-17212) Server process is not killed if shutdown script fails or is empty with Deploy-only server adapter
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17212?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17212:
-------------------------------------
[~mmalina] Please verify steps to replicate here
> Server process is not killed if shutdown script fails or is empty with Deploy-only server adapter
> -------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17212
> URL: https://issues.jboss.org/browse/JBIDE-17212
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.x
>
>
> As you said in JBIDE-7515, when you specify startup and shutdown scripts with a deploy-only server, the server process should be killed if the shutdown script fails. But that is not the case.
> From JBIDE-7515:
> {quote}
> I left the shutdown script empty.
> You said that if the shutdown script fails, the process ID will be killed. Maybe technically an empty command does not fail, but I believe in this case the running java process should still be killed and it isn't.
> In fact, it doesn't work even if I put something that will fail there, e.g. "exit 1".
> {quote}
> The shutdown should default to process kill even if the shutdown script is empty.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years
[JBoss JIRA] (JBIDE-17618) Server start button disabled after Eclipse restart
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17618?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17618:
-------------------------------------
I can't replicate this [~mmalina] Is this still an issue for you?
> Server start button disabled after Eclipse restart
> --------------------------------------------------
>
> Key: JBIDE-17618
> URL: https://issues.jboss.org/browse/JBIDE-17618
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 4.2.0.Beta2
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.2.x
>
> Attachments: disabled-server-start.png
>
>
> When you restart Eclipse with the Server View open, right after the IDE start, the first server will be selected, but the Start button cannot be clicked.
> !disabled-server-start.png!
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
10 years