Import-Package error for already-deployed dependency [message #1626115] |
Fri, 20 February 2015 15:53  |
Eclipse User |
|
|
|
Hi all,
I'm trying to deploy a package to Virgo with a dependency on org.glassfish.jersey.core.jersey-common_2.14.0, which itself depends on javax.annotation. I'm getting the following message in the log when I do so:
An Import-Package could not be resolved. Resolver error data <Import-Package: javax.annotation; version="[1.2.0,2.0.0)">. Caused by missing constraint in bundle <org.glassfish.jersey.core.jersey-common_2.14.0>
constraint: <Import-Package: javax.annotation; version="[1.2.0,2.0.0)">
The thing is, I am already deploying javax.annotation-api prior to this bundle being loaded. Some lines above the error in the log, I see two versions of javax-annotation being loaded:
Bundle javax.annotation_1.1.0.v201108011116, BundleEvent STARTED
Bundle javax.annotation-api_1.2.0, BundleEvent STARTED
The second bundle is a jar which I'm deploying with my package. Looking at the MANIFEST.MF for javax.annotation-api-1.2.jar, I see that it exports the exact package that is "missing" according to the error message:
Export-Package: javax.annotation;version="1.2",javax.annotation.security;version="1.2",javax.annotation.sql;version="1.2"
Has anyone encountered anything like this?
|
|
|
|
|
|
|
Re: Import-Package error for already-deployed dependency [message #1632995 is a reply to message #1632391] |
Tue, 24 February 2015 11:09  |
Eclipse User |
|
|
|
Thanks for the link about importing exported packages. Additionally, I just tried loading the jars one by one on a fresh install of both Virgo Nano and Virgo Tomcat 3.6.3, and jersey-common loaded without errors.
Unfortunately, the Virgo I need to run this on cannot be replaced or reinstalled as it is part of a packaged product. Is there any configuration specific to the Virgo server that could be causing this, since we're not seeing the same scenario on a fresh install?
|
|
|
Powered by
FUDForum. Page generated in 0.03589 seconds