The 1.6 hashmap implementation has changed which leads to the iterator returing the keys and/or values in a different order. Hence, it is only the test which fails, but wicket is still working correct.
Juergen On 8/12/07, Sean Sullivan <[EMAIL PROTECTED]> wrote: > Sun JDK 1.6.0 was the culprit. > > Maven 2.0.7 + Sun JDK 1.6.0 -------> tests fail > > Maven 2.0.7 + Sun JDK 1.5.0_11 -----> tests pass > > Cheers, > > Sean > > > On 8/11/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote: > > > > i dont think our tests work right on jdk6, not time to double check right > > now though. > > > > -igor > > > > > > On 8/11/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote: > > > > > > On 8/11/07, Sean Sullivan <[EMAIL PROTECTED]> wrote: > > > > I updated my workspace and I have all of the latest Wicket trunk > > > code. When > > > > I build with Maven: > > > > > > > > mvn clean install > > > > > > > > I see test failures: > > > > > > I just ran all unit tests and had no problems. Can you update and try > > > again? Btw, you can see the status of builds here > > > http://wicketstuff.org/bamboo/ > > > > > > Also, note that you don't have to build yourself if you want to use > > > snapshots. You can include: > > > > > > <repositories> > > > <repository> > > > <id>wicket-stuff.org</id> > > > <url>http://wicketstuff.org/maven/repository/ > > > </url> > > > <snapshots> > > > <enabled>true</enabled> > > > </snapshots> > > > </repository> > > > </repositories> > > > > > > <dependencies> > > > <dependency> > > > <groupId>org.apache.wicket</groupId> > > > <artifactId>wicket</artifactId> > > > <version>1.3.0-SNAPSHOT</version> > > > <type>jar</type> > > > <scope>compile</scope> > > > </dependency> > > > > > > in your maven file, so that you'll get the snapshots from our build > > > server. > > > > > > Or yet another way (which I use for development) is to just check the > > > wicket projects out and use them as project dependencies in my Eclipse > > > workspace. > > > > > > Eelco > > > > > >
