i think that's right.
at least there is no JDK 6 switch or something.
/heiko
On Fri, 2008-10-24 at 14:01 +0200, Joram Barrez wrote:
Tom,
I believe that Maven uses the JAVA_HOME variable.
Perhaps it's also safe to add this to the pom.xml (I've had problems
without it in the past)
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<configuration>
<source>1.6</source>
<target>1.6</target>
</configuration>
</plugin>
</plugins>
</build>
Joram
On Fri, Oct 24, 2008 at 1:58 PM, Tom Baeyens <tbaeyens(a)redhat.com>
wrote:
afaict from the hudson build so far, the database problem has
gone leaving only the JSK 6 problem.
that is what i want to tackle next.
i tried running mvn with JDK 6 on the classpath. that didn't
help as i'd feared.
iirc, maven doesn't take the jvm from the classpath, but
controls it all in the plugins right? i'll be searching in
that area to see which 'buttons' i have to push to reproduce
the jdk 6 failure locally.
if beat me in finding the pointers to run the tests with jdk
6, i would be eternally grateful :-)
regards, tom.
Heiko Braun wrote:
Something caused regression on mysql:
http://jbpm.dyndns.org:8280/hudson/job/jBPM3-Matrix/container=jboss422,da...
any ideas?
_______________________________________________
jbpm-dev mailing list
jbpm-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbpm-dev
--
regards, tom.
_______________________________________________
jbpm-dev mailing list
jbpm-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbpm-dev