It seems a couple of people are getting a head of themselves.
Firstly, the -1 vote of Dan and Hadrian are invalid without a technical
justification, and it seems they are trying to justify a -1 on some policy by
the Camel PMC that I for one are not aware of.
We have discussed removing the came
The Apache Jenkins build system has built Camel.trunk.notest (build #2048)
Status: Failure
Check console output at https://builds.apache.org/job/Camel.trunk.notest/2048/
to view the results.
On Nov 28, 2013, at 8:42 AM, James Strachan wrote:
> Should we back out the use of graphviz too? Do you think generating images
> for camel routes should be -1'd too?
No. Graphviz is a graphics library. ALL the code for taking the camel
routes and feeding the information into graphiz lives
+1
On Thu, Nov 28, 2013 at 9:08 PM, Hadrian Zbarcea wrote:
> The camel:dot goal provided by the camel-maven-plugin has not been
> maintained in 5+ years, produces poor quality output and, most importantly,
> doesn't seem to be used. I propose to remove it.
>
> Hadrian
>
>
+1
--
Willem Jiang
Red Hat, Inc.
Web: http://www.redhat.com
Blog: http://willemjiang.blogspot.com (http://willemjiang.blogspot.com/)
(English)
http://jnn.iteye.com (http://jnn.javaeye.com/) (Chinese)
Twitter: willemjiang
Weibo: 姜宁willem
On Friday, November 29, 2013 at 12:19 P
it happens when I use exchange in my java. There's no such issue when I use
other method in java to get body and header of file.
I have already verified that jar file. It is aready there :(
--
View this message in context:
http://camel.465427.n5.nabble.com/Using-org-apache-camel-Exchange-tp574
You still have a classpath issue. Verify that camel-core jar file is well
included
On Fri, Nov 29, 2013 at 3:46 AM, Claire wrote:
> I wonder if this because of the way I called Exchange? Here's the full
> exception.
>
> *Application context refresh failed
>
> (OsgiBundleXmlApplicationContext(bun
+1.
On Fri, Nov 29, 2013 at 2:08 AM, Hadrian Zbarcea wrote:
> The camel:dot goal provided by the camel-maven-plugin has not been
> maintained in 5+ years, produces poor quality output and, most importantly,
> doesn't seem to be used. I propose to remove it.
>
> Hadrian
>
>
>
Hi everyone,
Two weeks now I created a JIRA task with a patch for improving the CSV
unmarshalling. It know that you have been busy with more important
matter on the latest camel release.
What do you think ? Is it a bad idea ? a good idea ? a good idea with
a bad implementation ?
Thanks a lot,
A
