Camel
  1. Camel
  2. CAMEL-263

Move components except bean and mock to a separate maven project

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: 2.0-M1
    • Component/s: camel-core
    • Labels:
      None

      Description

      Most of the components (except bean and mock) below package components are not referenced from the rest of the camel code. So my suggestion is to move these into a separate maven project that could be called camel-components-standard. The new project will of course include camel_core but camel_core will not need to include the components.

      The only components that are heavily referenced from the rest of the camel_core are bean and mock. These will have to stay in the maven core project of course.

      The separation will make understanding the camel core code easier as it gets smaller.

        Activity

        Christian Schneider created issue -
        Claus Ibsen made changes -
        Field Original Value New Value
        Fix Version/s 1.3.0 [ 11840 ]
        Fix Version/s 1.4.0 [ 11849 ]
        Hide
        Claus Ibsen added a comment -

        -1

        Then all the people need a lot of more dependent jars to work with Camel.

        I would even argue that some of the camel-spring components should be in the core or camel-core and came-spring be merged.
        When you combine Camel and Spring gives you the outstanding power.

        Show
        Claus Ibsen added a comment - -1 Then all the people need a lot of more dependent jars to work with Camel. I would even argue that some of the camel-spring components should be in the core or camel-core and came-spring be merged. When you combine Camel and Spring gives you the outstanding power.
        Hide
        Christian Schneider added a comment -

        I don´t mean each component should be in it´s own package. But a package with the basic components could be easily separated from the core. The separation would make sure that no core class references a component class.

        Show
        Christian Schneider added a comment - I don´t mean each component should be in it´s own package. But a package with the basic components could be easily separated from the core. The separation would make sure that no core class references a component class.
        Claus Ibsen made changes -
        Fix Version/s 2.0.0 [ 11900 ]
        Fix Version/s 1.4.0 [ 11849 ]
        Hide
        Claus Ibsen added a comment -

        We will get complications with the build order in maven, as we use the current components extensively in unit testing camel-core itself.

        Show
        Claus Ibsen added a comment - We will get complications with the build order in maven, as we use the current components extensively in unit testing camel-core itself.
        Claus Ibsen made changes -
        Resolution Won't Fix [ 2 ]
        Status Open [ 1 ] Resolved [ 5 ]
        Hadrian Zbarcea made changes -
        Fix Version/s 2.0-M1 [ 12061 ]
        Fix Version/s 2.0.0 [ 11900 ]
        Claus Ibsen made changes -
        Status Resolved [ 5 ] Closed [ 6 ]
        Jeff Turner made changes -
        Project Import Sat Nov 27 00:14:50 EST 2010 [ 1290834890113 ]
        Transition Time In Source Status Execution Times Last Executer Last Execution Date
        Open Open Resolved Resolved
        299d 23h 9m 1 Claus Ibsen 10/Oct/08 18:28
        Resolved Resolved Closed Closed
        378d 17h 47m 1 Claus Ibsen 24/Oct/09 12:16

          People

          • Assignee:
            Unassigned
            Reporter:
            Christian Schneider
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development