You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Christian Grobmeier (JIRA)" <ji...@apache.org> on 2009/01/07 07:36:46 UTC

[jira] Commented: (SANDBOX-245) ZipEntry has same name as superclass

    [ https://issues.apache.org/jira/browse/SANDBOX-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12661463#action_12661463 ] 

Christian Grobmeier commented on SANDBOX-245:
---------------------------------------------

This issue is fixed in the new trunk. Please close this issue with the comment "fixed", thank you.

> ZipEntry has same name as superclass
> ------------------------------------
>
>                 Key: SANDBOX-245
>                 URL: https://issues.apache.org/jira/browse/SANDBOX-245
>             Project: Commons Sandbox
>          Issue Type: Bug
>          Components: Compress
>            Reporter: Sebb
>
> public class ZipEntry
>     extends java.util.zip.ZipEntry
> As Findbugs says:
> {quote}
> [Nm] Class names shouldn't shadow simple name of superclass [NM_SAME_SIMPLE_NAME_AS_SUPERCLASS]
> This class has a simple name that is identical to that of its superclass, except that its superclass is in a different package (e.g., alpha.Foo extends beta.Foo). This can be exceptionally confusing, create lots of situations in which you have to look at import statements to resolve references and creates many opportunities to accidently define methods that do not override methods in their superclasses. 
> {quote}

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.