You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Frank Bille Jensen (JIRA)" <ji...@apache.org> on 2008/06/09 16:39:45 UTC

[jira] Resolved: (WICKET-1389) Tests fail due to different order of attributes (under Java 6)

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

Frank Bille Jensen resolved WICKET-1389.
----------------------------------------

    Resolution: Fixed

> Tests fail due to different order of attributes (under Java 6)
> --------------------------------------------------------------
>
>                 Key: WICKET-1389
>                 URL: https://issues.apache.org/jira/browse/WICKET-1389
>             Project: Wicket
>          Issue Type: Bug
>          Components: wicket
>    Affects Versions: 1.3.1
>         Environment: JDK 1.6.0_04
>            Reporter: Henrik Lundahl
>            Assignee: Frank Bille Jensen
>            Priority: Minor
>             Fix For: 1.4-M3
>
>
> When building wicket-1.3-SNAPSHOT using JDK 1.6.0_04 I get some test failures with messages all similar to this:
> < <style type="text/css" id="org-apache-wicket-ajax-MockComponent1-0">
> ---
> > <style id="org-apache-wicket-ajax-MockComponent1-0" type="text/css">
> It seems like the element attributes have come in the "wrong" order (compared to the test case).
> Since making the tests attribute order independent would probably be difficult, I suggest instead that the code is changed to guarantee that the attributes always come in the same order (TreeMap instead of HashMap?).

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