See
https://github.com/apache/felix/blob/trunk/resolver/src/test/java/org/apache/felix/resolver/test/ResolverTest.java#L303-L369
for
a unit test using fragments.

2016-07-21 15:16 GMT+02:00 Raymond Auge <[email protected]>:

> Hey everyone,
>
> I've observed in bndtools that if a fragment contributes a capability to
> it's host, the resolve result will contain the host but not the fragment
> causing runtime resolution to fail.
>
> This is perfectly acceptable during runtime, but not during deploy time
> where I need to identify all the required artifacts.
>
> I've filled an issue on bnd here:
> https://github.com/bndtools/bnd/issues/1559
>
> But I'm suspecting that the resolver has at least something to do with it.
> I'm not claiming this is a bug but a limitation of the resolver API.
>
> Would there be a way to ask the resolver to include the fragments that were
> used to produce the result?
>
> Thoughts?
> --
> *Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
>  (@rotty3000)
> Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
>  (@Liferay)
> Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org>
> (@OSGiAlliance)
>



-- 
------------------------
Guillaume Nodet
------------------------
Red Hat, Open Source Integration

Email: [email protected]
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/

Reply via email to