Hello Developers and Jenkin users,

I tried to setup a Jenkins build with a forked geotools 2.5.x clone and run
into problems with jenkins. The main problem is, that the build process on
the same machine like my desktop produces different "output" than the
jenkins build server. Maven, Subversion and jdk are equal.

In the root directory of the hs-jdbc (modules/plugin/jdbc/jdbc-h2) module
are always created *.db and I checkt the osgeo hudson, its the same behavior
:
http://hudson.opengeo.org/hudson/view/geotools/job/geotools-2.7.x/ws/gt_2.7.x/modules/plugin/jdbc/jdbc-h2/

I tried to release with maven-release-plugin (release:prepare
release:perform) but it fails because of the "uncommitted" *.db files (via
the scm plugin it checks for local changes and if so the prepare goal fails.

Have anybody of you ever tried the maven-release-plugin in combination with
h2-test? I'm wondering because of the imagemosaic-jdbc, there are also
several h2 test cases, the driver initialization seems to be different and
in result any *.db file is create in the root folder of this module.

And that drives me crazy: On my local machine, any of these *.db files are
created in the jdbc-h2 module although the maven build started with the same
properties and parameters liek on the jenkins build machine.

This problem occurs on
2.7.x<http://hudson.opengeo.org/hudson/view/geotools/job/geotools-2.7.x/ws/gt_2.7.x/modules/plugin/jdbc/jdbc-h2/>and
on
trunk<http://hudson.opengeo.org/hudson/view/geotools/job/geotools-trunk/ws/gt_trunk/modules/plugin/jdbc/jdbc-h2/>
as
well. Properly its a bug in h2 if using it embedded ..

Do you have any suggestions?

Cheers and many thanks,
Frank
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel

Reply via email to