You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "Jean-Philippe CLEMENT (JIRA)" <ji...@apache.org> on 2016/03/10 12:34:40 UTC
[jira] [Comment Edited] (ARIES-1502) Blueprint files are not
handled in fragments
[ https://issues.apache.org/jira/browse/ARIES-1502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15189168#comment-15189168 ]
Jean-Philippe CLEMENT edited comment on ARIES-1502 at 3/10/16 11:34 AM:
------------------------------------------------------------------------
Ok so that's an intended behavior - no issue then. Thank you :)
PS: Please close this issue
was (Author: jeanphi):
Ok so that's an intended behavior - no issue then. Thank you :)
> Blueprint files are not handled in fragments
> --------------------------------------------
>
> Key: ARIES-1502
> URL: https://issues.apache.org/jira/browse/ARIES-1502
> Project: Aries
> Issue Type: Bug
> Components: Blueprint
> Affects Versions: blueprint-core-1.5.0
> Reporter: Jean-Philippe CLEMENT
>
> This issue description changed due to investigations and the evolution of my comprehension.
> I made two bundles, a host and a fragment attached to the host.
> The host defines the Bundle-Blueprint manifest header specifying for instance a single file called bp.xml.
> The fragment defines several files in the default OSGI-INF/blueprint folder, none named bp.xml.
> The fragment Blueprint files are not handled. Only a bp.xml would. As the fragment Bundle-Blueprint header is not taken into account (as per spec 121.3.4), is it normal not to handle fragment Blueprint files stored in the default OSGI-INF/blueprint folder?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)