[
https://issues.apache.org/jira/browse/BROOKLYN-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14999140#comment-14999140
]
ASF GitHub Bot commented on BROOKLYN-183:
-----------------------------------------
GitHub user CMoH opened a pull request:
https://github.com/apache/incubator-brooklyn/pull/1019
[BROOKLYN-183] Fix karaf package wiring for brooklyn-core
For some reason the `brooklyn-core` bundle still imports
`org.apache.felix.framework`, even if the actual code was moved to
`brooklyn-rt-felix` and excluded from `brooklyn-core`'s imports.
This PR addresses this issue.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/CMoH/incubator-brooklyn karaf-container-fix
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-brooklyn/pull/1019.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #1019
----
commit f0cadbabcef00aad8b3663d14685fea5591097a3
Author: Ciprian Ciubotariu <[email protected]>
Date: 2015-11-06T10:42:03Z
[BROOKLYN-183] Ignore bundle import of apache felix
----
> Create a Karaf runtime for Brooklyn
> -----------------------------------
>
> Key: BROOKLYN-183
> URL: https://issues.apache.org/jira/browse/BROOKLYN-183
> Project: Brooklyn
> Issue Type: Improvement
> Affects Versions: 0.8.0
> Reporter: Hadrian Zbarcea
> Fix For: 0.9.0
>
>
> Apache Karaf defines a lot of features out of the box, from security to
> logging that Brooklyn should use. Using an OSGi container (as opposed to the
> bare framework) allows us to better modularize Brooklyn focus on OSGi
> services and delegate commodity concerns to the container.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
