Home/ Questions/Q 8661479
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-12T16:30:27+00:00

We use Java within our build process, as it is used to resolve/publish our

  • 0

We use Java within our build process, as it is used to resolve/publish our dependencies via Ivy.

No problem, nor have we had with it for 2 years, until we’ve tried to upgrade Java 6 Update 26 to Version 7 Update 7, whereas a build on a local developer PC (WinXP) now takes 2 hours to complete, instead of 10 minutes!!

Nothing else has changed on the PC, making it the absolute target for our concerns.

Does anyone know of any reason as to why version 7 of Java would make such a speed difference like this?

UPDATE: The build process is NAnt-based, so Java.exe is called from a NAnt script, running in a Command (DOS) window.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    In my experience, Java 7 was a huge step backward in terms of speed and compatibility. I’ve found it slower not only to compile, but running the JRE as well.

    I’ve also had major issues running eclipse with it (and yes, i’ve used update 7).

    And from my standpoint there’s nothing in Java 7 that i need. I like the ForkJoinPool, and can get that as an add on library for Java 6.

    Maybe Java 8 will be better.

    • 0