[ 
https://issues.apache.org/jira/browse/BROOKLYN-183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15103129#comment-15103129
 ] 

ASF GitHub Bot commented on BROOKLYN-183:
-----------------------------------------

GitHub user kcris opened a pull request:

    https://github.com/apache/incubator-brooklyn/pull/1152

    [BROOKLYN-183] Add karaf features

    Add brooklyn-software-base, brooklyn-software-winrm and brooklyn-policy 
features.
    Ignore for now python imports in brooklyn-software-base.

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/kcris/incubator-brooklyn osgi-software

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-brooklyn/pull/1152.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 #1152
    
----
commit c022c6ef5450ed790632076711bafd365ff974d2
Author: Cristian Tarsoaga <[email protected]>
Date:   2016-01-16T01:26:52Z

    [BROOKLYN-183] Add karaf features
    
    Add brooklyn-software-base, brooklyn-software-winrm and brooklyn-policy 
features.
    Ignore for now python imports in brooklyn-software-base.

----


> 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
>            Assignee: Ciprian Ciubotariu
>             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)

Reply via email to