db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (DERBY-436) clean up imports and static field references in DRDA classes
Date Thu, 19 Jul 2012 20:39:34 GMT

     [ https://issues.apache.org/jira/browse/DERBY-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Knut Anders Hatlen updated DERBY-436:
-------------------------------------

    Attachment: d436.diff

Here's a patch that fixes the import and static field issues I found in the org.apache.derby.impl.drda
and org.apache.derby.drda packages. I just told NetBeans to organize the imports, on the assumption
that it organizes them in a way that Eclipse also is happy with.

All the regression tests passed.
                
> clean up imports and static field references in DRDA classes
> ------------------------------------------------------------
>
>                 Key: DERBY-436
>                 URL: https://issues.apache.org/jira/browse/DERBY-436
>             Project: Derby
>          Issue Type: Task
>          Components: Network Server
>    Affects Versions: 10.1.1.0, 10.2.1.6
>            Reporter: Kathey Marsden
>         Attachments: d436.diff
>
>
> In DRDA Classes, eg. DRAConnThread.java, and other classes in org.apache.derby.drda,
 Eclipse shows that the imports need to be organized and the static field references need
to be referenced in a static way. It would be good to clean up the warnings.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message