Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Eclipse Projects » Virgo » Virgo tooling and Oxygen(Tooling doesn't work after installation)
Virgo tooling and Oxygen [message #1769320] Sat, 29 July 2017 12:25 Go to next message
Bill Mair is currently offline Bill MairFriend
Messages: 72
Registered: July 2009
Member
I tried "http://download.eclipse.org/virgo/snapshot/tooling" and "http://download.eclipse.org/virgo/release/updatesite/3.7.2.RELEASE" (I didn't try "http://download.eclipse.org/virgo/milestone/tooling").

When I try to open the Server configuration dialog I get the following error:

org.eclipse.core.runtime.AssertionFailedException: assertion failed: 
	at org.eclipse.core.runtime.Assert.isTrue(Assert.java:110)
	at org.eclipse.core.runtime.Assert.isTrue(Assert.java:96)
	at org.eclipse.ui.part.MultiPageEditorPart.setActivePage(MultiPageEditorPart.java:1075)
	at org.eclipse.ui.part.MultiPageEditorPart.createPartControl(MultiPageEditorPart.java:352)
	at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.createPartControl(CompatibilityPart.java:151)
	at org.eclipse.ui.internal.e4.compatibility.CompatibilityEditor.createPartControl(CompatibilityEditor.java:99)
	at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.create(CompatibilityPart.java:355)
	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:498)
	at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
	at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:990)
	at org.eclipse.e4.core.internal.di.InjectorImpl.processAnnotated(InjectorImpl.java:955)
	at org.eclipse.e4.core.internal.di.InjectorImpl.inject(InjectorImpl.java:124)
	at org.eclipse.e4.core.internal.di.InjectorImpl.internalMake(InjectorImpl.java:399)
	at org.eclipse.e4.core.internal.di.InjectorImpl.make(InjectorImpl.java:318)
	at org.eclipse.e4.core.contexts.ContextInjectionFactory.make(ContextInjectionFactory.java:162)
	at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.createFromBundle(ReflectionContributionFactory.java:105)
	at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.doCreate(ReflectionContributionFactory.java:74)
	at org.eclipse.e4.ui.internal.workbench.ReflectionContributionFactory.create(ReflectionContributionFactory.java:56)
	at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer.createWidget(ContributedPartRenderer.java:129)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createWidget(PartRenderingEngine.java:997)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:666)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:772)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:743)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:737)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:721)
	at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$1.handleEvent(PartServiceImpl.java:104)
	at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:40)
	at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:233)
	at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:144)
	at org.eclipse.swt.widgets.Display.syncExec(Display.java:5439)
	at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:212)
	at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:36)
	at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:201)
	at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
	at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
	at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
	at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
	at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
	at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
	at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
	at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:52)
	at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:60)
	at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
	at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:173)
	at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:620)
	at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:584)
	at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:768)
	at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.bringToTop(PartServiceImpl.java:401)
	at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.showPart(PartServiceImpl.java:1187)
	at org.eclipse.ui.internal.WorkbenchPage.busyOpenEditor(WorkbenchPage.java:3261)
	at org.eclipse.ui.internal.WorkbenchPage.access$25(WorkbenchPage.java:3176)
	at org.eclipse.ui.internal.WorkbenchPage$10.run(WorkbenchPage.java:3158)
	at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3153)
	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3117)
	at org.eclipse.ui.internal.WorkbenchPage.openEditor(WorkbenchPage.java:3098)
	at org.eclipse.wst.server.ui.internal.ServerUIPlugin.editServer(ServerUIPlugin.java:447)
	at org.eclipse.wst.server.ui.internal.ServerUIPlugin.editServer(ServerUIPlugin.java:430)
	at org.eclipse.wst.server.ui.internal.view.servers.OpenAction.perform(OpenAction.java:36)
	at org.eclipse.wst.server.ui.internal.view.servers.AbstractServerAction.run(AbstractServerAction.java:64)
	at org.eclipse.ui.actions.RetargetAction.run(RetargetAction.java:216)
	at org.eclipse.ui.navigator.CommonNavigatorManager$2.open(CommonNavigatorManager.java:191)
	at org.eclipse.ui.OpenAndLinkWithEditorHelper$InternalListener.open(OpenAndLinkWithEditorHelper.java:46)
	at org.eclipse.jface.viewers.StructuredViewer$2.run(StructuredViewer.java:851)
	at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
	at org.eclipse.ui.internal.JFaceUtil.lambda$0(JFaceUtil.java:44)
	at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
	at org.eclipse.jface.viewers.StructuredViewer.fireOpen(StructuredViewer.java:848)
	at org.eclipse.jface.viewers.StructuredViewer.handleOpen(StructuredViewer.java:1163)
	at org.eclipse.ui.navigator.CommonViewer.handleOpen(CommonViewer.java:451)
	at org.eclipse.jface.util.OpenStrategy.fireOpenEvent(OpenStrategy.java:273)
	at org.eclipse.jface.util.OpenStrategy.access$2(OpenStrategy.java:268)
	at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:308)
	at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:86)
	at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5252)
	at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1348)
	at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4522)
	at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4107)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$5.run(PartRenderingEngine.java:1155)
	at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
	at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1044)
	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 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:498)
	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)


Is this an incompatibility issue or do I need to install something else?
Re: Virgo tooling and Oxygen [message #1769322 is a reply to message #1769320] Sat, 29 July 2017 12:36 Go to previous messageGo to next message
daniel marthaler is currently offline daniel marthalerFriend
Messages: 77
Registered: April 2012
Location: Z├╝rich
Member
Hi Bill

Please install the tooling from http://download.eclipse.org/virgo/release/tooling, as recommended on the Tooling Wiki page.

Regards,
Dani
Re: Virgo tooling and Oxygen [message #1769323 is a reply to message #1769322] Sat, 29 July 2017 12:43 Go to previous messageGo to next message
Bill Mair is currently offline Bill MairFriend
Messages: 72
Registered: July 2009
Member
Hi Dani,

I get the following error when trying that:

Cannot complete the install because one or more required items could not be found.
  Software being installed: Eclipse Virgo Tools 1.5.0.R01-RELEASE (org.eclipse.virgo.ide.feature.feature.group 1.5.0.R01-RELEASE)
  Missing requirement: Eclipse Virgo IDE (Bundlor Core) 1.5.0.R01-RELEASE (org.eclipse.virgo.ide.bundlor.core 1.5.0.R01-RELEASE) requires 'bundle org.objectweb.asm [3.1.0,4.0.0)' but it could not be found
  Cannot satisfy dependency:
    From: Eclipse Virgo Tools 1.5.0.R01-RELEASE (org.eclipse.virgo.ide.feature.feature.group 1.5.0.R01-RELEASE)
    To: org.eclipse.virgo.ide.bundlor.core [1.5.0.R01-RELEASE]
Re: Virgo tooling and Oxygen [message #1769373 is a reply to message #1769323] Mon, 31 July 2017 07:11 Go to previous messageGo to next message
GianMaria Romanato is currently offline GianMaria RomanatoFriend
Messages: 49
Registered: November 2015
Member
Hi Bill,

try adding the Eclipse Orbit bundle repository [1] to the list of known repositories [2] and then make sure to check "Contact all update sites during install to find required required software" in the installation dialog.
Please let me know if it works for you in this way.

[1] http://download.eclipse.org/tools/orbit/R-builds/R20170516192513/repository/
[2] Preferences -> Install/Update -> Available Software Sites

GianMaria.
Re: Virgo tooling and Oxygen [message #1769391 is a reply to message #1769320] Mon, 31 July 2017 09:55 Go to previous messageGo to next message
Bill Mair is currently offline Bill MairFriend
Messages: 72
Registered: July 2009
Member
Hi GianMaria,

I've added that repository, now I get:

Cannot complete the install because one or more required items could not be found.
  Software being installed: Eclipse Virgo Tools 1.5.0.R01-RELEASE (org.eclipse.virgo.ide.feature.feature.group 1.5.0.R01-RELEASE)
  Missing requirement: Artifact Repository 3.7.0.D-20150624084347 (org.eclipse.virgo.repository 3.7.0.D-20150624084347) requires 'package org.eclipse.virgo.util.osgi.manifest [3.7.0,4.0.0)' but it could not be found
  Cannot satisfy dependency:
    From: Eclipse Virgo Tools 1.5.0.R01-RELEASE (org.eclipse.virgo.ide.feature.feature.group 1.5.0.R01-RELEASE)
    To: org.eclipse.virgo.repository [3.7.0.D-20150624084347]
Re: Virgo tooling and Oxygen [message #1769395 is a reply to message #1769391] Mon, 31 July 2017 10:06 Go to previous messageGo to next message
GianMaria Romanato is currently offline GianMaria RomanatoFriend
Messages: 49
Registered: November 2015
Member
That's a package from a bundle of the Virgo Server. You also have to add the Virgo Server P2 repository [1] to the list of known repositories.

[1] http://download.eclipse.org/virgo/release/updatesite/3.7.2.RELEASE/
Re: Virgo tooling and Oxygen [message #1769405 is a reply to message #1769395] Mon, 31 July 2017 11:00 Go to previous messageGo to next message
Bill Mair is currently offline Bill MairFriend
Messages: 72
Registered: July 2009
Member
Hi GianMaria,

That did the trick. I'm sure that I didn't have include those sites before but it has now installed.

Thanks,

Bill
Re: Virgo tooling and Oxygen [message #1772043 is a reply to message #1769405] Mon, 04 September 2017 14:31 Go to previous messageGo to next message
Bill Mair is currently offline Bill MairFriend
Messages: 72
Registered: July 2009
Member
Hi, my customer is having the same problems. Weren't all the required plugins/bundles on the Virgo tooling updates site previously?

It is a real pain to have to link to 3 different sites, especially if you are behind an enterprise firewall and have a Nexus server proxy for all external sites.

Would it be possible to have all the plugins that are required for Virgo tooling to install all in one place?
Re: Virgo tooling and Oxygen [message #1772100 is a reply to message #1772043] Tue, 05 September 2017 13:59 Go to previous messageGo to next message
GianMaria Romanato is currently offline GianMaria RomanatoFriend
Messages: 49
Registered: November 2015
Member
Hi Bill,

the reason is that starting from version 1.5 the Virgo Tools depend on an additional Virgo Server bundle. Additionally, the Virgo Tools depend on Eclipse itself. Now, not all Eclipse versions and all Virgo versions have the same transitive dependencies and depending on which version of Virgo you are using and which version of Eclipse you are using some libraries needed by the Tooling may be pulled as transitive dependencies or may have to be taken somewhere else during installation.

At first sight it may seem that the simplest thing to do would be to simply ship those dependencies with the Tools themselves, but this may in reality lead to other issues.
For example, we recently changed one dependency of Virgo 3.7 Server to require a minimum version of a logging library rather than an exact version [1], because otherwise the installation of the Virgo Tools 1.5.1-SNAPSHOT in Eclipse Mars would pull that exact version of the library in Eclipse as Eclipse Mars uses a different and older version of the same. Then Eclipse would fail to start due to use-conflicts on the library packages.

If I change the Virgo Tools package to include some transitive dependencies I may solve the problem for you, but I am afraid it may become more difficult for people to install the Virgo Tools and use them with Virgo 3.5 or simply use them on an Eclipse version other than Mars or which contains additional third-party plug-ins. At the moment I don't have enough spare time to test all the possible combinations so I am trying to be conservative.

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=517499

GianMaria.

[Updated on: Tue, 05 September 2017 14:01]

Report message to a moderator

Re: Virgo tooling and Oxygen [message #1772102 is a reply to message #1772100] Tue, 05 September 2017 14:04 Go to previous messageGo to next message
GianMaria Romanato is currently offline GianMaria RomanatoFriend
Messages: 49
Registered: November 2015
Member
Bill,

if you want to provide a more smooth experience for your client you may want to consider preparing an Eclipse package for them. You could for example start from Eclipse for Java EE developers and install required dependencies using p2 director from the command line. An example is here [2].

GianMaria.

[2] https://stackoverflow.com/questions/44396777/eclipse-virgo-tooling-plugin-installation-using-p2-directory/
Re: Virgo tooling and Oxygen [message #1772131 is a reply to message #1772102] Tue, 05 September 2017 21:26 Go to previous message
Bill Mair is currently offline Bill MairFriend
Messages: 72
Registered: July 2009
Member
Hi GianMaria,

I think that the wiki page has to reflect these changes. There is no mention at https://wiki.eclipse.org/Virgo/Tooling of any of the above additional sites and the changes that you have described.

It would then be easier to preconfigure the update sites in the Nexus proxy (none of the computers in the customer's network have direct access to the web). Maybe some kind of table with the sites required for what eclipse and virgo version?

I think that customers could then simply mirror/scan/cache all of them to make sure that everything is available when installing the possible "in house" combinations.

Bill
Previous Topic:Removal of "old" Virgo versions from Virgo Download page
Next Topic:SLF4J distribution changed in 3.7.x
Goto Forum:
  


Current Time: Fri Nov 16 07:22:43 GMT 2018

Powered by FUDForum. Page generated in 0.04486 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top