You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Jean-Baptiste Onofré (Created JIRA)" <ji...@apache.org> on 2011/11/10 03:33:51 UTC
[jira] [Created] (KARAF-1001) Consistency between command
annotation and blueprint
Consistency between command annotation and blueprint
----------------------------------------------------
Key: KARAF-1001
URL: https://issues.apache.org/jira/browse/KARAF-1001
Project: Karaf
Issue Type: Improvement
Components: karaf-shell
Reporter: Jean-Baptiste Onofré
Fix For: 3.0.0
Currently, if you define a command annotation like this:
@Command(scope = "foo", name = "bar", ...)
and load the command using blueprint, with something like:
<command name="bar/foo">...</command>
the blueprint <command/> will have a precedence to the @Command annotation.
To be consistent, the @Command annotation should be the only one used, blueprint <command/> name should be only a blueprint ID (no impact on the command itself).
--
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
[jira] [Resolved] (KARAF-1001) Consistency between command
annotation and blueprint
Posted by "Guillaume Nodet (Resolved) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet resolved KARAF-1001.
------------------------------------
Resolution: Fixed
> Consistency between command annotation and blueprint
> ----------------------------------------------------
>
> Key: KARAF-1001
> URL: https://issues.apache.org/jira/browse/KARAF-1001
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Reporter: Jean-Baptiste Onofré
> Assignee: Guillaume Nodet
> Fix For: 3.0.0
>
>
> Currently, if you define a command annotation like this:
> @Command(scope = "foo", name = "bar", ...)
> and load the command using blueprint, with something like:
> <command name="bar/foo">...</command>
> the blueprint <command/> will have a precedence to the @Command annotation.
> To be consistent, the @Command annotation should be the only one used, blueprint <command/> name should be only a blueprint ID (no impact on the command itself).
--
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
[jira] [Assigned] (KARAF-1001) Consistency between command
annotation and blueprint
Posted by "Guillaume Nodet (Assigned) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Guillaume Nodet reassigned KARAF-1001:
--------------------------------------
Assignee: Guillaume Nodet
> Consistency between command annotation and blueprint
> ----------------------------------------------------
>
> Key: KARAF-1001
> URL: https://issues.apache.org/jira/browse/KARAF-1001
> Project: Karaf
> Issue Type: Improvement
> Components: karaf-shell
> Reporter: Jean-Baptiste Onofré
> Assignee: Guillaume Nodet
> Fix For: 3.0.0
>
>
> Currently, if you define a command annotation like this:
> @Command(scope = "foo", name = "bar", ...)
> and load the command using blueprint, with something like:
> <command name="bar/foo">...</command>
> the blueprint <command/> will have a precedence to the @Command annotation.
> To be consistent, the @Command annotation should be the only one used, blueprint <command/> name should be only a blueprint ID (no impact on the command itself).
--
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