You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by "John Ross (JIRA)" <ji...@apache.org> on 2013/07/01 20:44:41 UTC
[jira] [Resolved] (ARIES-868) Subsystem support for woven package
dependencies
[ https://issues.apache.org/jira/browse/ARIES-868?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
John Ross resolved ARIES-868.
-----------------------------
Resolution: Fixed
This was implemented in version 1.0. It will be replaced at some point by the standard way defined in RFC 201. See ARIES 1087.
> Subsystem support for woven package dependencies
> ------------------------------------------------
>
> Key: ARIES-868
> URL: https://issues.apache.org/jira/browse/ARIES-868
> Project: Aries
> Issue Type: Improvement
> Components: Subsystem
> Reporter: Mark Nuttall
> Assignee: Mark Nuttall
>
> We need a mechanism to support woven package dependencies within subsystems. For example, when running on Equinox 3.7+ the proxy code weaves a dependency on org.apache.aries.proxy.weaving.WovenProxy into application code. This prevents blueprint-managed subsystems from starting unless a bundle explicitly imports the org.apache.aries.proxy.weaving package, which should not be necessary. JPA is worse, in that multiple, and "harder to know" package dependencies are woven in.
> Investigate mechanisms for informing the SubsystemResolverHook about woven packages so that they can be permitted to resolve against the parent subsystem.
> Develop one or more itests: for example, one that shows blueprint working in a subsystem on Equinox 3.8 without explicitly stating woven package dependencies.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira