camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Schneider (JIRA)" <>
Subject [jira] Commented: (CAMEL-1677) Remove dependency cycles between model and sub packages
Date Mon, 08 Jun 2009 05:54:35 GMT


Christian Schneider commented on CAMEL-1677:

Oh and probably it is best you do not use the patch but rather move the classes in eclipse
yourself. I had only camel-core open and I guess some other projects could also use these

Btw. When you work on camel do you have all camel projects open in eclipse? I guess this could
make work a little slow but for cases like above it is probably necessary.


> Remove dependency cycles between model and sub packages
> -------------------------------------------------------
>                 Key: CAMEL-1677
>                 URL:
>             Project: Apache Camel
>          Issue Type: Improvement
>          Components: camel-core
>    Affects Versions: 2.0-M1
>            Reporter: Christian Schneider
>            Assignee: Willem Jiang
>             Fix For: 2.0-M2
>         Attachments: camel-core.patch, model-before.png, model_after.png
> Currently there is a dependency cycle between model and model.loadbalancer and between
model and model.dataformat. The reason in both cases that the base classes DataFormatDefinition
and LoadBalancerDefinition are in the subpackages but are referenced from model. 
> I think the goal should be that model does not reference the subpackages.
> The easy solution is to move the two classes above to model. After the move the cycles
are gone.

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

View raw message