[
https://issues.jboss.org/browse/JBOSGI-645?page=com.atlassian.jira.plugin...
]
Hannu Lahtinen commented on JBOSGI-645:
---------------------------------------
Hi [~arcivanov], I'm sorry, I made an incorrect assumption. As I said I'm
migrating a legacy system, but I'm still new to OSGi and had my reasons wrong. Newer
versions of the spring bundles without version="0" in MANIFEST resolved fine and
this led me to believe version="0" was the problem. The actual reason was that
the old stack had some system modules brought in as separate bundles with start levels and
I was incorrectly replacing those with system modules with start levels. After I removed
the start levels the bundles started resolving those dependencies just fine.
I discovered this trying to reproduce the problem for you with a clean configuration so in
a sense you solved my problem for me anyway. Thanks for the quick reply.
Cannot resolve Import-Package: org.acme.foo;version="0"
-------------------------------------------------------
Key: JBOSGI-645
URL:
https://issues.jboss.org/browse/JBOSGI-645
Project: JBoss OSGi
Issue Type: Bug
Components: framework
Reporter: Thomas Diesler
Assignee: Thomas Diesler
Fix For: JBossOSGi 2.0.0
Cannot resolve
{code}
// Bundle-SymbolicName: packageexportnoversion
// Export-Package: org.acme.foo
// Bundle-SymbolicName: packageimportversionzero
// Import-Package: org.acme.foo;version="0"
{code}
gives
{code}
Unable to resolve AbstractBundleRevision[packageimportversionzero:0.0.0]: missing
requirement
XPackageRequirement[dirs={filter=(&(osgi.wiring.package=org.acme.foo)(version>=0.0.0))},[packageimportversionzero:0.0.0]]
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)