[ https://issues.apache.org/jira/browse/ARIES-1858?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16679795#comment-16679795 ]
ASF subversion and git services commented on ARIES-1858: -------------------------------------------------------- Commit 1846140 from ggrzy...@apache.org in branch 'aries/trunk' [ https://svn.apache.org/r1846140 ] [ARIES-1858][CAMEL-12570] Add semantic exception for deprecated AbstractPropertyPlaceholder > Make typed property placeholders compatible with older Camel versions > --------------------------------------------------------------------- > > Key: ARIES-1858 > URL: https://issues.apache.org/jira/browse/ARIES-1858 > Project: Aries > Issue Type: Improvement > Components: Blueprint > Affects Versions: blueprint-core-1.10.0 > Reporter: Grzegorz Grzybek > Assignee: Grzegorz Grzybek > Priority: Major > Fix For: blueprint-core-1.10.1 > > > ARIES-1298 changed the runtime class of bean registered from > {{{http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.x.0}property-placeholder}} > and > {{{http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.x.0}property-placeholder}}. > This is definitely not caught by semver plugin. > {{camel-blueprint}} (see CAMEL-12570) added support for this new runtime > class - it was needed because Camel explicitly casts and uses reflection on > old {{org.apache.aries.blueprint.ext.AbstractPropertyPlaceholder}} class, > while blueprint-core 1.10.0 registers placeholder class that extends > {{org.apache.aries.blueprint.ext.AbstractPropertyPlaceholderExt}} - and these > two are not related. > The problem is that when user will try to upgrade to e.g., Karaf with > blueprint-core 1.10.0 *without upgrading Camel*, Camel blueprint will stop > detecting blueprint property resolvers. -- This message was sent by Atlassian JIRA (v7.6.3#76005)