The reason I ask is that it might be better to point the
non-hibernate-java8 modules to use the Java 6 javac when this JDK6_HOME is
set. So...
1) Running Gradle with Java 8, JDK6_HOME set -> we'd compile all the
non-hibernate-java8 modules setting
JavaCompile#options#forkOptions#executable to the
Does Eclipse have the ability, like IntelliJ does, to define a different
JDK for each module in a multi-module project?
On Sat, Mar 28, 2015 at 2:10 PM, Steve Ebersole wrote:
> Gradle really is quite elegant in most cases:
>
> if ( project.name != 'hibernate-java8' && rootProject.hasProperty(
>
Gradle really is quite elegant in most cases:
if ( project.name != 'hibernate-java8' && rootProject.hasProperty(
"JDK6_HOME" ) ) {
final File java6Home = new File( rootProject.property( "JDK6_HOME" ) as
String );
final org.gradle.internal.jvm.Jvm java6Jdk =
org.gradle.internal.jvm.Jvm.forHome( jav
On Sat, Mar 28, 2015 at 11:26 AM, Sanne Grinovero
wrote:
>
> Consider also that since we now have N slaves, there is no guarantee
> that a second job will run on the same build slave.
> So if the JDK8 build produces artifacts but only deployes them in the
> local repository, the second node might
On 27 March 2015 at 22:25, Steve Ebersole wrote:
> We should remove that -XX:MaxPermSize=512m setting as we discussed before.
I've changed this to:
-server -Xmx2G -Xms800M -Djava.net.preferIPv4Stack=true
-Djgroups.bind_addr=127.0.0.1 -XX:+PrintTenuringDistribution
-XX:+PrintGCDetails -Xloggc:/ho
We should remove that -XX:MaxPermSize=512m setting as we discussed before.
I understand all of that. I still think its probably worthwhile to look at
minimizing the amount of time and resources. For a couple of reasons.
First I am doing a lot of dev right now. In the 40-50 minutes it takes to
r
Hi Steve,
don't worry for the resources they consume. Each build job which we
run is fully isolated and running on independent hardware, so it's not
going to slow down any other build.
Since we now have a set of small servers, one each dedicated for a job
at a time, I've opted for low spec machine
I was curious why it took so long to run the master ORM jobs on the CI
machine compared to running the job locally. Locally I run `clean test` at
the root prject quite often and it takes roughly 9-10 minutes. The master
CI jobs generally take 45-50 minutes to complete.
So I enabled "Gradle build
