Allow for conditional aggregation of routes for DOT generation during the maven build.

• Key: CAMEL-413
• Type: New Feature
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Unassigned
• Reporter: Kevin Ross
• Affects Version/s: 1.2.0, 1.3.0
• Fix Version/s: 1.3.0

Description

For ease of unit testing, I separate distinct routes under different camel contexts. Unit testing is then quite easy, but DOT generation is really not a good representation when seeking to view the system as a whole.

This is a patch to camel-spring (Main.java), and the camel-maven-plugin. It allows the optional pom.xml configuration parameter (as well as a new Main.java parameter) to allow routes to be aggregated for the purposes of DOT generation only. Aggregation should have no impact on the runtime, and routes should not be started again.

Comments

[James Strachan]

Any chance you could re-cut the patches without reformatting all the code? Its really hard to see what you actually changed

[Kevin Ross]

Sorry, we have auto-format on save here, somewhat mandatory so we don't run into this exact situation (amongst our own team). I'll take a look and try to generate another patch.

[Kevin Ross]

Ok, I believe the new patches should be good. I replaced from the repo then copied over the changes and generated a new patch.

[James Strachan]

Patch applied, thanks!

[Claus Ibsen]

Closed all 1.3 tickets