brooklyn-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From andreaturli <>
Subject [GitHub] incubator-brooklyn pull request: Improvements to brooklyn-server/r...
Date Thu, 28 Jan 2016 10:13:17 GMT
GitHub user andreaturli opened a pull request:

    Improvements to brooklyn-server/rest/rest-api

    - remove duplication of jackson and jackson2 on brooklyn project
    - refactor pojos to have a consistent `toString`, `hashCode` and `equals`
    - refactor pojos to use jackson2 
    - adapt code to the new jackson2 api where needed
    @ahgittin I'd appreciate your thoughts particularly on `BrooklynJacksonJsonProvider` as
jackson api are significantly changed in that area.
    Notice this is not ready to be merged as even if `brooklyn-server/rest` sub-modules are
building fine, but karaf section need to be fixed. I'd appreciate any help from karaf experts.

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

    $ git pull improvement/rest-api

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

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #1177
commit 73260ed0e56fe75f8fe859d4571ebd4f0abf5159
Author: Andrea Turli <>
Date:   2016-01-22T17:08:13Z

    Initial work to simplify the rest server
    - remove JsonNode from API interfaces
    - refactor consistently toStringand hashCode and equals for the domain objects
    - remove deprecated code
    - simplified pom dependencies

commit 151ec2f9e5efcddc1bec65d9f1c1fbfe641c3118
Author: Andrea Turli <>
Date:   2016-01-26T12:00:11Z

    remove com.codehaus.jackson dependency and promote com.fasterxml.jackson usage

commit 93d753553925d60ba9c4264c3aab635036720cc1
Author: Andrea Turli <>
Date:   2016-01-27T11:46:41Z

    More fixes to support jackson 2
    - adjust BrooklynJacksonSerializer to use jackson 2 api
    - fix web.xml for rest-api and rest-client


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 or file a JIRA ticket
with INFRA.

View raw message