It is running tests-served.
I can't see how it might be picking up an extra property.
I'm using the script to run using
$ bash ./msdf.sh
I'm also using 2.2.1:-
$ mvn -version
/usr/java/jdk1.6.0_26/bin/..
Apache Maven 2.2.1 (rNON-CANONICAL_2011-02-08_16-41_mockbuild;
2011-02-08 16:41:04+0000)
Java version: 1.6.0_26
Java home: /usr/java/jdk1.6.0_26/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux" version: "2.6.38.8-32.fc15.x86_64" arch: "amd64"
Family: "unix"
Rob
On 07/07/11 10:53, Kevin Meyer - KMZ wrote:
Rob's build is definitely running the "tests-served" profile, which means
that somewhere he is picking up a "-P integration-tests".
To build the site documentation, I use the bashalias mssd which is
short for:
mvn site-deploy -D modules=site -D deploy=local
I notice that the contributers guide refers to running the integration-
tests, in section 12.4.3 "Dry Run".
I am using Maven mvn 2.2.1, for what its worth.
Regards,
Kevin
On 7 Jul 2011 at 7:06, Dan Haywood wrote:
As I understand this (Kevin worked on this code the most recently), the
'tests-served' modules have a dependency on a MySQL server being
installed. I don't have MySQL installed myself, so what I can't quite
work out is why the tests don't hang for me too.
At any rate, I think the workaround is just to remove 'tests-served'
from the 'modules' file (which is used to drive the msdf.sh script).
Given this is just the site documentation which has already been
generated, I'm happy not to sweat it if you are?
Dan
~~~~~~~~~
On 06/07/2011 22:04, Robert Matthews wrote:
This is the line that it stops at:
Forking command line: /bin/sh -c cd
/home/rcm/tmp/isis-0.1.2-incubating/runtimes/dflt/objectstores/sql/tests-served
&& /usr/java/jdk1.6.0_26/jre/bin/java -jar
/home/rcm/tmp/isis-0.1.2-incubating/runtimes/dflt/objectstores/sql/tests-served/target/surefire/surefirebooter2544362058491521935.jar
/home/rcm/tmp/isis-0.1.2-incubating/runtimes/dflt/objectstores/sql/tests-served/target/surefire/surefire3369931567537246989tmp
/home/rcm/tmp/isis-0.1.2-incubating/runtimes/dflt/objectstores/sql/tests-served/target/surefire/surefire1520401733116391419tmp
This just suggests that one of tests is hanging. I am seeing port 3306
being blocked by my firewall while trying to get to an unknown server.
Now I don't believe anything else on my machine is trying to access
MySql anywhere. Could this be your test settings?
Rob
On 06/07/11 13:40, Kevin Meyer - KMZ wrote:
Hi Rob,
This is really weird - the default SQL tests just use HSQLDB, so there
shouldn't be any issue.
You would need to enable full integration testing to switch on "served"
tests, which then look for database servers (you'll noticed timeouts
searching for "abacus" - my server).
Is your system running:
Default Runtime SQL ObjectStore Integration Tests - Common
or
Default Runtime SQL ObjectStore Integration Tests - Served
If the latter, you *will* need to update the mysql.properties and
postgresql.properties in the sql-tests-served project.
The latter is turned on by profile "integration-tests", BTW.
Regards,
Kevin
On 6 Jul 2011 at 12:55, Robert Matthews wrote:
On trying the site build I get infinite pause in 'Default Runtime SQL
ObjectStore Integration Tests'. I've Ctrl-C'd it so it continues with
the next project and the rest complete fine.
Rob
