The Apache Jenkins build system has built Camel.trunk.notest (build #1817)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/1817/
to view the results.
I guess all is explained here: http://camel.apache.org/contributing.html
On Wed, Mar 13, 2013 at 2:53 PM, Mark wrote:
> I see on the Apache Camel "building" page
> (http://camel.apache.org/building.html) that the latest source is in
> subversion, but then I see on this list alot of references t
I see on the Apache Camel "building" page
(http://camel.apache.org/building.html) that the latest source is in
subversion, but then I see on this list alot of references to git
(https://github.com/apache/camel).
Are these mirrored?
Hi
Yeah we can for sure have both component and data format in the same
Maven component. We do this for others as well.
I think you are on the right track with your ideas.
Looking forward to your contributions.
On Wed, Mar 13, 2013 at 9:46 AM, Franz Paul Forsthofer
wrote:
> Hi,
>
> the API I
Hi,
the API I want to use is also available in Java 6 (see
http://docs.oracle.com/javase/6/docs/technotes/guides/security/xmldsig/overview.html).
I had a look at the project camel-xmlsecurity. The XML signature
feature will fit well into this project.
The XML en/decryption feature is implemented
Sorry to reply you late, I just came back when I was cleaning up the JIRA
issue today.
As you know we don't change the third part dependency version unless it has
some critical bug, I'm afraid you have to use Camel 2.11.0 for the
PoolingClientConnectionManager.
BTW, I just committed the code which
