As an experiment, I disabled Maven tests via command line 'mvn -Dmaven.test.skip=true' which results in the following new errors:
Basically the error is a BeanDefinitionStoreException that's thrown by Jetty while initializing the Spring root WebApplicationContext. It happens because of an invalid bean definition named 'cfg' in applicationContext.xml that can't resolve placeholder 'ipt.datadir', though I haven't figured out why the placeholder is causing problems yet.
On Wed, Aug 26, 2009 at 3:45 PM, Aaron Steeleeightysteele@gmail.com 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: