Latest ME2015 update breaks spring and task list (mylyn)

MyEclipse IDE

Installation, Configuration & Updates

This topic has 4 replies, 3 voices, and was last updated 9 years ago by Brian Fernandes.

Viewing 5 posts - 1 through 5 (of 5 total)

Author

Posts

March 26, 2015 at 11:59 am #353973 Reply

atomz4peace

Participant

I just did the latest rolling update to 2015CI and now my Spring Explorer and Task List (mylyn) view windows just say:

Could not create the view: org.springframework.ide.eclipse.ui.navigator.springExplorer

Could not create the view: org.eclipse.mylyn.tasks.ui.views.tasks

I have lots of errors in the error log, including many of “FrameworkEvent ERROR”. The first in the list is pasted below.

Can anyone help?

org.osgi.framework.BundleException: Could not resolve module: com.genuitec.eclipse.lib.spring41 [2316]
  Unresolved requirement: Require-Bundle: com.genuitec.eclipse.maven
    -> Bundle-SymbolicName: com.genuitec.eclipse.maven; bundle-version="13.0.0.me201411120556"; singleton:="true"
       com.genuitec.eclipse.maven [1820]
         Unresolved requirement: Require-Bundle: org.eclipse.m2e.editor
           -> Bundle-SymbolicName: org.eclipse.m2e.editor; bundle-version="1.5.0.me201405280815"; singleton:="true"
              org.eclipse.m2e.editor [956]
                Unresolved requirement: Require-Bundle: org.eclipse.m2e.core.ui; bundle-version="[1.5.0,1.6.0)"
                  -> Bundle-SymbolicName: org.eclipse.m2e.core.ui; bundle-version="1.5.0.me201503191638"; singleton:="true"
                     org.eclipse.m2e.core.ui [2699]
                       Unresolved requirement: Require-Bundle: org.eclipse.m2e.core; bundle-version="[1.5.0,1.6.0)"
                         -> Bundle-SymbolicName: org.eclipse.m2e.core; bundle-version="1.5.0.me201410311552"; singleton:="true"
                            org.eclipse.m2e.core [1871]
                              No resolution report for the bundle.                Unresolved requirement: Require-Bundle: org.eclipse.m2e.editor.xml; bundle-version="[1.5.0,1.6.0)"
                  -> Bundle-SymbolicName: org.eclipse.m2e.editor.xml; bundle-version="1.5.0.me201406190457"; singleton:="true"
                     org.eclipse.m2e.editor.xml [957]
                       Unresolved requirement: Require-Bundle: org.eclipse.m2e.core.ui; bundle-version="[1.5.0,1.6.0)"
                         -> Bundle-SymbolicName: org.eclipse.m2e.core.ui; bundle-version="1.5.0.me201503191638"; singleton:="true"
                       Unresolved requirement: Require-Bundle: org.eclipse.m2e.core; bundle-version="[1.5.0,1.6.0)"
                         -> Bundle-SymbolicName: org.eclipse.m2e.core; bundle-version="1.5.0.me201410311552"; singleton:="true"
                Unresolved requirement: Require-Bundle: org.eclipse.m2e.core; bundle-version="[1.5.0,1.6.0)"
                  -> Bundle-SymbolicName: org.eclipse.m2e.core; bundle-version="1.5.0.me201410311552"; singleton:="true"
         Unresolved requirement: Require-Bundle: org.eclipse.m2e.jdt; bundle-version="1.0.0"
           -> Bundle-SymbolicName: org.eclipse.m2e.jdt; bundle-version="1.5.0.me201411120556"; singleton:="true"
              org.eclipse.m2e.jdt [1872]
                Unresolved requirement: Require-Bundle: org.eclipse.m2e.core; bundle-version="[1.5.0,1.6.0)"
                  -> Bundle-SymbolicName: org.eclipse.m2e.core; bundle-version="1.5.0.me201410311552"; singleton:="true"
         Unresolved requirement: Require-Bundle: org.eclipse.m2e.core; bundle-version="1.0.0"
           -> Bundle-SymbolicName: org.eclipse.m2e.core; bundle-version="1.5.0.me201410311552"; singleton:="true"
         Unresolved requirement: Require-Bundle: org.eclipse.m2e.core.ui; bundle-version="1.0.0"
           -> Bundle-SymbolicName: org.eclipse.m2e.core.ui; bundle-version="1.5.0.me201503191638"; singleton:="true"
         Unresolved requirement: Require-Bundle: org.eclipse.m2e.editor.xml; bundle-version="1.2.0"
           -> Bundle-SymbolicName: org.eclipse.m2e.editor.xml; bundle-version="1.5.0.me201406190457"; singleton:="true"
         Unresolved requirement: Require-Bundle: org.eclipse.m2e.launching; bundle-version="1.0.0"
           -> Bundle-SymbolicName: org.eclipse.m2e.launching; bundle-version="1.5.0.me201405280815"; singleton:="true"
              org.eclipse.m2e.launching [960]
                Unresolved requirement: Require-Bundle: org.eclipse.m2e.core; bundle-version="[1.5.0,1.6.0)"
                  -> Bundle-SymbolicName: org.eclipse.m2e.core; bundle-version="1.5.0.me201410311552"; singleton:="true"
                Unresolved requirement: Require-Bundle: org.eclipse.m2e.core.ui; bundle-version="[1.5.0,1.6.0)"
                  -> Bundle-SymbolicName: org.eclipse.m2e.core.ui; bundle-version="1.5.0.me201503191638"; singleton:="true"
  Bundle was not resolved because of a uses contraint violation.
  org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.m2e.core [osgi.identity; osgi.identity="org.eclipse.m2e.core"; type="osgi.bundle"; version:Version="1.5.0.me201410311552"; singleton:="true"] because it is exposed to package 'javax.annotation' from resources org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.2.v20150203-1939"; singleton:="true"] and javax.annotation [osgi.identity; osgi.identity="javax.annotation"; type="osgi.bundle"; version:Version="1.2.0.me20130426-1947"] via two dependency chains.

Chain 1:
  org.eclipse.m2e.core [osgi.identity; osgi.identity="org.eclipse.m2e.core"; type="osgi.bundle"; version:Version="1.5.0.me201410311552"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.eclipse.core.runtime)(bundle-version>=3.7.0))
     |
    provide: osgi.wiring.bundle: org.eclipse.core.runtime
  org.eclipse.osgi [osgi.identity; osgi.identity="org.eclipse.osgi"; type="osgi.bundle"; version:Version="3.10.2.v20150203-1939"; singleton:="true"]

Chain 2:
  org.eclipse.m2e.core [osgi.identity; osgi.identity="org.eclipse.m2e.core"; type="osgi.bundle"; version:Version="1.5.0.me201410311552"; singleton:="true"]
    require: (&(osgi.wiring.bundle=com.google.guava)(&(bundle-version>=14.0.1)(!(bundle-version>=16.0.0))))
     |
    provide: osgi.wiring.bundle; osgi.wiring.bundle="com.google.guava"; bundle-version:Version="15.0.0.v201403281430"
  com.google.guava [osgi.identity; osgi.identity="com.google.guava"; type="osgi.bundle"; version:Version="15.0.0.v201403281430"]
    import: (osgi.wiring.package=javax.annotation)
     |
    export: osgi.wiring.package: javax.annotation
  javax.annotation [osgi.identity; osgi.identity="javax.annotation"; type="osgi.bundle"; version:Version="1.2.0.me20130426-1947"]
    at org.eclipse.osgi.container.Module.start(Module.java:434)
    at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
    at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1561)
    at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
    at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
    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)

March 26, 2015 at 10:35 pm #353975 Reply

support-swapna

Moderator

Hi,

Sorry that you are seeing this issue. We do not see any issues with the update to CI 12 at our end.

Please start MyEclipse with -clean command args and check if it resolves the issue.
If the issue persists, please reverse to CI 11 from the update wizard and try to upgrade again.

Once upgraded, start MyEclipse with -clean switch and check how it works. Alternatively, you could try installing through the CI 12 offline / online installers available here.

Please also share your OS and version details.

Let us know how it works for you.

March 27, 2015 at 1:08 am #353976 Reply

atomz4peace

Participant

the -clean did the trick, thank you!

March 27, 2015 at 6:51 am #353981 Reply

support-swapna

Moderator

Hi,

Glad that it is working.
Let us know if you see any issues.

April 2, 2015 at 4:50 pm #354021 Reply

Brian Fernandes

Moderator

For others coming late to this thread, please see: https://www.genuitec.com/forums/topic/issues-upgrading-to-2015-ci-12/ for additional details.

Atomz,

Just a few questions that could help us replicate this issue internally:
1) Could you tell us what version of 2015 CI you were on prior to this fix? if you’ve been on the CI stream for some time, roughly how many upgrades have you gone through?

2) Had you installed any additional plugins into MyEclipse?

Thanks and sorry for the inconvenience caused.

Author

Posts

Viewing 5 posts - 1 through 5 (of 5 total)