Camel.trunk.notest - Build # 1917 - Still Failing

The Apache Jenkins build system has built Camel.trunk.notest (build #1917) Status: Still Failing Check console output at https://builds.apache.org/job/Camel.trunk.notest/1917/ to view the results.

Re: Xml schema RouteDefinition

And to avoid a bad design, it should be only = 1 and not 1..N On Sun, Jun 30, 2013 at 3:08 PM, Claus Ibsen wrote: > Hi > > Yeah there is no reason why it can be 0. It should really be 1..n. > Though 99% uses a single in a route. > > So yeah if we can have the schema generated with 1 as minimum

Camel.trunk.notest - Build # 1916 - Failure

The Apache Jenkins build system has built Camel.trunk.notest (build #1916) Status: Failure Check console output at https://builds.apache.org/job/Camel.trunk.notest/1916/ to view the results.

[HEADS UP] - Apache Camel 2.10.6 release because of CVE-2013-2160

is in preparation... Best, Christian - Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Camel: https://www.apache.org/foundation/ Apache Member: https://www.apache.org/foundation/members.html https://www.linkedin.com/pub/christian

Re: [DISCUSS] - Apache Camel 2.11.1 release

Thanks Hadrian for the offer. If we are not able to start the release this week, I'm happy to take this over to you :-). I updated the maven release plugin configuration for the 2.11.x maintenance branch to use the Git repo and merged Dan's change to only generate the HTML manual. I tested it and

Re: Check Style MutableException check

Because we cannot rename the classes (part of the API) or delete the setter methods (used by the unmarshaller), I went ahead and updated the Check Style rule... Best, Christian - Software Integration Specialist Apache Camel committer: https://camel.apache.org/team V.P. Apache Cam

Check Style MutableException check

Because of this check [1], the check style validation of the following classes fails: org/apache/camel/component/salesforce/api/dto/bulk/Error.java org/apache/camel/component/salesforce/api/dto/bulk/ResultError org/apache/camel/component/salesforce/internal/dto/LoginError If no body has objections

Re: Xml schema RouteDefinition

Hi Yeah there is no reason why it can be 0. It should really be 1..n. Though 99% uses a single in a route. So yeah if we can have the schema generated with 1 as minimum then that would be better. Feel free to log a JIRA and provide a patch. On 6/30/13, AlanFoster wrote: > Hi guys, > > I'm jus

Xml schema RouteDefinition

Hi guys, I'm just wondering if there are any technical reasons why a RouteDefinition is allowed zero to unbounded occurrences of the `from` element; >From the Schema for camel 2.10.0 - .. ..