Unresolved constraint in bundle org.ops4j.pax.web.pax-web-spi
-------------------------------------------------------------
Key: PAXWEB-170
URL: http://issues.ops4j.org/browse/PAXWEB-170
Project: Pax Web
Issue Type: Bug
Affects Versions: 0.7.0
Reporter: Alin Dreghiciu
Assignee: Alin Dreghiciu
Fix For: 0.8.0
Originally part of PAXWEB-169:
To explain the issues I was seeing; First off I was getting an unresolved
constraint problem deploying the spi bundle. It looks for the internal package
'org.ops4j.pax.web.service.spi.internal'
{code}
org.osgi.framework.BundleException: Unresolved constraint in bundle
org.ops4j.pax.web.pax-web-spi [78]: package;
(&(package=org.ops4j.pax.web.service.spi.internal)(version>=0.7.0))
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3268)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1596)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:890)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:877)
at org.apache.felix.karaf.shell.osgi.StartBundle.doExecute(StartBundle.java:29)
at
org.apache.felix.karaf.shell.osgi.BundlesCommand.doExecute(BundlesCommand.java:49)
at
org.apache.felix.karaf.shell.console.OsgiCommandSupport.execute(OsgiCommandSupport.java:41)
at
org.apache.felix.gogo.commands.basic.AbstractCommand.execute(AbstractCommand.java:34)
at
org.apache.felix.gogo.runtime.shell.CommandProxy.execute(CommandProxy.java:45)
at org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:211)
at
org.apache.felix.gogo.runtime.shell.Closure.executeStatement(Closure.java:146)
at org.apache.felix.gogo.runtime.shell.Pipe.run(Pipe.java:91)
at org.apache.felix.gogo.runtime.shell.Closure.execute(Closure.java:75)
at
org.apache.felix.gogo.runtime.shell.CommandSessionImpl.execute(CommandSessionImpl.java:71)
at org.apache.felix.karaf.shell.console.jline.Console.run(Console.java:115)
at java.lang.Thread.run(Thread.java:619)
{code}
>From what I can tell this is being caused by the inclusion of the Activator
>clause in the bnd file, which doesn't seem to exist.
Bundle-Activator:\
${bundle.namespace}.internal.Activator
I removed this statement and rebuilt and it then deployed fine. I guess this
activator got ditched at some stage.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
