Mailing-List: contact dev-help@brooklyn.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@brooklyn.apache.org
From: aledsage <git@git.apache.org>
To: dev@brooklyn.apache.org
Reply-To: dev@brooklyn.apache.org
Message-ID: <git-pr-305-brooklyn-server@git.apache.org>
Subject: [GitHub] brooklyn-server pull request #305: BROOKLYN-338: BrooklynApi fixes for karaf
Content-Type: text/plain
Date: Tue, 23 Aug 2016 22:36:23 +0000 (UTC)
archived-at: Tue, 23 Aug 2016 22:36:26 -0000

GitHub user aledsage opened a pull request:

    https://github.com/apache/brooklyn-server/pull/305

    BROOKLYN-338: BrooklynApi fixes for karaf

    These aren’t enough to fix BROOKLYN-338, but it’s a start:
    * Ensures rest-client imports the resteasy marshallers package,
      which it calls with reflection (via the resteasy ProxyBuilder).
    * Passes the ProxyBuilder a classloader that has access to the 
      rest-api classes and to rest-client’s classloader (which thus 
      can access the marshallers).

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

    $ git pull https://github.com/aledsage/brooklyn-server BROOKLYN-338

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

    https://github.com/apache/brooklyn-server/pull/305.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 #305
    
----
commit f270f09e345252e065fdc03ce70b02a2beb4de87
Author: Aled Sage <aled.sage@gmail.com>
Date:   2016-08-23T22:35:47Z

    BROOKLYN-338: BrooklynApi fixes for karaf
    
    These aren’t enough to fix BROOKLYN-338, but it’s a start:
    * Ensures rest-client imports the resteasy marshallers package,
      which it calls with reflection (via the resteasy ProxyBuilder).
    * Passes the ProxyBuilder a classloader that has access to the 
      rest-api classes and to rest-client’s classloader (which thus 
      can access the marshallers).

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---