Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [incquery-dev] Headless building issues

Hi,

> - is this issue connected to our incquery-maven-compiler in any way? (You mention it but all entries in the commit are referring pom.xml files…)
Directly not, but indirectly yes. The incquery-maven-compiler failed in my machine with a strange class signing exception, and its debugging lead me to the issue itself.

> - exactly what issue has been solved by your changes?
I could compile IncQuery codebase with my changes; and the results should be deterministic, as the dependency conflicts have been removed entirely.

> - what do you mean by “used on Hudson by default”? 
The eclipse.org hudson instance used Maven 3.0.5 (I guess, that was the default version used there). There were other versions as well, I switched to a 3.1.1 one for the build job to work.

> - can the idiosyncratic behavior (Java version vs JVM) of the Xtend builder be worked around somehow? (or better yet, reported to them via bugzilla?)
They are reported (e.g. https://bugs.eclipse.org/bugs/show_bug.cgi?id=438764), and they should work when Maven toolchains were set up correctly, but I did not manage to do that on our build server. Xtext 2.8 managed to improve on this behaviour for the IDE (https://eclipse.org/xtend/releasenotes.html#/releasenotes/2015/03/11/version-2-8-0), but I am not sure it works from Maven as well. Did not have the time to test it correctly, but we had an issue about two week ago that suggest it is not that simple.

> - shouldn't this Maven dependency be mentioned in our developer documentation somewhere?
Good point. I was too tired on Friday to do that, but it should be noted.

Cheers,
Zoli
-- Zoltán Ujhelyi

Technology Expert
IncQueryLabs Ltd.

Back to the top