The Apache Jenkins build system has built Camel.trunk.notest (build #3478)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3478/
to view the results.
The Apache Jenkins build system has built Camel.trunk.notest (build #3477)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3477/
to view the results.
GitHub user valdar opened a pull request:
https://github.com/apache/camel/pull/1874
CAMEL-11635 : corrected wrong groupId in camel examples readme.md and
features.xml
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/valdar/camel
The Apache Jenkins build system has built Camel.trunk.notest (build #3476)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3476/
to view the results.
+1 looks promising for data type metadata as well!
It'll need something similar for DataFormat so it can hold type
metadata as well as components, but it can be addressed separately.
Thanks,
Tomo
On Fri, 2017-08-04 at 14:13 +0200, Claus Ibsen wrote:
> On Fri, Aug 4, 2017 at 2:09 PM, Luca Burgaz
GitHub user valdar opened a pull request:
https://github.com/apache/camel/pull/1873
CAMEL-11634 : clean up dbcp 1 dependencies and move it (where possible) to
dbcp 2
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/valdar/camel C
GitHub user Fabryprog opened a pull request:
https://github.com/apache/camel/pull/1872
CAMEL-11633 - Upgrade client mqtt paho base lib
lib upgrade https://issues.apache.org/jira/browse/CAMEL-11633
You can merge this pull request into a Git repository by running:
$ git pull http
Github user asfgit closed the pull request at:
https://github.com/apache/camel/pull/1870
---
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 enab
GitHub user ramu11 opened a pull request:
https://github.com/apache/camel/pull/1871
"CAMEL-11617:spring-boot - service-call tests uses hardcoded port numbers"
 "CAMEL-11617:spring-boot - service-call tests uses hardcoded port
numbers"
You can merge this pull
GitHub user Fabryprog opened a pull request:
https://github.com/apache/camel/pull/1870
CAMEL-11631, Camel-Paho Missiong reconnect logic
https://issues.apache.org/jira/browse/CAMEL-11631
You can merge this pull request into a Git repository by running:
$ git pull https://github.
On Fri, Aug 4, 2017 at 2:09 PM, Luca Burgazzoli wrote:
> Would be nice to make @Metadata repeatable so we can better express
> multiple concepts like:
>
> @Metadata(label = "extensions", types = { A.class, B.class, ...})
> @Metadata(label = "cloud,saas")
> class MyComponent extends DefaultComponen
The Apache Jenkins build system has built Camel.trunk.notest (build #3475)
Status: Still Failing
Check console output at https://builds.apache.org/job/Camel.trunk.notest/3475/
to view the results.
Would be nice to make @Metadata repeatable so we can better express
multiple concepts like:
@Metadata(label = "extensions", types = { A.class, B.class, ...})
@Metadata(label = "cloud,saas")
class MyComponent extends DefaultComponent {
}
---
Luca Burgazzoli
On Fri, Aug 4, 2017 at 1:35 PM, Claus
GitHub user Sw1m1k opened a pull request:
https://github.com/apache/camel/pull/1869
Update AbstractSObjectBase.java
Commented: OwnerId = null
Sometimes need to update Owner.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com
Hey Luca
Just took a bit of look, especially the first commit about the changes
involving camel-core.
I really like this, great work, its more cleaner and the code is
separated into that component.extension package.
+1
Down the road we should have the some metadata on @Metadata or
something so
Github user vrlgohel closed the pull request at:
https://github.com/apache/camel/pull/1867
---
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 en
Hello,
I've recently been working on CAMEL-11550 [1] aimed to introduce the
concept of "Component Extensions" which are functionalities not directly
targeting Camel runtime but that can provide some useful stuffs as
example for tooling.
You can find the implementation on my camel fork [2] which i
Github user sarel2 closed the pull request at:
https://github.com/apache/camel/pull/1862
---
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 enab
18 matches
Mail list logo
