Bundle installation question

["John D. Ament" <jo...@gmail.com>]

Hi all

So I'm reading through docs and examples and archetypes, trying to come up
with some usable integrations.

I'm trying to do both JAX-WS and JAX-RS as my endpoints.  I can get some of
the archetypes to work, but as soon as I start mucking with things the
whole system gets confused.

I see errors like this:

org.osgi.framework.BundleException: Unresolved constraint in bundle esb-ws
[205]: Unable to resolve 205.0: missing requirement [205.0] package;
(&(package=org.springframework.
beans.factory.config)(version>=3.1.0)(!(version>=4.0.0)))

When trying to install my module via osgi:install (-s file:path/to/the/file)

The one thing that looks ominous is that it's referencing spring 3.1, even
though my application doesn't specify a version.  When I looked at the
manifest.mf file (just dawned on me, literally) I noticed that it was
referencing Spring 3.1.  I'm using the standard maven plugin, is it going
to look for versions?

John

Re: Bundle installation question

[Freeman Fang <fr...@gmail.com>]

Hi,

Yes, maven-bundle-plugin will check dependency version from your pom.xml and add it into the Import-Package.
－－－－－－－－－－－－－
Freeman(Yue) Fang

Red Hat, Inc. 
FuseSource is now part of Red Hat
Web: http://fusesource.com | http://www.redhat.com/
Twitter: freemanfang
Blog: http://freemanfang.blogspot.com
http://blog.sina.com.cn/u/1473905042
weibo: @Freeman小屋



On 2013-6-28, at 上午3:13, John D. Ament wrote:

> Hi all
> 
> So I'm reading through docs and examples and archetypes, trying to come up
> with some usable integrations.
> 
> I'm trying to do both JAX-WS and JAX-RS as my endpoints.  I can get some of
> the archetypes to work, but as soon as I start mucking with things the
> whole system gets confused.
> 
> I see errors like this:
> 
> org.osgi.framework.BundleException: Unresolved constraint in bundle esb-ws
> [205]: Unable to resolve 205.0: missing requirement [205.0] package;
> (&(package=org.springframework.
> beans.factory.config)(version>=3.1.0)(!(version>=4.0.0)))
> 
> When trying to install my module via osgi:install (-s file:path/to/the/file)
> 
> The one thing that looks ominous is that it's referencing spring 3.1, even
> though my application doesn't specify a version.  When I looked at the
> manifest.mf file (just dawned on me, literally) I noticed that it was
> referencing Spring 3.1.  I'm using the standard maven plugin, is it going
> to look for versions?
> 
> John