no reason for being java6 only, really not intended. The POM specifies to build java5 classes and my eclipse compiler settings actually say java5 compliant. But thats not true as you have found out. When I use java5 as the default compiler in eclipse I see the DataResource class is in trouble.
The SQLException is old, but unfortunately not the specific constructor: http://java.sun.com/j2se/1.4.2/docs/api/java/sql/SQLException.html
I have fixed DataResource and comitted it to the trunk. That was all there is to make it java5 compliant again.
The stupid maven doesnt find the symbol/class error doesnt occurr here. really strange. I always had the feeling this is because of the WAR overlays and the AppFuse framework. Maybe its time to get rid of it and keep the IPT independant of AppFuse - but that is a bit of work...
Ah, and Ive changed the POM profiles so that: - by default no tests are run, so $mvn should work now to get jetty up and running - a new profile -P test is added that uses the gbif test registry and does run all tests
Markus
On Aug 27, 2009, at 0:45, Aaron Steele wrote:
SQLException(String reason, Throwable cause) was added in Java 6.
I discovered the same and modified my working copy of DataResource.java to be Java 1.5 compliant. Is there a reason for for this 1.5 incompatibility?
Also, do we have documentation for setting up Eclipse for IPT development? Here's how I've set things up in Eclipse so far:
SVN checkout of trunk/gbif-providertool
Command line 'mvn eclipse:eclipse' fails (http://txtb.in/4d6). The
workaround is setting the filtering property to true on line 260 of pom.xml, although I'm not sure what the implications are for this change.
- Command line 'mvn -Declipse.workspace=~/Projects/Workspace
eclipse:configure-workspace' results in .classpath errors (http://txtb.in/4d9). The workaround is deleting the 'output' properties from the following classpath entires in the .classpath file:
<classpathentry kind="src" path="src/main/webapp/data" /> <classpathentry kind="src" path="src/main/webapp/WEB-INF/pages" />
Finally, running command line 'mvn' results in a build failure due to 69 test errors: