On HIPP we do not even define a default Java so that projects will have
to explicitly set it. I think for a build to be reproducible a project
should never depend on the default Java and instead explicitly set the
Java version they are targeting.
The problem with defaults is when they suddenly
Ed : No, this was seen directly on build.eclipse.org, and our failing
build (ecoretools) is not on an HIPP (as far as I know since I am not
the main releng there).
Dennis : M4 is the first time we see this failure, and we had never
changed the default VM before.
The default alternative (I'm
Hi all,
I had the same problem with build.eclipse.org last week.
After trying around with combination of different processors and ant versions
I gave up and switched to the /usr/lib64/jvm/java-1_6_0-ibm-1.6.0
We really need a better JVM default, for HIPPs and build.eclipse.org.
Best regards,
Denni
Hi Laurent
A long time ago GNU Java was the almost unuseable
default for vanilla Unix systems.
Have you perhaps just switched to a
new unconfigured platform such as a HIPP where the defaults are
different?
Regards
Ed Willink
On 17.12.2013 10:33, Laurent
Goubet wrote:
> Hi,
>
> Wit
Hi,
With Luna M4, we've begun to see "strange" failures in our ant promoters :
javax.xml.transform.TransformerConfigurationException: no
xsl:version attribute on literal result node
This happened for us on the ant promoters for EMF Compare and Acceleo,
and we also had a random failure on
