You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "John Ross (JIRA)" <ji...@apache.org> on 2016/02/04 18:23:39 UTC
[jira] [Resolved] (ARIES-1452) Subsystem throws exception when
bundle imports osgi framework
[ https://issues.apache.org/jira/browse/ARIES-1452?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Ross resolved ARIES-1452.
------------------------------
Resolution: Cannot Reproduce
Assignee: John Ross
I attached a ZIP containing a complete runtime intended to reproduce the described environment. I am able to successfully install and start the attached ESA. I'm going to need help reproducing this. Please update either the attached runtime or test class.
felix-framework-5.4.0]$ java -jar bin/felix.jar
[FelixStartLevel] INFO org.apache.sling.commons.threads.impl.DefaultThreadPoolManager - Started Apache Sling Thread Pool Manager
[FelixStartLevel] INFO org.apache.sling.settings.impl.SlingSettingsServiceImpl - Read Sling ID null from file ./felix-cache/bundle24/data/sling.id.file
[FelixStartLevel] INFO org.apache.sling.settings.impl.SlingSettingsServiceImpl - Created new Sling ID 3a44050b-7bb5-41dc-941e-3cd682f745d0
[FelixStartLevel] INFO org.apache.sling.settings.impl.SlingSettingsServiceImpl - No run modes active
____________________________
Welcome to Apache Felix Gogo
g! subsystem:install file:/home/jwross/.m2/repository/idoneus/mdm-parser-subsystem/1.0.0-SNAPSHOT/mdm-parser-subsystem-1.0.0-SNAPSHOT.esa
Installing subsystem: file:/home/jwross/.m2/repository/idoneus/mdm-parser-subsystem/1.0.0-SNAPSHOT/mdm-parser-subsystem-1.0.0-SNAPSHOT.esa
Subsystem successfully installed: mdm-parser-subsystem; id: 1
g! subsystem:start 1
g! subsystem:list
0 ACTIVE org.osgi.service.subsystem.root 1.0.0
1 ACTIVE mdm-parser-subsystem 1.0.0.SNAPSHOT
g!
> Subsystem throws exception when bundle imports osgi framework
> -------------------------------------------------------------
>
> Key: ARIES-1452
> URL: https://issues.apache.org/jira/browse/ARIES-1452
> Project: Aries
> Issue Type: Bug
> Components: Subsystem
> Affects Versions: subsystem-2.0.6, subsystem-2.0.8
> Environment: Mac OS X
> Apache Felix (inside Apache Sling 9-SNAPSHOT)
> Reporter: Roy Teeuwen
> Assignee: John Ross
> Attachments: Aries1452Test.java, felix-framework-5.4.0.zip, testcase.zip
>
>
> When building an OSGi subsystem feature, I created two bundles, an api and a core. The core has following embedded dependency:
> <dependency>
> <groupId>com.squeakysand.osgi</groupId>
> <artifactId>squeakysand-osgi</artifactId>
> <version>0.4.0</version>
> </dependency>
> Using previous dependency in the core, it creates the Import-Package org.osgi.framework;version="[1.5,2)” when using maven-bundle-plugin version 3.0.1.
> Starting up this subsystem through the webconsole subsystem plugin of Apache Felix, following error is thrown:
> 13.11.2015 22:01:23.849 *ERROR* [Thread-95] org.apache.sling.extensions.threaddump.internal.Activator Uncaught exception in Thread Thread[Thread-95,5,main]
> org.osgi.service.subsystem.SubsystemException: org.osgi.service.resolver.ResolutionException: Uses constraint violation. Unable to resolve resource idoneus.mdm-parser-core [/var/folders/h1/k9tr352j615f8jrrzh5yr5b80000gn/T/inputStreamExtract734624941409606295.zip/mdm-parser-core-1.0.0-SNAPSHOT.jar] because it is exposed to package 'org.osgi.framework' from resources org.apache.felix.framework [org.apache.felix.framework [0](R 0)] and org.apache.felix.framework [org.apache.felix.framework [0](R 0)] via two dependency chains.
> Chain 1:
> idoneus.mdm-parser-core [/var/folders/h1/k9tr352j615f8jrrzh5yr5b80000gn/T/inputStreamExtract734624941409606295.zip/mdm-parser-core-1.0.0-SNAPSHOT.jar]
> import: (&(osgi.wiring.package=org.osgi.framework)(&(version>=1.5.0)(!(version>=2.0.0))))
> |
> export: osgi.wiring.package: org.osgi.framework
> org.apache.felix.framework [org.apache.felix.framework [0](R 0)]
> Chain 2:
> idoneus.mdm-parser-core [/var/folders/h1/k9tr352j615f8jrrzh5yr5b80000gn/T/inputStreamExtract734624941409606295.zip/mdm-parser-core-1.0.0-SNAPSHOT.jar]
> import: (&(osgi.wiring.package=org.apache.sling.event.jobs.consumer)(&(version>=1.2.0)(!(version>=2.0.0))))
> |
> export: osgi.wiring.package=org.apache.sling.event.jobs.consumer; uses:=org.osgi.service.event
> org.apache.sling.event [org.apache.sling.event [103](R 103.0)]
> import: (&(osgi.wiring.package=org.osgi.service.event)(version>=1.2.0)(!(version>=2.0.0)))
> |
> export: osgi.wiring.package=org.osgi.service.event; uses:=org.osgi.framework
> org.apache.felix.eventadmin [org.apache.felix.eventadmin [9](R 9.0)]
> import: (&(osgi.wiring.package=org.osgi.framework)(version>=1.3.0)(!(version>=2.0.0)))
> |
> export: osgi.wiring.package: org.osgi.framework
> org.apache.felix.framework [org.apache.felix.framework [0](R 0)]
> at org.apache.aries.subsystem.core.internal.SubsystemResource.computeDependencies(SubsystemResource.java:395)
> This does not happen when I install the api and core as seperate bundles in the OSGi container
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)