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 (Created) (JIRA)" <ji...@apache.org> on 2011/12/11 11:36:40 UTC

[jira] [Created] (SANSELAN-59) UnicodeMetricsUTF16 redefines constants BYTE_ORDER_BIG_ENDIAN & BYTE_ORDER_LITTLE_ENDIAN

UnicodeMetricsUTF16 redefines constants BYTE_ORDER_BIG_ENDIAN & BYTE_ORDER_LITTLE_ENDIAN
----------------------------------------------------------------------------------------

                 Key: SANSELAN-59
                 URL: https://issues.apache.org/jira/browse/SANSELAN-59
             Project: Commons Sanselan
          Issue Type: Bug
            Reporter: Sebb


The private class UnicodeMetricsUTF16 redefines the constants BYTE_ORDER_BIG_ENDIAN & BYTE_ORDER_LITTLE_ENDIAN which are also defined in the BinaryConstants class (also in scope but with different values).

This is very confusing; the private class should either use unique names for the settings, or it should use the ones from BinaryConstants.


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

        

[jira] [Resolved] (SANSELAN-59) UnicodeMetricsUTF16 redefines constants BYTE_ORDER_BIG_ENDIAN & BYTE_ORDER_LITTLE_ENDIAN

Posted by "Damjan Jovanovic (Resolved) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SANSELAN-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Damjan Jovanovic resolved SANSELAN-59.
--------------------------------------

    Resolution: Fixed

Fixed by commit 1213158, resolving fixed.

                
> UnicodeMetricsUTF16 redefines constants BYTE_ORDER_BIG_ENDIAN & BYTE_ORDER_LITTLE_ENDIAN
> ----------------------------------------------------------------------------------------
>
>                 Key: SANSELAN-59
>                 URL: https://issues.apache.org/jira/browse/SANSELAN-59
>             Project: Commons Sanselan
>          Issue Type: Bug
>            Reporter: Sebb
>
> The private class UnicodeMetricsUTF16 redefines the constants BYTE_ORDER_BIG_ENDIAN & BYTE_ORDER_LITTLE_ENDIAN which are also defined in the BinaryConstants class (also in scope but with different values).
> This is very confusing; the private class should either use unique names for the settings, or it should use the ones from BinaryConstants.

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

        

[jira] [Updated] (SANSELAN-59) UnicodeMetricsUTF16 redefines constants BYTE_ORDER_BIG_ENDIAN & BYTE_ORDER_LITTLE_ENDIAN

Posted by "Emmanuel Bourg (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SANSELAN-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emmanuel Bourg updated SANSELAN-59:
-----------------------------------

    Fix Version/s: 1.0
    
> UnicodeMetricsUTF16 redefines constants BYTE_ORDER_BIG_ENDIAN & BYTE_ORDER_LITTLE_ENDIAN
> ----------------------------------------------------------------------------------------
>
>                 Key: SANSELAN-59
>                 URL: https://issues.apache.org/jira/browse/SANSELAN-59
>             Project: Commons Sanselan
>          Issue Type: Bug
>            Reporter: Sebb
>             Fix For: 1.0
>
>
> The private class UnicodeMetricsUTF16 redefines the constants BYTE_ORDER_BIG_ENDIAN & BYTE_ORDER_LITTLE_ENDIAN which are also defined in the BinaryConstants class (also in scope but with different values).
> This is very confusing; the private class should either use unique names for the settings, or it should use the ones from BinaryConstants.

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