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

Posted to dev@camel.apache.org by donovanmuller <gi...@git.apache.org> on 2015/12/16 00:09:51 UTC

[GitHub] camel pull request: CAMEL-9424 Correctly build TriggerKey using th...

GitHub user donovanmuller opened a pull request:

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

    CAMEL-9424 Correctly build TriggerKey using the trigger prefix releva…

    …nt to the Action. This fixes the fuplicate trigger name issue when setting both start and stop route times on a CronScheduledRoutePolicy.

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

    $ git pull https://github.com/donovanmuller/camel CAMEL-9424

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

    https://github.com/apache/camel/pull/732.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 #732
    
----
commit 5d5bcfada07ded8e46c27aa07d194e7e7eb555bb
Author: Donovan Muller <do...@gmail.com>
Date:   2015-12-15T22:56:44Z

    CAMEL-9424 Correctly build TriggerKey using the trigger prefix relevant to the Action. This fixes the fuplicate trigger name issue when setting both start and stop route times on a CronScheduledRoutePolicy.

----


---
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-9424 Correctly build TriggerKey using th...

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

Github user donovanmuller closed the pull request at:

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


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