[JBoss JIRA] (JBIDE-16597) OpenShift Server Adapter: Open launch configuration cause error
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16597?page=com.atlassian.jira.plugi... ]
Marián Labuda updated JBIDE-16597:
----------------------------------
Attachment: open_launch_config3.png
open_launch_config2.png
open_launch_config1.png
> OpenShift Server Adapter: Open launch configuration cause error
> ---------------------------------------------------------------
>
> Key: JBIDE-16597
> URL: https://issues.jboss.org/browse/JBIDE-16597
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Assignee: Andre Dietisheim
> Attachments: open_launch_config1.png, open_launch_config2.png, open_launch_config3.png
>
>
> In OpenShift server adapter settings is Open launch configuration link. Throws error after click on it. See attached images and error log:
> {code:title=.log}
> !ENTRY org.eclipse.ui 4 0 2014-02-17 13:45:08.437
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.handleApplyPressed(LaunchConfigurationTabGroupViewer.java:1401)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$3.widgetSelected(LaunchConfigurationTabGroupViewer.java:308)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4423)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1154)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationPropertiesDialog.open(LaunchConfigurationPropertiesDialog.java:213)
> at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:661)
> at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:638)
> at org.eclipse.wst.server.ui.internal.editor.OverviewEditorPart$9.linkActivated(OverviewEditorPart.java:594)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4423)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-16596) OpenShift Server Adapter: Timeouts and publishing fields are too small
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-16596:
-------------------------------------
Summary: OpenShift Server Adapter: Timeouts and publishing fields are too small
Key: JBIDE-16596
URL: https://issues.jboss.org/browse/JBIDE-16596
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.2.0.Alpha2
Reporter: Marián Labuda
Assignee: Andre Dietisheim
Priority: Minor
Attachments: small_field.png
In Server View double click on any OpenShift server adapter to open adapter settings. There are 2 fields for timeout settings and one for publishing which are too small. See attached image. It is impossible to see values (just only through hoovering).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-16595) Forge shows error when running IDE with Java 6
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16595?page=com.atlassian.jira.plugi... ]
Koen Aers reassigned JBIDE-16595:
---------------------------------
Assignee: Koen Aers
> Forge shows error when running IDE with Java 6
> ----------------------------------------------
>
> Key: JBIDE-16595
> URL: https://issues.jboss.org/browse/JBIDE-16595
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.Alpha2
> Reporter: Pavol Srna
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.2.0.Alpha2
>
> Attachments: forge-err.png
>
>
> StackTrace:
> ----------------
> org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.forge.ui.ext [1039]
> Unresolved requirement: osgi.wiring.bundle; filter:="(osgi.wiring.bundle=org.jboss.tools.forge2.runtime)"
> -> osgi.wiring.bundle; osgi.wiring.bundle="org.jboss.tools.forge2.runtime"; bundle-version:Version="2.0.1.Alpha2-v20140212-0016-B11"; singleton:="true"
> org.jboss.tools.forge2.runtime [1042]
> Unresolved requirement: osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))"
> at org.eclipse.osgi.container.Module.start(Module.java:424)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1551)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1502)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1445)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
> Caused by: org.osgi.service.resolver.ResolutionException: Unable to resolve osgi.identity; osgi.identity="org.jboss.tools.forge.ui.ext"; type="osgi.bundle"; version:Version="1.1.0.Alpha2-v20140212-0016-B11"; singleton:="true": missing requirement osgi.wiring.bundle; filter:="(osgi.wiring.bundle=org.jboss.tools.forge2.runtime)" [caused by: Unable to resolve osgi.identity; osgi.identity="org.jboss.tools.forge2.runtime"; type="osgi.bundle"; version:Version="2.0.1.Alpha2-v20140212-0016-B11"; singleton:="true": missing requirement osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))"]
> at org.apache.felix.resolver.Candidates.populateResource(Candidates.java:291)
> at org.apache.felix.resolver.Candidates.populate(Candidates.java:154)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:146)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolveSingleRevision(ModuleResolver.java:948)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:874)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:111)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:471)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:429)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:419)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> ... 7 more
> Root exception:
> org.osgi.service.resolver.ResolutionException: Unable to resolve osgi.identity; osgi.identity="org.jboss.tools.forge.ui.ext"; type="osgi.bundle"; version:Version="1.1.0.Alpha2-v20140212-0016-B11"; singleton:="true": missing requirement osgi.wiring.bundle; filter:="(osgi.wiring.bundle=org.jboss.tools.forge2.runtime)" [caused by: Unable to resolve osgi.identity; osgi.identity="org.jboss.tools.forge2.runtime"; type="osgi.bundle"; version:Version="2.0.1.Alpha2-v20140212-0016-B11"; singleton:="true": missing requirement osgi.ee; filter:="(&(osgi.ee=JavaSE)(version=1.7))"]
> at org.apache.felix.resolver.Candidates.populateResource(Candidates.java:291)
> at org.apache.felix.resolver.Candidates.populate(Candidates.java:154)
> at org.apache.felix.resolver.ResolverImpl.resolve(ResolverImpl.java:146)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolveSingleRevision(ModuleResolver.java:948)
> at org.eclipse.osgi.container.ModuleResolver$ResolveProcess.resolve(ModuleResolver.java:874)
> at org.eclipse.osgi.container.ModuleResolver.resolveDelta(ModuleResolver.java:111)
> at org.eclipse.osgi.container.ModuleContainer.resolveAndApply(ModuleContainer.java:471)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:429)
> at org.eclipse.osgi.container.ModuleContainer.resolve(ModuleContainer.java:419)
> at org.eclipse.osgi.container.Module.start(Module.java:406)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1551)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1530)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1502)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1445)
> at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-16370) evaluate creating OSGi bindex
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16370?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16370:
-----------------------------------
Description:
bindex is the standard for provisionning in OSGi < R5. It would be useful to provide bindex for locus (as well as p2 metadata) if we have some other OSGi projects at JBoss willing to consume some Locus bundles.
In a longer-term future, we can imagine that p2 conforms to OSGi standards
> evaluate creating OSGi bindex
> -----------------------------
>
> Key: JBIDE-16370
> URL: https://issues.jboss.org/browse/JBIDE-16370
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, locus
> Environment: Since it is easy to create OSGi bindex (equivalent of p2, but specified by OSGi standard, works outside of Eclipse) using https://github.com/bndtools/bindex , it would be nice to include those bindex in the p2 repo we deliver to support standards as well.
> Reporter: Mickael Istria
> Priority: Optional
> Fix For: 4.2.x
>
>
> bindex is the standard for provisionning in OSGi < R5. It would be useful to provide bindex for locus (as well as p2 metadata) if we have some other OSGi projects at JBoss willing to consume some Locus bundles.
> In a longer-term future, we can imagine that p2 conforms to OSGi standards
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-16370) evaluate creating OSGi bindex
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16370?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16370:
-----------------------------------
Environment: (was: Since it is easy to create OSGi bindex (equivalent of p2, but specified by OSGi standard, works outside of Eclipse) using https://github.com/bndtools/bindex , it would be nice to include those bindex in the p2 repo we deliver to support standards as well.)
> evaluate creating OSGi bindex
> -----------------------------
>
> Key: JBIDE-16370
> URL: https://issues.jboss.org/browse/JBIDE-16370
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, locus
> Reporter: Mickael Istria
> Priority: Optional
> Fix For: 4.2.x
>
>
> bindex is the standard for provisionning in OSGi < R5. It would be useful to provide bindex for locus (as well as p2 metadata) if we have some other OSGi projects at JBoss willing to consume some Locus bundles.
> In a longer-term future, we can imagine that p2 conforms to OSGi standards
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-16370) evaluate creating OSGi bindex
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16370?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-16370:
-----------------------------------
Description:
Since it is easy to create OSGi bindex (equivalent of p2, but specified by OSGi standard, works outside of Eclipse) using https://github.com/bndtools/bindex , it would be nice to include those bindex in the p2 repo we deliver to support standards as well.
That would allow other projects doing OSGi but not p2 to consume Locus artifacts.
was:
bindex is the standard for provisionning in OSGi < R5. It would be useful to provide bindex for locus (as well as p2 metadata) if we have some other OSGi projects at JBoss willing to consume some Locus bundles.
In a longer-term future, we can imagine that p2 conforms to OSGi standards
> evaluate creating OSGi bindex
> -----------------------------
>
> Key: JBIDE-16370
> URL: https://issues.jboss.org/browse/JBIDE-16370
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, locus
> Reporter: Mickael Istria
> Priority: Optional
> Fix For: 4.2.x
>
>
> Since it is easy to create OSGi bindex (equivalent of p2, but specified by OSGi standard, works outside of Eclipse) using https://github.com/bndtools/bindex , it would be nice to include those bindex in the p2 repo we deliver to support standards as well.
> That would allow other projects doing OSGi but not p2 to consume Locus artifacts.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months
[JBoss JIRA] (JBIDE-16368) Clean useless features from TP
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16368?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16368:
---------------------------------------------
moved this is of 4.2.x since work is being done.
> Clean useless features from TP
> ------------------------------
>
> Key: JBIDE-16368
> URL: https://issues.jboss.org/browse/JBIDE-16368
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: target-platform
> Affects Versions: 4.2.x
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Optional
> Fix For: 4.2.0.Beta1
>
>
> In order to trim some stuff out of our target-platform, we should:
> * Install JBDS from installer
> * Look at its content in plugins/ and features/ and compare it with content of the TP site.
> Everything that is in TP site but not in JBDS is probably worth being removed from TP.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 2 months