You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@camel.apache.org by tlehoux <gi...@git.apache.org> on 2017/05/28 04:23:05 UTC

[GitHub] camel pull request #1722: CAMEL-10768: Dropbox component support specifying ...

GitHub user tlehoux opened a pull request:

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

    CAMEL-10768: Dropbox component support specifying route params using headers

    This a patch to support setting options with headers for dropbox component. It's for all endpoint options except accessToken and clientIdentifier, for which, IMO, it was not relevant. 
    - remotePath
    - localPath
    - newRemotePath
    - uploadMode
    - query

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

    $ git pull https://github.com/tlehoux/camel master

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

    https://github.com/apache/camel/pull/1722.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 #1722
    
----
commit 1a544e57af3afb21c39c26edfaab98456472c9c9
Author: Thomas Lehoux <tl...@gmail.com>
Date:   2017-05-28T04:11:43Z

    Dropbox component support specifying route params using headers

----


---
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 #1722: CAMEL-10768: Dropbox component support specifying ...

Posted by tlehoux <gi...@git.apache.org>.

Github user tlehoux closed the pull request at:

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


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