You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by gzurowski <gi...@git.apache.org> on 2014/03/17 19:17:58 UTC

[GitHub] camel pull request: CAMEL-7285: Upgrade camel-jcr to Jackrabbit 2....

GitHub user gzurowski opened a pull request:

    https://github.com/apache/camel/pull/113

    CAMEL-7285: Upgrade camel-jcr to Jackrabbit 2.6.5

    Rewrite JUnit tests to support change of default SecurityManager and
    AccessManager in Jackrabbit 2.6.
    
    Signed-off-by: Gregor Zurowski <gr...@zurowski.org>

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

    $ git pull https://github.com/gzurowski/camel Jackrabbit265

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

    https://github.com/apache/camel/pull/113.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 #113
    
----
commit b436c0f7ed650d2d8ba1ea7fa7fcb39dea2e3f00
Author: Gregor Zurowski <gr...@zurowski.org>
Date:   2014-03-16T21:46:55Z

    CAMEL-7285: Upgrade camel-jcr to Jackrabbit 2.6.5
    
    Rewrite JUnit tests to support change of default SecurityManager and
    AccessManager in Jackrabbit 2.6.
    
    Signed-off-by: Gregor Zurowski <gr...@zurowski.org>

----


---
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.
---

[GitHub] camel pull request: CAMEL-7285: Upgrade camel-jcr to Jackrabbit 2....

Posted by asfgit <gi...@git.apache.org>.
Github user asfgit closed the pull request at:

    https://github.com/apache/camel/pull/113


---
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.
---