You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Hendy Irawan (JIRA)" <ji...@apache.org> on 2013/03/16 08:50:12 UTC
[jira] [Created] (FELIX-3972) Generated Bundles MANIFEST.MF contain
invalid Import-Package: org.osgi.service.blueprint;version="[1.0.0,2.0.0)"
Hendy Irawan created FELIX-3972:
-----------------------------------
Summary: Generated Bundles MANIFEST.MF contain invalid Import-Package: org.osgi.service.blueprint;version="[1.0.0,2.0.0)"
Key: FELIX-3972
URL: https://issues.apache.org/jira/browse/FELIX-3972
Project: Felix
Issue Type: Bug
Components: Maven Bundle Plugin
Affects Versions: maven-bundle-plugin-2.3.7
Environment: Eclipse Virgo Nano Web 3.6.1, Eclipse Virgo Jetty 3.6.1
Reporter: Hendy Irawan
The Import-Package is incorrect because org.osgi.service.blueprint has no code and is not importable (see http://mail-archives.apache.org/mod_mbox/aries-dev/201106.mbox/%3CBANLkTine2R1b9JD_xPcnzC_WNYZF0jXEhg@mail.gmail.com%3E ). In practice it is incompatible with Eclipse Virgo.
{code}
[2013-03-16 14:41:05.458] fs-watcher <HD0001I> Hot deployer processing 'CREATED' event for file 'dep-0.0.1-SNAPSHOT.jar'.
[2013-03-16 14:41:05.460] fs-watcher <DE0001I> Installing from '/home/rudi/virgo-nano-full-3.6.1.RELEASE/pickup/dep-0.0.1-SNAPSHOT.jar'.
[2013-03-16 14:41:05.481] fs-watcher <DE0002I> Installed bundle 'com.hendyirawan.blueprintdep.dep' version '0.0.1.SNAPSHOT'.
[2013-03-16 14:41:05.481] fs-watcher <DE0003I> Starting bundle 'com.hendyirawan.blueprintdep.dep' version '0.0.1.SNAPSHOT'.
[2013-03-16 14:41:05.523] fs-watcher <DE0012E> Failed to start bundle 'com.hendyirawan.blueprintdep.dep' version '0.0.1.SNAPSHOT'. See the logs for more information. org.osgi.framework.BundleException: The bundle "com.hendyirawan.blueprintdep.dep_0.0.1.SNAPSHOT [175]" could not be resolved. Reason: Missing Constraint: Import-Package: org.osgi.service.blueprint; version="[1.0.0,2.0.0)"
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolverError(AbstractBundle.java:1332)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.getResolutionFailureException(AbstractBundle.java:1316)
at org.eclipse.osgi.framework.internal.core.BundleHost.startWorker(BundleHost.java:323)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:300)
at org.eclipse.osgi.framework.internal.core.AbstractBundle.start(AbstractBundle.java:292)
at org.eclipse.virgo.nano.deployer.internal.BundleDeployer.deploy(BundleDeployer.java:284)
at org.eclipse.virgo.nano.deployer.internal.StandardApplicationDeployer.deploy(StandardApplicationDeployer.java:100)
at org.eclipse.virgo.nano.deployer.internal.StandardApplicationDeployer.deploy(StandardApplicationDeployer.java:191)
at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.deploy(HotDeployerFileSystemListener.java:225)
at org.eclipse.virgo.nano.deployer.hot.HotDeploymentFileSystemListener.onChange(HotDeployerFileSystemListener.java:79)
at org.eclipse.virgo.util.io.FileSystemChecker.notifyListeners(FileSystemChecker.java:373)
at org.eclipse.virgo.util.io.FileSystemChecker.check(FileSystemChecker.java:282)
at org.eclipse.virgo.nano.deployer.hot.WatchTask.run(WatchTask.java:48)
at java.lang.Thread.run(Thread.java:722)
{code}
It can be replaced with Import-Package: org.osgi.service.blueprint.container which Virgo does export.
Virgo exported packages are: (as of 3.6.1)
{code}
org.osgi.service.blueprint.reflect; version="1.0.1"<osgi.enterprise_4.2.0.v201108120515 [172]>
org.osgi.service.blueprint.container; version="1.0.1"<osgi.enterprise_4.2.0.v201108120515 [172]>
{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