[jboss-jira] [JBoss JIRA] (WFLY-3622) CLI should WARN about usage deprecated api

Brian Stansberry (JIRA) issues at jboss.org
Mon Jul 14 11:40:33 EDT 2014


    [ https://issues.jboss.org/browse/WFLY-3622?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12984829#comment-12984829 ] 

Brian Stansberry commented on WFLY-3622:
----------------------------------------

Perhaps in the interactive shell; not in any non-interactive usage since it will change the output. Unless it becomes part of some operation response header in the low level API (i.e. from read-resource, read/write-attribute, any deprecated non-global op).

If it's part of the low level responses, it shouldn't break read-resource by including the header for a non-deprecated resource just because the response includes a deprecated attribute.

> CLI should WARN about usage deprecated api
> ------------------------------------------
>
>                 Key: WFLY-3622
>                 URL: https://issues.jboss.org/browse/WFLY-3622
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: CLI
>            Reporter: Tomaz Cerar
>            Assignee: Alexey Loubyansky
>             Fix For: 9.0.0.CR1
>
>
> We added support for deprecating resouces/attributes/operations/parameters some time ago.
> I would be a good thing that we would warn users if they are using deprecated API.
> Every resource/attribute/operation/param that is deprecated has extra element "deprecated" in metadata
> With sub elements 
> - "since", which tells in what version it was deprecated
> - "reason", text description why it is deprecated.
> Reason in most cases also tells what is new replacement.



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)


More information about the jboss-jira mailing list