You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (Resolved) (JIRA)" <ji...@apache.org> on 2012/01/24 13:44:40 UTC
[jira] [Resolved] (CAMEL-4934) CamelBeanPostProcessor - Move from
camel-spring to camel-core to make it reuseable by others such as
camel-blueprint and camel-test
[ https://issues.apache.org/jira/browse/CAMEL-4934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-4934.
--------------------------------
Resolution: Fixed
Moved logic to camel-core so it can be reused by camel-test, camel-blueprint and others without the need for Spring JARs on the classpath.
> CamelBeanPostProcessor - Move from camel-spring to camel-core to make it reuseable by others such as camel-blueprint and camel-test
> -----------------------------------------------------------------------------------------------------------------------------------
>
> Key: CAMEL-4934
> URL: https://issues.apache.org/jira/browse/CAMEL-4934
> Project: Camel
> Issue Type: Improvement
> Components: camel-core, camel-spring
> Reporter: Claus Ibsen
> Assignee: Claus Ibsen
> Fix For: 2.10.0
>
>
> The CamelBeanPostProcessor is currently in camel-spring for historical reasons. We should move it to camel-core, to let it be reusable by camel-test and camel-blueprint as well.
> This will also ensure that using CamelTestSupport you can use the Camel @EndpointInject, @Produce etc annotations in your unit test classes.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira