felix-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Nodet <gno...@apache.org>
Subject Re: [resolver] fragments use case
Date Thu, 21 Jul 2016 13:52:43 GMT
I think that's wrong.
Fragments are available from the output wiring map and the only wire they
have is a requirement to their host bundle.

2016-07-21 15:16 GMT+02:00 Raymond Auge <raymond.auge@liferay.com>:

> 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: gnodet@redhat.com
Web: http://fusesource.com
Blog: http://gnodet.blogspot.com/

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message