You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Hadrian Zbarcea (JIRA)" <ji...@apache.org> on 2008/04/02 15:14:32 UTC

[jira] Updated: (CAMEL-413) Allow for conditional aggregation of routes for DOT generation during the maven build.

     [ https://issues.apache.org/activemq/browse/CAMEL-413?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hadrian Zbarcea updated CAMEL-413:
----------------------------------

    Fix Version/s: 1.3.0
                       (was: 1.4.0)

> Allow for conditional aggregation of routes for DOT generation during the maven build.
> --------------------------------------------------------------------------------------
>
>                 Key: CAMEL-413
>                 URL: https://issues.apache.org/activemq/browse/CAMEL-413
>             Project: Apache Camel
>          Issue Type: New Feature
>    Affects Versions: 1.2.0, 1.3.0
>         Environment: Any
>            Reporter: Kevin Ross
>             Fix For: 1.3.0
>
>         Attachments: Not-Formatted-Dot-Aggregation-camel-maven-plugin.patch, Not-Formatted-Dot-Aggregation-camel-spring-Main.java.patch
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.