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

classic Classic list List threaded Threaded
14 messages Options
Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
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
         Environment: Any
            Reporter: Kevin Ross
             Fix For: 1.3.0


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.

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org

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

Kevin Ross updated CAMEL-413:
-----------------------------

    Attachment: Dot-Aggregation-camel-maven-plugin.patch

> 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
>         Environment: Any
>            Reporter: Kevin Ross
>             Fix For: 1.3.0
>
>         Attachments: Dot-Aggregation-camel-maven-plugin.patch, 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.

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Kevin Ross updated CAMEL-413:
-----------------------------

    Attachment: Dot-Aggregation-camel-spring-Main.java.patch

> 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
>         Environment: Any
>            Reporter: Kevin Ross
>             Fix For: 1.3.0
>
>         Attachments: Dot-Aggregation-camel-maven-plugin.patch, 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.

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Claus Ibsen updated CAMEL-413:
------------------------------

        Fix Version/s: 1.4.0
                           (was: 1.3.0)
    Affects Version/s: 1.2.0
                       1.3.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.4.0
>
>         Attachments: Dot-Aggregation-camel-maven-plugin.patch, 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.

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/activemq/browse/CAMEL-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41933#action_41933 ]

James Strachan commented on CAMEL-413:
--------------------------------------

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

> 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.4.0
>
>         Attachments: Dot-Aggregation-camel-maven-plugin.patch, 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.

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/activemq/browse/CAMEL-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41934#action_41934 ]

Kevin Ross commented on CAMEL-413:
----------------------------------

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.


> 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.4.0
>
>         Attachments: Dot-Aggregation-camel-maven-plugin.patch, 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.

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/activemq/browse/CAMEL-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41934#action_41934 ]

[hidden email] edited comment on CAMEL-413 at 3/31/08 7:47 AM:
-----------------------------------------------------------

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.


      was (Author: [hidden email]):
    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.

 

> 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.4.0
>
>         Attachments: Dot-Aggregation-camel-maven-plugin.patch, 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.

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Kevin Ross updated CAMEL-413:
-----------------------------

    Attachment: Not-Formatted-Dot-Aggregation-camel-maven-plugin.patch

> 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.4.0
>
>         Attachments: Dot-Aggregation-camel-spring-Main.java.patch, Not-Formatted-Dot-Aggregation-camel-maven-plugin.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.

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Kevin Ross updated CAMEL-413:
-----------------------------

    Attachment:     (was: Dot-Aggregation-camel-maven-plugin.patch)

> 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.4.0
>
>         Attachments: Dot-Aggregation-camel-spring-Main.java.patch, Not-Formatted-Dot-Aggregation-camel-maven-plugin.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.

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Kevin Ross updated CAMEL-413:
-----------------------------

    Attachment: Not-Formatted-Dot-Aggregation-camel-spring-Main.java.patch

> 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.4.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.

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

Kevin Ross updated CAMEL-413:
-----------------------------

    Attachment:     (was: Dot-Aggregation-camel-spring-Main.java.patch)

> 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.4.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.

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

    [ https://issues.apache.org/activemq/browse/CAMEL-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=41935#action_41935 ]

Kevin Ross commented on CAMEL-413:
----------------------------------

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

> 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.4.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.

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

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

James Strachan resolved CAMEL-413.
----------------------------------

    Resolution: Fixed

Patch applied, thanks!

> 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.4.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.

Reply | Threaded
Open this post in threaded view
|

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

JIRA jira@apache.org
In reply to this post by JIRA jira@apache.org

     [ 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.