Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [papyrus-rt-dev] Developer Setup Updates for Oxygen
Ugh.  That’s a new installation?  Not an upgrade of a previous installation?  If so, this needs to come to the attention of the Planning Council.

BTW, a problem like this should have nothing to do with using bundle pools or not.  The bundle pool is just a shareable storage of JARs and other artifacts.  It doesn’t alter the configuration of a p2-based installation, the Equinox framework, or resolution of bundle dependencies.  It only serves to avoid duplication of artifacts amongst multiple Eclipse configurations.

Cheers,

Christian

On May 29, 2017, 08:56 -0400, Peter Cigéhn <peter.cigehn@xxxxxxxxx>, wrote:
Hi,

Just for the sake of it I only installed the committer's package using the Eclipse Installer, without even adding the Papyrus-RT project (or any of its sub-projects). And I still bump into these wiring issues. So it seem unrelated to anything from the Papyrus-RT developer setup.

/Peter Cigéhn

On 29 May 2017 at 14:11, Peter Cigéhn <peter.cigehn@xxxxxxxxx> wrote:
Hi,

Am I the only one that still bump into the wiring issues? Now I have tried to update my development environment both on my laptop at home, as well as my laptop at the office. In both cases I still get the wiring issues. It takes an extremely long time to startup the first time, and then I get a number of FrameworkEvent.ERROR in the error log (see below). Before going ahead an nuke my p2 bundle pool and start all over with all my installations sharing this bundle pool, I just want to know if anyone else also gets these wiring issues. We had some of these wiring issues pre-M7 also with Papyrus-RT tester installation. And as Christian stated, they should have been fixed for M7, and the wiring issues for Papyrus-RT did went away for after M7. I have never installed the committer's package for Oxygen, so I don't know if it actually worked for M7, or if things have regressed for RC1 once again. Or if it just my bundle pool that have gone bananas (but it is strange that it is happening for both my laptop at home as well as at the office).

/Peter Cigéhn

!ENTRY org.eclipse.epp.mpc.core 4 0 2017-05-29 13:55:43.679
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.epp.mpc.core [228]
  Unresolved requirement: Require-Bundle: org.eclipse.userstorage.oauth; bundle-version="[1.0.0,2.0.0)"
    -> Bundle-SymbolicName: org.eclipse.userstorage.oauth; bundle-version="1.0.0.v20170519-1728"; singleton:="true"
       org.eclipse.userstorage.oauth [1028]
         Unresolved requirement: Require-Bundle: org.eclipse.userstorage.ui; bundle-version="1.0.0"
           -> Bundle-SymbolicName: org.eclipse.userstorage.ui; bundle-version="1.0.1.v20170201-1648"; singleton:="true"
              org.eclipse.userstorage.ui [1029]
                No resolution report for the bundle.  Bundle was not resolved because of a uses contraint violation.
  org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.userstorage.ui [osgi.identity; osgi.identity="org.eclipse.userstorage.ui"; type="osgi.bundle"; version:Version="1.0.1.v20170201-1648"; singleton:="true"] because it is exposed to package 'org.apache.http.auth' from resources org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.3.6.v201511171540"] and org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.5.2.v20170210-0925"] via two dependency chains.

Chain 1:
  org.eclipse.userstorage.ui [osgi.identity; osgi.identity="org.eclipse.userstorage.ui"; type="osgi.bundle"; version:Version="1.0.1.v20170201-1648"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.apache.httpcomponents.httpclient)(&(bundle-version>=4.0.0)(!(bundle-version>=4.4.0))))
     |
    provide: osgi.wiring.bundle: org.apache.httpcomponents.httpclient
  org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.3.6.v201511171540"]

Chain 2:
  org.eclipse.userstorage.ui [osgi.identity; osgi.identity="org.eclipse.userstorage.ui"; type="osgi.bundle"; version:Version="1.0.1.v20170201-1648"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.eclipse.userstorage)(&(bundle-version>=1.0.0)(!(bundle-version>=2.0.0))))
     |
    provide: osgi.wiring.bundle; bundle-version:Version="1.1.0.v20170328-0205"; osgi.wiring.bundle="org.eclipse.userstorage"; singleton:="true"
  org.eclipse.userstorage [osgi.identity; osgi.identity="org.eclipse.userstorage"; type="osgi.bundle"; version:Version="1.1.0.v20170328-0205"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.apache.httpcomponents.httpclient)(&(bundle-version>=4.3.0)(!(bundle-version>=5.0.0))))
     |
    provide: osgi.wiring.bundle: org.apache.httpcomponents.httpclient
  org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.5.2.v20170210-0925"]
at org.eclipse.osgi.container.Module.start(Module.java:444)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1628)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1607)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1579)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1522)
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)

!ENTRY org.eclipse.epp.mpc.core.win32 4 0 2017-05-29 13:55:43.679
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.epp.mpc.core.win32 [229]
  Unresolved requirement: Import-Package: org.eclipse.epp.internal.mpc.core.transport.httpclient; bundle-version="1.6.0"
    -> Export-Package: org.eclipse.epp.internal.mpc.core.transport.httpclient; bundle-symbolic-name="org.eclipse.epp.mpc.core"; bundle-version="1.6.0.v20170524-1922"; version="0.0.0"; x-friends:="org.eclipse.epp.mpc.core.win32"
       org.eclipse.epp.mpc.core [228]
         Unresolved requirement: Require-Bundle: org.eclipse.userstorage.oauth; bundle-version="[1.0.0,2.0.0)"
           -> Bundle-SymbolicName: org.eclipse.userstorage.oauth; bundle-version="1.0.0.v20170519-1728"; singleton:="true"
              org.eclipse.userstorage.oauth [1028]
                Unresolved requirement: Require-Bundle: org.eclipse.userstorage.ui; bundle-version="1.0.0"
                  -> Bundle-SymbolicName: org.eclipse.userstorage.ui; bundle-version="1.0.1.v20170201-1648"; singleton:="true"
                     org.eclipse.userstorage.ui [1029]
                       No resolution report for the bundle.  Bundle was not resolved because of a uses contraint violation.
  org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.userstorage.ui [osgi.identity; osgi.identity="org.eclipse.userstorage.ui"; type="osgi.bundle"; version:Version="1.0.1.v20170201-1648"; singleton:="true"] because it is exposed to package 'org.apache.http.auth' from resources org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.3.6.v201511171540"] and org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.5.2.v20170210-0925"] via two dependency chains.

Chain 1:
  org.eclipse.userstorage.ui [osgi.identity; osgi.identity="org.eclipse.userstorage.ui"; type="osgi.bundle"; version:Version="1.0.1.v20170201-1648"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.apache.httpcomponents.httpclient)(&(bundle-version>=4.0.0)(!(bundle-version>=4.4.0))))
     |
    provide: osgi.wiring.bundle: org.apache.httpcomponents.httpclient
  org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.3.6.v201511171540"]

Chain 2:
  org.eclipse.userstorage.ui [osgi.identity; osgi.identity="org.eclipse.userstorage.ui"; type="osgi.bundle"; version:Version="1.0.1.v20170201-1648"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.eclipse.userstorage)(&(bundle-version>=1.0.0)(!(bundle-version>=2.0.0))))
     |
    provide: osgi.wiring.bundle; bundle-version:Version="1.1.0.v20170328-0205"; osgi.wiring.bundle="org.eclipse.userstorage"; singleton:="true"
  org.eclipse.userstorage [osgi.identity; osgi.identity="org.eclipse.userstorage"; type="osgi.bundle"; version:Version="1.1.0.v20170328-0205"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.apache.httpcomponents.httpclient)(&(bundle-version>=4.3.0)(!(bundle-version>=5.0.0))))
     |
    provide: osgi.wiring.bundle: org.apache.httpcomponents.httpclient
  org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.5.2.v20170210-0925"]
at org.eclipse.osgi.container.Module.start(Module.java:444)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1628)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1607)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1579)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1522)
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)

!ENTRY org.eclipse.epp.mpc.ui 4 0 2017-05-29 13:55:43.695
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.epp.mpc.ui [231]
  Unresolved requirement: Require-Bundle: org.eclipse.userstorage.ui; bundle-version="[1.0.0,2.0.0)"
    -> Bundle-SymbolicName: org.eclipse.userstorage.ui; bundle-version="1.0.1.v20170201-1648"; singleton:="true"
       org.eclipse.userstorage.ui [1029]
         No resolution report for the bundle.  Unresolved requirement: Require-Bundle: org.eclipse.epp.mpc.core; bundle-version="1.6.0"
    -> Bundle-SymbolicName: org.eclipse.epp.mpc.core; bundle-version="1.6.0.v20170524-1922"; singleton:="true"
       org.eclipse.epp.mpc.core [228]
         Unresolved requirement: Require-Bundle: org.eclipse.userstorage.oauth; bundle-version="[1.0.0,2.0.0)"
           -> Bundle-SymbolicName: org.eclipse.userstorage.oauth; bundle-version="1.0.0.v20170519-1728"; singleton:="true"
              org.eclipse.userstorage.oauth [1028]
                Unresolved requirement: Require-Bundle: org.eclipse.userstorage.ui; bundle-version="1.0.0"
                  -> Bundle-SymbolicName: org.eclipse.userstorage.ui; bundle-version="1.0.1.v20170201-1648"; singleton:="true"
  Unresolved requirement: Require-Bundle: org.eclipse.userstorage.oauth; bundle-version="[1.0.0,2.0.0)"
    -> Bundle-SymbolicName: org.eclipse.userstorage.oauth; bundle-version="1.0.0.v20170519-1728"; 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.userstorage.ui [osgi.identity; osgi.identity="org.eclipse.userstorage.ui"; type="osgi.bundle"; version:Version="1.0.1.v20170201-1648"; singleton:="true"] because it is exposed to package 'org.apache.http.auth' from resources org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.3.6.v201511171540"] and org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.5.2.v20170210-0925"] via two dependency chains.

Chain 1:
  org.eclipse.userstorage.ui [osgi.identity; osgi.identity="org.eclipse.userstorage.ui"; type="osgi.bundle"; version:Version="1.0.1.v20170201-1648"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.apache.httpcomponents.httpclient)(&(bundle-version>=4.0.0)(!(bundle-version>=4.4.0))))
     |
    provide: osgi.wiring.bundle: org.apache.httpcomponents.httpclient
  org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.3.6.v201511171540"]

Chain 2:
  org.eclipse.userstorage.ui [osgi.identity; osgi.identity="org.eclipse.userstorage.ui"; type="osgi.bundle"; version:Version="1.0.1.v20170201-1648"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.eclipse.userstorage)(&(bundle-version>=1.0.0)(!(bundle-version>=2.0.0))))
     |
    provide: osgi.wiring.bundle; bundle-version:Version="1.1.0.v20170328-0205"; osgi.wiring.bundle="org.eclipse.userstorage"; singleton:="true"
  org.eclipse.userstorage [osgi.identity; osgi.identity="org.eclipse.userstorage"; type="osgi.bundle"; version:Version="1.1.0.v20170328-0205"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.apache.httpcomponents.httpclient)(&(bundle-version>=4.3.0)(!(bundle-version>=5.0.0))))
     |
    provide: osgi.wiring.bundle: org.apache.httpcomponents.httpclient
  org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.5.2.v20170210-0925"]
at org.eclipse.osgi.container.Module.start(Module.java:444)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1628)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1607)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1579)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1522)
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)

!ENTRY org.eclipse.userstorage.oauth 4 0 2017-05-29 13:55:46.020
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.userstorage.oauth [1028]
  Unresolved requirement: Require-Bundle: org.eclipse.userstorage.ui; bundle-version="1.0.0"
    -> Bundle-SymbolicName: org.eclipse.userstorage.ui; bundle-version="1.0.1.v20170201-1648"; singleton:="true"
       org.eclipse.userstorage.ui [1029]
         No resolution report for the bundle.  Bundle was not resolved because of a uses contraint violation.
  org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.userstorage.ui [osgi.identity; osgi.identity="org.eclipse.userstorage.ui"; type="osgi.bundle"; version:Version="1.0.1.v20170201-1648"; singleton:="true"] because it is exposed to package 'org.apache.http.auth' from resources org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.3.6.v201511171540"] and org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.5.2.v20170210-0925"] via two dependency chains.

Chain 1:
  org.eclipse.userstorage.ui [osgi.identity; osgi.identity="org.eclipse.userstorage.ui"; type="osgi.bundle"; version:Version="1.0.1.v20170201-1648"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.apache.httpcomponents.httpclient)(&(bundle-version>=4.0.0)(!(bundle-version>=4.4.0))))
     |
    provide: osgi.wiring.bundle: org.apache.httpcomponents.httpclient
  org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.3.6.v201511171540"]

Chain 2:
  org.eclipse.userstorage.ui [osgi.identity; osgi.identity="org.eclipse.userstorage.ui"; type="osgi.bundle"; version:Version="1.0.1.v20170201-1648"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.eclipse.userstorage)(&(bundle-version>=1.0.0)(!(bundle-version>=2.0.0))))
     |
    provide: osgi.wiring.bundle; bundle-version:Version="1.1.0.v20170328-0205"; osgi.wiring.bundle="org.eclipse.userstorage"; singleton:="true"
  org.eclipse.userstorage [osgi.identity; osgi.identity="org.eclipse.userstorage"; type="osgi.bundle"; version:Version="1.1.0.v20170328-0205"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.apache.httpcomponents.httpclient)(&(bundle-version>=4.3.0)(!(bundle-version>=5.0.0))))
     |
    provide: osgi.wiring.bundle: org.apache.httpcomponents.httpclient
  org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.5.2.v20170210-0925"]
at org.eclipse.osgi.container.Module.start(Module.java:444)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1628)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1607)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1579)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1522)
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)

!ENTRY org.eclipse.userstorage.ui 4 0 2017-05-29 13:55:46.036
!MESSAGE FrameworkEvent ERROR
!STACK 0
org.osgi.framework.BundleException: Could not resolve module: org.eclipse.userstorage.ui [1029]
  Bundle was not resolved because of a uses contraint violation.
  org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource org.eclipse.userstorage.ui [osgi.identity; osgi.identity="org.eclipse.userstorage.ui"; type="osgi.bundle"; version:Version="1.0.1.v20170201-1648"; singleton:="true"] because it is exposed to package 'org.apache.http.auth' from resources org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.3.6.v201511171540"] and org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.5.2.v20170210-0925"] via two dependency chains.

Chain 1:
  org.eclipse.userstorage.ui [osgi.identity; osgi.identity="org.eclipse.userstorage.ui"; type="osgi.bundle"; version:Version="1.0.1.v20170201-1648"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.apache.httpcomponents.httpclient)(&(bundle-version>=4.0.0)(!(bundle-version>=4.4.0))))
     |
    provide: osgi.wiring.bundle: org.apache.httpcomponents.httpclient
  org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.3.6.v201511171540"]

Chain 2:
  org.eclipse.userstorage.ui [osgi.identity; osgi.identity="org.eclipse.userstorage.ui"; type="osgi.bundle"; version:Version="1.0.1.v20170201-1648"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.eclipse.userstorage)(&(bundle-version>=1.0.0)(!(bundle-version>=2.0.0))))
     |
    provide: osgi.wiring.bundle; bundle-version:Version="1.1.0.v20170328-0205"; osgi.wiring.bundle="org.eclipse.userstorage"; singleton:="true"
  org.eclipse.userstorage [osgi.identity; osgi.identity="org.eclipse.userstorage"; type="osgi.bundle"; version:Version="1.1.0.v20170328-0205"; singleton:="true"]
    require: (&(osgi.wiring.bundle=org.apache.httpcomponents.httpclient)(&(bundle-version>=4.3.0)(!(bundle-version>=5.0.0))))
     |
    provide: osgi.wiring.bundle: org.apache.httpcomponents.httpclient
  org.apache.httpcomponents.httpclient [osgi.identity; osgi.identity="org.apache.httpcomponents.httpclient"; type="osgi.bundle"; version:Version="4.5.2.v20170210-0925"]
at org.eclipse.osgi.container.Module.start(Module.java:444)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1628)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1607)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1579)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1522)
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)


On 26 May 2017 at 19:38, Young-Soo Roh <ysroh@xxxxxxxxxxxxx> wrote:

I wiped out everything and tried again and it seem to work so far.

 

I will use the bundle pool next time J

 

Regards,

 

Young-Soo Roh

Sr. Software Developer

Zeligsoft (2009) Ltd.

 

From: papyrus-rt-dev-bounces@eclipse.org [mailto:papyrus-rt-dev-bounces@eclipse.org] On Behalf Of Christian Damus
Sent: Friday, May 26, 2017 1:25 PM


To: papyrus-rt developer discussions
Subject: Re: [papyrus-rt-dev] Developer Setup Updates for Oxygen

 

No, the git repository has nothing to do with it.

 

What’s this about being asked to install the dsml.validation feature?  I’ve never seen that.  It’s not optional; the Papyrus-RT setup model requires it, so nothing should be asking.  This could well be related to the problem:  the Neon and Oxygen versions of this feature would need incompatible versions of some of the main Papyrus bundles.

 

And, I do highly recommend using the bundle pools.  It’s safe, doesn’t cause problems like this, and is very friendly to your disk storage.


Cheers,

 

Christian


On May 26, 2017, 13:22 -0400, Young-Soo Roh <ysroh@xxxxxxxxxxxxx>, wrote:

Hi Christian,

 

Yes I did. The only thing is that I am reusing the same git repository used for Neon. I don’t think it matters??

Anyway, I am going to try again.

 

 

One thing unusual was that the start up execution asked about installing dsml.validation so I said yes.

 

I am going to try again..

 

Regards,

 

Young-Soo Roh

Sr. Software Developer

Zeligsoft (2009) Ltd.

 

From: papyrus-rt-dev-bounces@eclipse.org [mailto:papyrus-rt-dev-bounces@eclipse.org] On Behalf Of Christian Damus
Sent: Friday, May 26, 2017 1:17 PM
To: papyrus-rt developer discussions
Subject: Re: [papyrus-rt-dev] Developer Setup Updates for Oxygen

 

Hi, Young-Soo,

 

Did you make sure to select Oxygen for both the release of the EPP on which you based your installation (the first page of the installer) and also the ‘Target Platform’ variable?  And also the ‘master’/‘Oxygen’ stream of all of the setup projects that you import?


Cheers,

 

Christian


On May 26, 2017, 13:16 -0400, Young-Soo Roh <ysroh@xxxxxxxxxxxxx>, wrote:

Christian,

 

I am getting following error on start up task execution.

Any idea why??

 

 

Cannot complete the request.  Generating details.

ERROR: org.eclipse.equinox.p2.director code=10053 Cannot complete the install because one or more required items could not be found.

  at org.eclipse.oomph.util.OomphPlugin.coreException(OomphPlugin.java:280)

  at org.eclipse.oomph.p2.internal.core.ProfileTransactionImpl.resolve(ProfileTransactionImpl.java:425)

  at org.eclipse.oomph.p2.internal.core.ProfileTransactionImpl.commit(ProfileTransactionImpl.java:337)

  at org.eclipse.oomph.setup.p2.impl.P2TaskImpl.perform(P2TaskImpl.java:729)

  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.doPerformNeededSetupTasks(SetupTaskPerformer.java:3324)

  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.access$1(SetupTaskPerformer.java:3267)

  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil$1.run(SetupTaskPerformer.java:4488)

  at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)

  at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)

  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil.performNeededSetupTasks(SetupTaskPerformer.java:4482)

  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer$WorkspaceUtil.access$0(SetupTaskPerformer.java:4480)

  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performNeededSetupTasks(SetupTaskPerformer.java:3258)

  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.performTriggeredSetupTasks(SetupTaskPerformer.java:3233)

  at org.eclipse.oomph.setup.internal.core.SetupTaskPerformer.perform(SetupTaskPerformer.java:3133)

  at org.eclipse.oomph.setup.ui.wizards.ProgressPage$9.run(ProgressPage.java:567)

  at org.eclipse.oomph.setup.ui.wizards.ProgressPage$11$1.run(ProgressPage.java:693)

  at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)

  ERROR: org.eclipse.equinox.p2.director code=0 Software being installed: artificial_root 1.0.0.v1495818655645

  ERROR: org.eclipse.equinox.p2.director code=0 Missing requirement: Papyrus widgets 2.0.1.201705260146 (org.eclipse.papyrus.infra.widgets 2.0.1.201705260146) requires 'bundle org.eclipse.e4.ui.model.workbench [1.2.0,2.0.0)' but it could not be found

  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:

    ERROR: org.eclipse.equinox.p2.director code=0 From: artificial_root 1.0.0.v1495818655645

    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrus.extra.dsml.validation.feature.feature.group 0.0.0

  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:

    ERROR: org.eclipse.equinox.p2.director code=0 From: Customization Manager 1.2.0.201705260252 (org.eclipse.papyrus.customization 1.2.0.201705260252)

    ERROR: org.eclipse.equinox.p2.director code=0 To: bundle org.eclipse.papyrus.infra.properties.ui [1.2.0,2.0.0)

  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:

    ERROR: org.eclipse.equinox.p2.director code=0 From: Papyrus DSML Validation Feature (Incubation) 1.2.0.201705260252 (org.eclipse.papyrus.extra.dsml.validation.feature.feature.group 1.2.0.201705260252)

    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrus.customization [1.2.0.201705260252]

  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:

    ERROR: org.eclipse.equinox.p2.director code=0 From: Papyrus Properties Run-time 1.2.2.201705260146 (org.eclipse.papyrus.infra.properties.ui 1.2.2.201705260146)

    ERROR: org.eclipse.equinox.p2.director code=0 To: bundle org.eclipse.papyrus.infra.widgets [2.0.0,3.0.0)

 

 

Regards,

 

Young-Soo Roh

Sr. Software Developer

Zeligsoft (2009) Ltd.

 

From: papyrus-rt-dev-bounces@eclipse.org [mailto:papyrus-rt-dev-bounces@eclipse.org] On Behalf Of Ernesto Posse
Sent: Friday, May 26, 2017 12:36 PM
To: papyrus-rt developer discussions
Subject: Re: [papyrus-rt-dev] Developer Setup Updates for Oxygen

 

A fresh install works. I even included the Installer and Migration components and they seem to be Ok.  It's good to see a new splash screen too.

 

I've updated the wiki developer instructions. Although the screenshots still show Neon at various places, there are explicit notes instructing the user to select Oxygen instead.

 

 

On Fri, May 26, 2017 at 11:47 AM Ernesto Posse <eposse@xxxxxxxxxxxxx> wrote:

Sorry, I cut part of the error. It complains about conflicting bundles. The full error is

 

  ERROR: org.eclipse.equinox.p2.director code=0 Software being installed: artificial_root 1.0.0.v1495813449953

  ERROR: org.eclipse.equinox.p2.director code=1 Only one of the following can be installed at once: 

    ERROR: org.eclipse.equinox.p2.director code=0 Papyrus DSML Validation (Incubation) 1.2.0.201705100759 (org.eclipse.papyrus.dsml.validation 1.2.0.201705100759)

    ERROR: org.eclipse.equinox.p2.director code=0 Papyrus DSML Validation (Incubation) 1.2.0.201705170313 (org.eclipse.papyrus.dsml.validation 1.2.0.201705170313)

  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:

    ERROR: org.eclipse.equinox.p2.director code=0 From: artificial_root 1.0.0.v1495813449953

    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrus.dsml.validation.feature.feature.group 0.0.0

  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:

    ERROR: org.eclipse.equinox.p2.director code=0 From: artificial_root 1.0.0.v1495813449953

    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrus.extra.dsml.validation.feature.feature.group 0.0.0

  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:

    ERROR: org.eclipse.equinox.p2.director code=0 From: Papyrus DSML Validation Feature (Incubation) 1.2.0.201705100759 (org.eclipse.papyrus.dsml.validation.feature.feature.group 1.2.0.201705100759)

    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrus.dsml.validation [1.2.0.201705100759]

  ERROR: org.eclipse.equinox.p2.director code=1 Cannot satisfy dependency:

    ERROR: org.eclipse.equinox.p2.director code=0 From: Papyrus DSML Validation Feature (Incubation) 1.2.0.201705170313 (org.eclipse.papyrus.extra.dsml.validation.feature.feature.group 1.2.0.201705170313)

    ERROR: org.eclipse.equinox.p2.director code=0 To: org.eclipse.papyrus.dsml.validation [1.2.0.201705170313]

 

 

Anyway, I'll try to do a fresh install to see if it works for me.

 

 

 

 

On Fri, May 26, 2017 at 11:42 AM Christian Damus <give.a.damus@xxxxxxxxx> wrote:

I don't know what that means.  Is the org.eclipse.papyrus.dsml.validation feature an error?

 

This feature is renamed since Neon.  Perhaps Papyrus doesn’t provide the p2.inf instructions that tell p2 how to update from org.eclipse.papyrus.extra.dsml.validation to org.eclipse.papyrus.dsml.validation?  I don't know.

 

Cheers,


Christian


On May 26, 2017, 11:37 -0400, Ernesto Posse <eposse@xxxxxxxxxxxxx>, wrote:

I just tried it on my existing Neon install, to see what happened, and I can't even get error dialogs. It fails in the P2 Director task with

 

    ERROR: org.eclipse.equinox.p2.director code=0 Papyrus DSML Validation (Incubation) 1.2.0.201705100759 (org.eclipse.papyrus.dsml.validation 1.2.0.201705100759)

    ERROR: org.eclipse.equinox.p2.director code=0 Papyrus DSML Validation (Incubation) 1.2.0.201705170313 (org.eclipse.papyrus.dsml.validation 1.2.0.201705170313)

 

Is this expected then?

 

 

On Fri, May 26, 2017 at 11:32 AM Christian Damus <give.a.damus@xxxxxxxxx> wrote:

Hi, Young-Soo,

 

You don’t actually have to re-install until it’s convenient to do so.  In the mean-time, whenever you run an update, you can just uncheck the p2 task.

 

But, yes, a Neon workbench cannot be updated to Oxygen because you will end up with a constant barrage of error dialogs caused by classpath errors (wiring problems) in JDT UI.  It would have to be installed from scratch.  But, at least, an existing workspace seems to be safely upgradeable.


Cheers,

 

Christian


On May 26, 2017, 11:26 -0400, Young-Soo Roh <ysroh@xxxxxxxxxxxxx>, wrote:

Thanks Christian,

 

I will have to re-install my dev env then.

 

Regards,

 

Young-Soo Roh

Sr. Software Developer

Zeligsoft (2009) Ltd.

 

From: papyrus-rt-dev-bounces@eclipse.org [mailto:papyrus-rt-dev-bounces@eclipse.org] On Behalf Of Christian Damus
Sent: Friday, May 26, 2017 11:07 AM
To: papyrus-rt developer discussions
Subject: [papyrus-rt-dev] Developer Setup Updates for Oxygen

 

Hi, Team,

 

Since Oxygen M7 seems to resolve the Apache bundle wiring problems in the Eclipse/Oomph/MPC/etc. substrate, the developer setup model now is updated to install Papyrus and Papyrus-RT Oxygen in the development environment instead of Neon.  This should help at least with editing models and avoid PDE’s complaints about forward targeting.


Cheers,

 

Christian

 

Virus-free. www.avg.com

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev

--

Ernesto Posse

Zeligsoft

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev

--

Ernesto Posse

Zeligsoft

--

Ernesto Posse

Zeligsoft

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev

_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev


_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev



_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev

Back to the top