hi romney and rhauch,
the test unit for the method DateUtil.getCalendarFromStandardString() does't work because of a bug in the method.
possible value of timeZoneHour can be +01 or -01 etc.
the parse of the value -01 to -1 is possible but the parse of +01 to 1 isn't possible with the Integer.parseInt("+01") and thereby the method throws a java.lang.NumberFormatException: For input string: "+01"
int zoneOffsetInMillis = Integer.parseInt(timeZoneHour) * 60 * 60 * 1000;
@romney use jdk 1.5 in place of jdk 1.6.0_04, because the JBDNA is configured to be compiled and tested with jdk 1.5
<!-- Specify the compiler options and settings --> <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <configuration> <source>1.5</source> <target>1.5</target> <showDeprecation>false</showDeprecation> <showWarnings>false</showWarnings> </configuration> </plugin>
@romney: did you check out all of the projects, or just the 'dna-common' project?
@romney, @sisepago: Thanks for finding this problem. I've logged a new JIRA issue (http://jira.jboss.org/jira/browse/DNA-20), added a test case for a time zone prefixed with '+', and made a fix. The unit tests related to stopwatch are likely failing because Thread.sleep appears to be wildly inaccurate. Still looking into a good way of handling that.
I belive I got the entire project containing the following dir. structure:dna-common
The reason I asked is that I'm wondering why you needed to add the hamcrest library to the (dna-common?) pom.xml. That should have been inherited from the parent POM, which is right under 'trunk' (see https://svn.jboss.org/repos/dna/trunk/).
What version of Maven are you using? I'm using 2.0.7.
I am using maven 2.0.8.
I did not add the hamcrest library to dna-common pom.xml, but to the parent pom.xml. After looking through the logs I can see the hamcrest library was added to the parent pom.xml in revision 66.
Anyway, after updating parent pom.xml (and now using revision 66) everything works fine.
Great! Thanks again for running the tests. Stay tuned to the blog for announcements.