[jira] [Commented] (ISIS-451) Abstract methods (and perhaps synthetic methods) not being filtered out of metamodel

["ASF subversion and git services (JIRA)" <ji...@apache.org>]

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

ASF subversion and git services commented on ISIS-451:
------------------------------------------------------

Commit e1fa54a20eb6506c6a8b5cb3837fa5af004bca4a in branch refs/heads/master from [~danhaywood]
[ https://git-wip-us.apache.org/repos/asf?p=isis.git;h=e1fa54a ]

ISIS-451: fixing filtering of synthetic/abstract methods from metamodel

                
> Abstract methods (and perhaps synthetic methods) not being filtered out of metamodel
> ------------------------------------------------------------------------------------
>
>                 Key: ISIS-451
>                 URL: https://issues.apache.org/jira/browse/ISIS-451
>             Project: Isis
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: core-1.2.0
>            Reporter: Dan Haywood
>            Assignee: Dan Haywood
>            Priority: Minor
>             Fix For: core-1.3.0
>
>
> ... leading to situation where two properties seemingly appear for the same method.
> For example, declare:
> public interface WithInterval<T> {
>     /// other stuff
>     T getNext();
>     T getPrevious();
> }
> and then:
> public class SomeEntity implements WithInterval<SomeEntity> {
>     ...
> }
> ... would find that there would be two "next" and two "previous" properties displayed.  One is for the impl within SomeEntity, and one is for the abstract definition of the method in WithInterval.

--
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