You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Sebb (JIRA)" <ji...@apache.org> on 2008/07/06 15:28:52 UTC

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

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.

[jira] Moved: (COMPRESS-10) ZipEntry has same name as superclass

Posted by "Dennis Lundberg (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/COMPRESS-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg moved SANDBOX-245 to COMPRESS-10:
-------------------------------------------------

    Component/s:     (was: Compress)
            Key: COMPRESS-10  (was: SANDBOX-245)
        Project: Commons Compress  (was: Commons Sandbox)

> ZipEntry has same name as superclass
> ------------------------------------
>
>                 Key: COMPRESS-10
>                 URL: https://issues.apache.org/jira/browse/COMPRESS-10
>             Project: Commons Compress
>          Issue Type: Bug
>            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.

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

Posted by "Christian Grobmeier (JIRA)" <ji...@apache.org>.
    [ 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.

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

Posted by "Torsten Curdt (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SANDBOX-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Torsten Curdt closed SANDBOX-245.
---------------------------------

    Resolution: Fixed

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