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 (Jira)" <ji...@apache.org> on 2020/08/26 13:51:00 UTC

[jira] [Commented] (CAMEL-15439) configurer: use full qualified class name instead of simple class name

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

Claus Ibsen commented on CAMEL-15439:
-------------------------------------

Okay the long name is on the way. If you have the old way you can delete src/generated and re-generated to build with long name

> configurer: use full qualified class name instead of simple class name
> ----------------------------------------------------------------------
>
>                 Key: CAMEL-15439
>                 URL: https://issues.apache.org/jira/browse/CAMEL-15439
>             Project: Camel
>          Issue Type: Improvement
>          Components: camel-core
>            Reporter: Luca Burgazzoli
>            Assignee: Claus Ibsen
>            Priority: Minor
>             Fix For: 3.5.0
>
>
> Assuming we have a class like
> {code:java}
> package my.package;
> @Configurer
> class MyClass {
> }
> {code}
> Then the camel maven plugin creates an entry in
> {code}
> META-INF/services/org/apache/camel/configurer/MyClass
> {code}
> Which is fine as long as the use of configure does not get traction but as there's no qualifier for the class, it may happen that we have some naming clash.
> Maybe the configurer should generate
> {code}
> META-INF/services/org/apache/camel/configurer/my.package.MyClass
> {code}
> instead



--
This message was sent by Atlassian Jira
(v8.3.4#803005)