incubator-cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe San (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-1080) Interface heirarchy for AccountManagerImpl superflous
Date Fri, 01 Feb 2013 07:09:12 GMT

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

Joe San commented on CLOUDSTACK-1080:
-------------------------------------

I just wanted to know if there are any guidelines set up by the entire project and agreed
on some refactoring standards? If not, I can definitely come up with a proposal. 

How do you guys normally handle proposals? Should I create a new Jira or just send an email
to the dev list with my ideas? I would rather like to have a Jira ticket for this discussion.
                
> Interface heirarchy for AccountManagerImpl superflous
> -----------------------------------------------------
>
>                 Key: CLOUDSTACK-1080
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-1080
>             Project: CloudStack
>          Issue Type: Improvement
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: API
>            Reporter: Joe San
>            Assignee: Rohit Yadav
>            Priority: Trivial
>              Labels: Refactoring
>
> The AccountManagerImpl.java has two interfaces in its implements clause which is a bit
redundant. These two interfaces are already in the same heirarchy (AccountManager and AccountService).
Can we refactor the AccountManagerImpl to implement only the AccountManager?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message