next m2eclipse Problem

My Project has the standard Project structure which is recommended by maven.


scr
|-main
| |-java
| |-resources
|-test
| |-java
| |-resources


under main-resources I have my "real" properties file which has the real mysql-database connection parameters and under test-resources I have a test properties file which points to a in-memory HSQLDB.
When running the JUnit Tests standalone the Test took the test properties file and everything was OK. When running maven with goal Package, the tests failed. I was adding some debug-messages and found out, that maven took the wrong properties file (the "real" properties file).
After a long period of googling around and trying to configure the surefire-plugin I tried to call the target from the console ...
I THINK I'M GOING TO KICK THE m2eclipse PLUGIN SINCE IT IS THE SECOND TIME IT COST ME A LOT OF TIME !

JDK 1.4 - 1.5 Compatibility Problem

It has been the third time, that I experienced problems by migrating a Project from JDK 1.4 to JDK 1.5. Every time I remembered about "a problem" but never remembered what it exactly was.
In this Post I want to sum up these Problems.
Actually I only know one, but it's noteworthy. REALLY :-)
The Problem causes Bigdecimal to work in a different way when using the toString method
Here is the bug report.