Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/1798
---
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
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/1798
CAMEL-11473: camel-kafka - Use unique groupId by default
https://issues.apache.org/jira/browse/CAMEL-11473
You can merge this pull request into a Git repository by running:
$ git pull https
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/822
---
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
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/567
---
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
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/1188
---
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
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/1188
CAMEL-10347: camel-scr todos and polish
https://issues.apache.org/jira/browse/CAMEL-10347
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/yuruki
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/1186
---
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
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/1186
CAMEL-10339: Allow date offsets and timezones with Simple language
https://issues.apache.org/jira/browse/CAMEL-10339
You can merge this pull request into a Git repository by running:
$ git pull
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/1162
---
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
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/1163
---
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
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/1163
CAMEL-10298: Remove readLockTimeout check from readLockMinAge (2.17.x)
https://issues.apache.org/jira/browse/CAMEL-10298
You can merge this pull request into a Git repository by running:
$ git
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/1162
CAMEL-10298: Remove readLockTimeout check from readLockMinAge
https://issues.apache.org/jira/browse/CAMEL-10298
You can merge this pull request into a Git repository by running:
$ git pull
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/822
CAMEL-9498: Universal local registry for CamelContext
This change adds an always available local SimpleRegistry to CamelContext.
Local registry makes sure that you can always add beans
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/773
---
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
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/760
---
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
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/773
CAMEL-9498: Always provide a writable local registry (camel-2.16.x)
https://issues.apache.org/jira/browse/CAMEL-9498
plus some polish
You can merge this pull request into a Git repository
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/760
CAMEL-9498: Always provide a writable local registry
https://issues.apache.org/jira/browse/CAMEL-9498
+ some polish
You can merge this pull request into a Git repository by running
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/626
CAMEL-9181: Simplify ScrHelper
CAMEL-9181 for master branch.
https://issues.apache.org/jira/browse/CAMEL-9181
You can merge this pull request into a Git repository by running:
$ git
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/623
CAMEL-9166 for 2.15.x
Here's the same CAMEL-9166 prefixing and backward compatibility fix for
2.15.x branch.
You can merge this pull request into a Git repository by running:
$ git pull https
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/620
CAMEL-9166: Some functionality broken in Camel-8857
https://issues.apache.org/jira/browse/CAMEL-9166
You can merge this pull request into a Git repository by running:
$ git pull https
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/567
CAMEL-8999 Watchdog route policy
Watchdog route policy for spotting starved, overactive or stuck routes.
You can merge this pull request into a Git repository by running:
$ git pull https
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/467
---
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
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/467
CAMEL-7833 InOnly and InOut routes as ObservableExchange sequences
Basic InOnly and InOut routes seem to just work as ObservableExchange
sequences.
To be honest, I don't quite understand why
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/464
---
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
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/459
---
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
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/462
CAMEL-7833 Added convenience method ReactiveCamel.to(...)
Added convenience method ReactiveCamel.to(String uri) and
ReactiveCamel.to(Endpoint endpoint) for nicer DSL experience.
Changed
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/464
camel-scr: Removed unnecessary method calls
No effect in practice, but stopCamelContext() was called twice in a row for
no reason.
You can merge this pull request into a Git repository by running
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/462
---
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
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/459
CAMEL-7833 Use Camel endpoints inside RX sequence
CamelOperator class allows us to use Camel endpoints inside an RX sequence,
like so:
```
ObservableMessage
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/419
---
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
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/414
---
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
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/419
CAMEL-8439 Use setAutoStartup(false) instead of skipping start()
https://issues.apache.org/jira/browse/CAMEL-8439
You can merge this pull request into a Git repository by running:
$ git pull
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/343
---
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
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/303
---
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
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/329
---
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
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/329
CAMEL-7997 working on camel-scr todos
* Removed JBoss Fuse references.
* Projects generated by camel-archetype-scr now run in vanilla Karaf
(2.4.0).
* Got rid of public fields
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/316
---
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
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/316
CAMEL-7997 New modules: camel-scr, camel-archetype-scr
Support module and archetype for running Camel in Service Component Runtime
(OSGi Declarative Services) bundles.
You can merge this pull
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/295
---
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
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/296
---
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
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/303
CAMEL-1077 Added remote address support to camel-netty consumer
This pull request adds *clientMode* parameter to netty component. When
*clientMode* is true netty consumer will listen to the given
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/296
CAMEL-7875 Method for adding objects to Registry
Having a write method in Registry interface simplifies configuring Camel
routes in CamelTestSupport unit tests where a registry reference
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/295
ENH-354 Adding properties to PropertiesComponent
Added setInitialProperties(Properties initialProperties) and
getInitialProperties() public methods to PropertiesComponent. These methods
allow us
Github user yuruki closed the pull request at:
https://github.com/apache/camel/pull/221
---
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
GitHub user yuruki opened a pull request:
https://github.com/apache/camel/pull/221
Add system property and env variable resolving to property prefix and suffix
This change adds system property and environment variable resolving to
PropertiesComponent's propertyPrefix
45 matches
Mail list logo
