[JBoss JIRA] (JBIDE-26228) Fix Ubuntu 1710 instances
by Josef Kopriva (JIRA)
Josef Kopriva created JBIDE-26228:
-------------------------------------
Summary: Fix Ubuntu 1710 instances
Key: JBIDE-26228
URL: https://issues.jboss.org/browse/JBIDE-26228
Project: Tools (JBoss Tools)
Issue Type: Task
Components: qa
Affects Versions: 4.9.0.AM1
Environment: OpenStack
Reporter: Josef Kopriva
Assignee: Josef Kopriva
After last rebuild of ubuntu 1710, machines does not work.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-25557) OpenJDK9 + org.jboss.forge: org.jboss.forge.furnace.exception.ContainerException
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25557?page=com.atlassian.jira.plugi... ]
Josef Kopriva commented on JBIDE-25557:
---------------------------------------
[~jeffmaury] yes, Forge can be now started without issues.
> OpenJDK9 + org.jboss.forge: org.jboss.forge.furnace.exception.ContainerException
> --------------------------------------------------------------------------------
>
> Key: JBIDE-25557
> URL: https://issues.jboss.org/browse/JBIDE-25557
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.5.2.AM3
> Environment: FC27 + OpenJDK9
> Red Hat JBoss Developer Studio Version: 11.2.0.AM3
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.9.x
>
>
> Forge does not start:
> {code:java}
> null
> org.eclipse.core.jobs
> Error
> Thu Jan 11 12:59:40 CET 2018
> An internal error occurred during: "Starting JBoss Forge 3.7.2.Final".
> org.jboss.forge.furnace.exception.ContainerException: No services of type [org.jboss.forge.addon.projects.ProjectFactory] could be found in any started addons.
> at org.jboss.forge.furnace.impl.addons.ImportedImpl.get(ImportedImpl.java:79)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:97)
> at org.jboss.forge.furnace.services.Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.get(Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.java)
> at org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:95)
> at org.jboss.tools.forge.ui.util.ForgeHelper.initializeFurnaceRuntime(ForgeHelper.java:99)
> at org.jboss.tools.forge.ui.util.ForgeHelper.access$0(ForgeHelper.java:89)
> at org.jboss.tools.forge.ui.util.ForgeHelper$1.runInWorkspace(ForgeHelper.java:57)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> {code:java}
> null
> org.eclipse.ui
> Error
> Thu Jan 11 12:59:40 CET 2018
> Unhandled event loop exception
> org.jboss.forge.furnace.exception.ContainerException: No services of type [org.jboss.forge.addon.shell.spi.ShellHandle] could be found in any started addons.
> at org.jboss.forge.furnace.impl.addons.ImportedImpl.get(ImportedImpl.java:79)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:97)
> at org.jboss.forge.furnace.services.Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.get(Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.java)
> at org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:95)
> at org.jboss.tools.forge.ui.internal.cli.AeshConsole.start(AeshConsole.java:46)
> at org.jboss.tools.aesh.ui.view.AbstractTextViewer$1.run(AbstractTextViewer.java:46)
> at org.eclipse.ui.internal.PendingSyncExec.run(PendingSyncExec.java:58)
> at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:168)
> at org.eclipse.ui.internal.UISynchronizer.lambda$0(UISynchronizer.java:150)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4577)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4186)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> 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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22138 at 7/23/18 2:14 PM:
-------------------------------------------------------------------
[~rob.stryker] m2e-wtp sets the module name in the following method: [AbstractProjectConfiguratorDelegate#configureDeployedName|https://github....]
I see it being called, which then causes the file to change on disk.
This then causes *J2EEModuleVirtualComponent* to clear it's cache:
{code}
J2EEModuleVirtualComponent(VirtualComponent).clearCache() line: 721
J2EEModuleVirtualComponent.clearCache() line: 512
J2EEModuleVirtualComponent(VirtualComponent).resourceChanged(Resource) line: 95
VirtualComponent$ResourceAdapter.notifyChanged(Notification) line: 78
WTPModulesResource(TranslatorResourceImpl).eNotify(Notification) line: 444
WTPModulesResource(ResourceImpl).setModified(boolean) line: 1867
WTPModulesResource(TranslatorResourceImpl).doSave(OutputStream, Map) line: 192
WTPModulesResource(ResourceImpl).save(OutputStream, Map<?,?>) line: 1475
WTPModulesResource(ResourceImpl).save(Map<?,?>) line: 1044
WTPModulesResource(ReferencedXMIResourceImpl).save(Map) line: 377
WTPModulesResource(TranslatorResourceImpl).save(Map) line: 167
ModuleStructuralModel(EditModel).primSaveResource(Resource) line: 1303
ModuleStructuralModel(EditModel).saveResource(Resource) line: 1334
ModuleStructuralModel(EditModel).primSave(IProgressMonitor) line: 1269
EditModel$1.run(IProgressMonitor) line: 373
Workspace.run(ICoreRunnable, ISchedulingRule, int, IProgressMonitor) line: 2289
Workspace.run(IWorkspaceRunnable, ISchedulingRule, int, IProgressMonitor) line: 2316
ModuleStructuralModel.runSaveOperation(IWorkspaceRunnable, IProgressMonitor) line: 310
ModuleStructuralModel(EditModel).save(IProgressMonitor, Object) line: 376
ModuleStructuralModel.saveIfNecessary(IProgressMonitor, Object) line: 392
StructureEdit.saveIfNecessary(IProgressMonitor) line: 397
WebProjectConfiguratorDelegate(AbstractProjectConfiguratorDelegate).configureDeployedName(IProject, String) line: 189
{code}
But I dont see *J2EEDeployableFactory#clearCache* being called. Btw. I dont see J2EEDeployableFactory listening to resource change. Here are the listeners that I see registered:
* org.eclipse.emf.common.notify.impl.AdapterImpl@21197771
* org.eclipse.wst.common.internal.emfworkbench.integration.EditModel$ResourceAdapter@6bc55154
* org.eclipse.wst.common.internal.emfworkbench.WorkbenchResourceHelper$FileAdapter@3543d4e1
* EMF2DOMAdapterImpl(#document,WTPModulesResource), org.eclipse.wst.common.componentcore.internal.resources.VirtualComponent$ResourceAdapter@2e185af0
was (Author: adietish):
[~rob.stryker] m2e-wtp sets the module name in the following method: [AbstractProjectConfiguratorDelegate#configureDeployedName|https://github....]
I see it being called, which then causes the file to change on disk.
This then causes J2EEModuleVirtualComponent to clear it's cache:
{code}
J2EEModuleVirtualComponent(VirtualComponent).clearCache() line: 721
J2EEModuleVirtualComponent.clearCache() line: 512
J2EEModuleVirtualComponent(VirtualComponent).resourceChanged(Resource) line: 95
VirtualComponent$ResourceAdapter.notifyChanged(Notification) line: 78
WTPModulesResource(TranslatorResourceImpl).eNotify(Notification) line: 444
WTPModulesResource(ResourceImpl).setModified(boolean) line: 1867
WTPModulesResource(TranslatorResourceImpl).doSave(OutputStream, Map) line: 192
WTPModulesResource(ResourceImpl).save(OutputStream, Map<?,?>) line: 1475
WTPModulesResource(ResourceImpl).save(Map<?,?>) line: 1044
WTPModulesResource(ReferencedXMIResourceImpl).save(Map) line: 377
WTPModulesResource(TranslatorResourceImpl).save(Map) line: 167
ModuleStructuralModel(EditModel).primSaveResource(Resource) line: 1303
ModuleStructuralModel(EditModel).saveResource(Resource) line: 1334
ModuleStructuralModel(EditModel).primSave(IProgressMonitor) line: 1269
EditModel$1.run(IProgressMonitor) line: 373
Workspace.run(ICoreRunnable, ISchedulingRule, int, IProgressMonitor) line: 2289
Workspace.run(IWorkspaceRunnable, ISchedulingRule, int, IProgressMonitor) line: 2316
ModuleStructuralModel.runSaveOperation(IWorkspaceRunnable, IProgressMonitor) line: 310
ModuleStructuralModel(EditModel).save(IProgressMonitor, Object) line: 376
ModuleStructuralModel.saveIfNecessary(IProgressMonitor, Object) line: 392
StructureEdit.saveIfNecessary(IProgressMonitor) line: 397
WebProjectConfiguratorDelegate(AbstractProjectConfiguratorDelegate).configureDeployedName(IProject, String) line: 189
{code}
But I dont see *J2EEDeployableFactory#clearCache* being called. Btw. I dont see J2EEDeployableFactory listening to resource change. Here are the listeners that I see registered:
* org.eclipse.emf.common.notify.impl.AdapterImpl@21197771
* org.eclipse.wst.common.internal.emfworkbench.integration.EditModel$ResourceAdapter@6bc55154
* org.eclipse.wst.common.internal.emfworkbench.WorkbenchResourceHelper$FileAdapter@3543d4e1
* EMF2DOMAdapterImpl(#document,WTPModulesResource), org.eclipse.wst.common.componentcore.internal.resources.VirtualComponent$ResourceAdapter@2e185af0
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.9.0.AM1
>
> Attachments: image-2018-06-22-19-02-57-247.png
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
> steps:
> # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.)
> # EXEC: import the app into your Eclipse workspace
> # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift"
> # EXEC: create a server adapter and start it
> # ASSERT: adapter starts syncing, verify what war is used
> Result:
> The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war"
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-22138) Server adapter: doesn't respect openshift maven profile
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22138?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-22138 at 7/23/18 12:08 PM:
--------------------------------------------------------------------
[~rob.stryker] m2e-wtp sets the module name in the following method: [AbstractProjectConfiguratorDelegate#configureDeployedName|https://github....]
I see it being called, which then causes the file to change on disk.
This then causes J2EEModuleVirtualComponent to clear it's cache:
{code}
J2EEModuleVirtualComponent(VirtualComponent).clearCache() line: 721
J2EEModuleVirtualComponent.clearCache() line: 512
J2EEModuleVirtualComponent(VirtualComponent).resourceChanged(Resource) line: 95
VirtualComponent$ResourceAdapter.notifyChanged(Notification) line: 78
WTPModulesResource(TranslatorResourceImpl).eNotify(Notification) line: 444
WTPModulesResource(ResourceImpl).setModified(boolean) line: 1867
WTPModulesResource(TranslatorResourceImpl).doSave(OutputStream, Map) line: 192
WTPModulesResource(ResourceImpl).save(OutputStream, Map<?,?>) line: 1475
WTPModulesResource(ResourceImpl).save(Map<?,?>) line: 1044
WTPModulesResource(ReferencedXMIResourceImpl).save(Map) line: 377
WTPModulesResource(TranslatorResourceImpl).save(Map) line: 167
ModuleStructuralModel(EditModel).primSaveResource(Resource) line: 1303
ModuleStructuralModel(EditModel).saveResource(Resource) line: 1334
ModuleStructuralModel(EditModel).primSave(IProgressMonitor) line: 1269
EditModel$1.run(IProgressMonitor) line: 373
Workspace.run(ICoreRunnable, ISchedulingRule, int, IProgressMonitor) line: 2289
Workspace.run(IWorkspaceRunnable, ISchedulingRule, int, IProgressMonitor) line: 2316
ModuleStructuralModel.runSaveOperation(IWorkspaceRunnable, IProgressMonitor) line: 310
ModuleStructuralModel(EditModel).save(IProgressMonitor, Object) line: 376
ModuleStructuralModel.saveIfNecessary(IProgressMonitor, Object) line: 392
StructureEdit.saveIfNecessary(IProgressMonitor) line: 397
WebProjectConfiguratorDelegate(AbstractProjectConfiguratorDelegate).configureDeployedName(IProject, String) line: 189
{code}
But I dont see *J2EEDeployableFactory#clearCache* being called. Btw. I dont see J2EEDeployableFactory listening to resource change. Here are the listeners that I see registered:
* org.eclipse.emf.common.notify.impl.AdapterImpl@21197771
* org.eclipse.wst.common.internal.emfworkbench.integration.EditModel$ResourceAdapter@6bc55154
* org.eclipse.wst.common.internal.emfworkbench.WorkbenchResourceHelper$FileAdapter@3543d4e1
* EMF2DOMAdapterImpl(#document,WTPModulesResource), org.eclipse.wst.common.componentcore.internal.resources.VirtualComponent$ResourceAdapter@2e185af0
was (Author: adietish):
I think that I found where in m2e-wtp the module name is set: [AbstractProjectConfiguratorDelegate#configureDeployedName|https://github....]
And I see it being called, which then causes the file to change on disk.
[~rob.stryker] this then causes J2EEModuleVirtualComponent to clear it's cache:
{code}
J2EEModuleVirtualComponent(VirtualComponent).clearCache() line: 721
J2EEModuleVirtualComponent.clearCache() line: 512
J2EEModuleVirtualComponent(VirtualComponent).resourceChanged(Resource) line: 95
VirtualComponent$ResourceAdapter.notifyChanged(Notification) line: 78
WTPModulesResource(TranslatorResourceImpl).eNotify(Notification) line: 444
WTPModulesResource(ResourceImpl).setModified(boolean) line: 1867
WTPModulesResource(TranslatorResourceImpl).doSave(OutputStream, Map) line: 192
WTPModulesResource(ResourceImpl).save(OutputStream, Map<?,?>) line: 1475
WTPModulesResource(ResourceImpl).save(Map<?,?>) line: 1044
WTPModulesResource(ReferencedXMIResourceImpl).save(Map) line: 377
WTPModulesResource(TranslatorResourceImpl).save(Map) line: 167
ModuleStructuralModel(EditModel).primSaveResource(Resource) line: 1303
ModuleStructuralModel(EditModel).saveResource(Resource) line: 1334
ModuleStructuralModel(EditModel).primSave(IProgressMonitor) line: 1269
EditModel$1.run(IProgressMonitor) line: 373
Workspace.run(ICoreRunnable, ISchedulingRule, int, IProgressMonitor) line: 2289
Workspace.run(IWorkspaceRunnable, ISchedulingRule, int, IProgressMonitor) line: 2316
ModuleStructuralModel.runSaveOperation(IWorkspaceRunnable, IProgressMonitor) line: 310
ModuleStructuralModel(EditModel).save(IProgressMonitor, Object) line: 376
ModuleStructuralModel.saveIfNecessary(IProgressMonitor, Object) line: 392
StructureEdit.saveIfNecessary(IProgressMonitor) line: 397
WebProjectConfiguratorDelegate(AbstractProjectConfiguratorDelegate).configureDeployedName(IProject, String) line: 189
{code}
But I dont see *J2EEDeployableFactory#clearCache* being called. Btw. There doesn't see to be such listener attached and thus being informed upon resource change. Here are the listeners that I see registered:
* org.eclipse.emf.common.notify.impl.AdapterImpl@21197771
* org.eclipse.wst.common.internal.emfworkbench.integration.EditModel$ResourceAdapter@6bc55154
* org.eclipse.wst.common.internal.emfworkbench.WorkbenchResourceHelper$FileAdapter@3543d4e1
* EMF2DOMAdapterImpl(#document,WTPModulesResource), org.eclipse.wst.common.componentcore.internal.resources.VirtualComponent$ResourceAdapter@2e185af0
> Server adapter: doesn't respect openshift maven profile
> -------------------------------------------------------
>
> Key: JBIDE-22138
> URL: https://issues.jboss.org/browse/JBIDE-22138
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Environment: JBoss Developer Studio (Core Features) 9.1.0.GA-v20160403-1700-B477
> Openshift plugin 3.1.0.Final-v20160401-2357-B263
> Reporter: Rafael Benevides
> Assignee: Andre Dietisheim
> Labels: openshift_v3, server_adapter
> Fix For: 4.9.0.AM1
>
> Attachments: image-2018-06-22-19-02-57-247.png
>
>
> This is a follow up on JBIDE-22128.
> The maven profile is never read to determine the actual archive name. That will require more coupling to m2e, in order to load the pom.xml model using the openshift profile, if it exists, in order to determine the archive name. This will be a long running operation and will require more significant changes
> steps:
> # EXEC: follow steps outlined in https://github.com/redhat-helloworld-msa/helloworld-msa/blob/master/hello... (deploying with fabric8 maven plugin doesn't work, you end up having the pod failing with ImagePullBack error. You need to take the alternative road where you deploy via "oc new-build", "oc new-app", "oc expose" etc.)
> # EXEC: import the app into your Eclipse workspace
> # EXEC: "hello" (workspace) project: Properties > Maven > Active Maven Profile: set "openshift"
> # EXEC: create a server adapter and start it
> # ASSERT: adapter starts syncing, verify what war is used
> Result:
> The war that's created locally and then synced to the pod is "hello.war" even though the profile specifies "ROOT.war"
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26148) CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected $PATH)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26148?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26148:
-------------------------------------
Description:
[CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
{code:title=CommandLocationBinary}
public String findLocation(int timeout) {
if (foundLoc != null || searchFailed)
return foundLoc;
String searched = CommandLocationLookupStrategy.get().search(this, timeout);
if (searched == null) {
searchFailed = true;
}
foundLoc = searched;
return searched;
}
{code}
Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
What if I update my ex. correct a broken link to oc while I keep Eclipse running?
I'd think that one should be able to repeat the lookup if it fails since the user could modify it's system while he keeps Eclipse running. Afaics the current impl forces me to restart Eclipse.
was:
[CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
{code:title=CommandLocationBinary}
public String findLocation(int timeout) {
if (foundLoc != null || searchFailed)
return foundLoc;
String searched = CommandLocationLookupStrategy.get().search(this, timeout);
if (searched == null) {
searchFailed = true;
}
foundLoc = searched;
return searched;
}
{code}
Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
What if I update my ex. correct a broken link to oc while I keep Eclipse running?
I'd think that one should be able to repeat the lookup if it fails since the user could modify it's system while he keeps Eclipse running. Afaics the current impl forces me to restart Eclipse once I changed my $PATH.
> CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected $PATH)
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26148
> URL: https://issues.jboss.org/browse/JBIDE-26148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
>
> [CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
> {code:title=CommandLocationBinary}
> public String findLocation(int timeout) {
> if (foundLoc != null || searchFailed)
> return foundLoc;
> String searched = CommandLocationLookupStrategy.get().search(this, timeout);
> if (searched == null) {
> searchFailed = true;
> }
> foundLoc = searched;
> return searched;
> }
> {code}
> Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
> What if I update my ex. correct a broken link to oc while I keep Eclipse running?
> I'd think that one should be able to repeat the lookup if it fails since the user could modify it's system while he keeps Eclipse running. Afaics the current impl forces me to restart Eclipse.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26148) CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected a broken link)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26148?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26148:
-------------------------------------
Summary: CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected a broken link) (was: CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected $PATH))
> CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected a broken link)
> --------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26148
> URL: https://issues.jboss.org/browse/JBIDE-26148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
>
> [CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
> {code:title=CommandLocationBinary}
> public String findLocation(int timeout) {
> if (foundLoc != null || searchFailed)
> return foundLoc;
> String searched = CommandLocationLookupStrategy.get().search(this, timeout);
> if (searched == null) {
> searchFailed = true;
> }
> foundLoc = searched;
> return searched;
> }
> {code}
> Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
> What if I update my ex. correct a broken link to oc while I keep Eclipse running?
> I'd think that one should be able to repeat the lookup if it fails since the user could modify it's system while he keeps Eclipse running. Afaics the current impl forces me to restart Eclipse.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26148) CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected $PATH)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26148?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-26148:
-------------------------------------
Description:
[CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
{code:title=CommandLocationBinary}
public String findLocation(int timeout) {
if (foundLoc != null || searchFailed)
return foundLoc;
String searched = CommandLocationLookupStrategy.get().search(this, timeout);
if (searched == null) {
searchFailed = true;
}
foundLoc = searched;
return searched;
}
{code}
Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
What if I update my ex. correct a broken link to oc while I keep Eclipse running?
I'd think that one should be able to repeat the lookup if it fails since the user could modify it's system while he keeps Eclipse running. Afaics the current impl forces me to restart Eclipse once I changed my $PATH.
was:
[CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
{code:title=CommandLocationBinary}
public String findLocation(int timeout) {
if (foundLoc != null || searchFailed)
return foundLoc;
String searched = CommandLocationLookupStrategy.get().search(this, timeout);
if (searched == null) {
searchFailed = true;
}
foundLoc = searched;
return searched;
}
{code}
Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
What if I update my PATH while I keep Eclipse running?
I'd think that one should be able to repeat the lookup if it fails since the user could modify it's system while he keeps Eclipse running. Afaics the current impl forces me to restart Eclipse once I changed my $PATH.
> CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected $PATH)
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26148
> URL: https://issues.jboss.org/browse/JBIDE-26148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
>
> [CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
> {code:title=CommandLocationBinary}
> public String findLocation(int timeout) {
> if (foundLoc != null || searchFailed)
> return foundLoc;
> String searched = CommandLocationLookupStrategy.get().search(this, timeout);
> if (searched == null) {
> searchFailed = true;
> }
> foundLoc = searched;
> return searched;
> }
> {code}
> Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
> What if I update my ex. correct a broken link to oc while I keep Eclipse running?
> I'd think that one should be able to repeat the lookup if it fails since the user could modify it's system while he keeps Eclipse running. Afaics the current impl forces me to restart Eclipse once I changed my $PATH.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26148) CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected $PATH)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26148?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-26148 at 7/23/18 11:38 AM:
--------------------------------------------------------------------
[~rob.stryker] Ack on that but how often and when would that happen? Only when one starts the adapter up or maybe in the preferences. Situations where I'd think that the user expects heavier loads in Eclipse?
I believe that the $PATH is only loaded at vm startup, missing updates to it anyhow. So the only case that we can catch is where one corrects a missing link while keeping Eclipse running. I'd think that this is worth it, but arguable.
was (Author: adietish):
[~rob.stryker] Ack on that. And then I believe that the $PATH is only loaded at vm startup, missing updates to it anyhow.
> CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected $PATH)
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26148
> URL: https://issues.jboss.org/browse/JBIDE-26148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
>
> [CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
> {code:title=CommandLocationBinary}
> public String findLocation(int timeout) {
> if (foundLoc != null || searchFailed)
> return foundLoc;
> String searched = CommandLocationLookupStrategy.get().search(this, timeout);
> if (searched == null) {
> searchFailed = true;
> }
> foundLoc = searched;
> return searched;
> }
> {code}
> Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
> What if I update my PATH while I keep Eclipse running?
> I'd think that one should be able to repeat the lookup if it fails since the user could modify it's system while he keeps Eclipse running. Afaics the current impl forces me to restart Eclipse once I changed my $PATH.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-26148) CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected $PATH)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-26148?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-26148:
------------------------------------------
[~rob.stryker] Ack on that. And then I believe that the $PATH is only loaded at vm startup, missing updates to it anyhow.
> CommandLocationBinary: only searches once (wont retry if it fails, forcing me to restart Eclipse once I corrected $PATH)
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-26148
> URL: https://issues.jboss.org/browse/JBIDE-26148
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.6.0.AM3
> Reporter: Andre Dietisheim
> Assignee: Rob Stryker
>
> [CommandLocationBinary|https://github.com/adietish/jbosstools-openshift/bl...] allows to lookup a command (on the $PATH, etc.). But it'll only do so once:
> {code:title=CommandLocationBinary}
> public String findLocation(int timeout) {
> if (foundLoc != null || searchFailed)
> return foundLoc;
> String searched = CommandLocationLookupStrategy.get().search(this, timeout);
> if (searched == null) {
> searchFailed = true;
> }
> foundLoc = searched;
> return searched;
> }
> {code}
> Once the lookup failed, it'll store this in the var *searchFailed* and wont do it a 2nd time.
> What if I update my PATH while I keep Eclipse running?
> I'd think that one should be able to repeat the lookup if it fails since the user could modify it's system while he keeps Eclipse running. Afaics the current impl forces me to restart Eclipse once I changed my $PATH.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months
[JBoss JIRA] (JBIDE-25557) OpenJDK9 + org.jboss.forge: org.jboss.forge.furnace.exception.ContainerException
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25557?page=com.atlassian.jira.plugi... ]
Jeff MAURY commented on JBIDE-25557:
------------------------------------
[~jkopriva] can we close it ?
> OpenJDK9 + org.jboss.forge: org.jboss.forge.furnace.exception.ContainerException
> --------------------------------------------------------------------------------
>
> Key: JBIDE-25557
> URL: https://issues.jboss.org/browse/JBIDE-25557
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.5.2.AM3
> Environment: FC27 + OpenJDK9
> Red Hat JBoss Developer Studio Version: 11.2.0.AM3
> Reporter: Josef Kopriva
> Assignee: Jeff MAURY
> Priority: Critical
> Fix For: 4.9.x
>
>
> Forge does not start:
> {code:java}
> null
> org.eclipse.core.jobs
> Error
> Thu Jan 11 12:59:40 CET 2018
> An internal error occurred during: "Starting JBoss Forge 3.7.2.Final".
> org.jboss.forge.furnace.exception.ContainerException: No services of type [org.jboss.forge.addon.projects.ProjectFactory] could be found in any started addons.
> at org.jboss.forge.furnace.impl.addons.ImportedImpl.get(ImportedImpl.java:79)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:97)
> at org.jboss.forge.furnace.services.Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.get(Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.java)
> at org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:95)
> at org.jboss.tools.forge.ui.util.ForgeHelper.initializeFurnaceRuntime(ForgeHelper.java:99)
> at org.jboss.tools.forge.ui.util.ForgeHelper.access$0(ForgeHelper.java:89)
> at org.jboss.tools.forge.ui.util.ForgeHelper$1.runInWorkspace(ForgeHelper.java:57)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
> {code:java}
> null
> org.eclipse.ui
> Error
> Thu Jan 11 12:59:40 CET 2018
> Unhandled event loop exception
> org.jboss.forge.furnace.exception.ContainerException: No services of type [org.jboss.forge.addon.shell.spi.ShellHandle] could be found in any started addons.
> at org.jboss.forge.furnace.impl.addons.ImportedImpl.get(ImportedImpl.java:79)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
> at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
> at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:97)
> at org.jboss.forge.furnace.services.Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.get(Imported_$$_javassist_4e1fc78d-0b5f-4839-8d1e-22b7d372d229.java)
> at org.jboss.tools.forge.core.furnace.FurnaceService.lookup(FurnaceService.java:95)
> at org.jboss.tools.forge.ui.internal.cli.AeshConsole.start(AeshConsole.java:46)
> at org.jboss.tools.aesh.ui.view.AbstractTextViewer$1.run(AbstractTextViewer.java:46)
> at org.eclipse.ui.internal.PendingSyncExec.run(PendingSyncExec.java:58)
> at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:168)
> at org.eclipse.ui.internal.UISynchronizer.lambda$0(UISynchronizer.java:150)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:37)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4577)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4186)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1150)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1039)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:153)
> at org.eclipse.ui.internal.Workbench.lambda$3(Workbench.java:680)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:594)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:151)
> 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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 8 months