Re: [incquery-dev] Headless building issues

[Ujhelyi Zoltán <ujhelyiz@xxxxxxxxxxxxxxxx>]

Hi,

> On 28 Sep 2015, at 11:19, István Ráth <rath@xxxxxxxxxx> wrote:
> 
>> > - 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.
> As I understand, you suggest that the issue is completely independent of our codebase, and should occur in other Maven-Tycho scenarios. Has anyone at Eclipse encountered something similar in the past?
Generally, combining Maven/Java and Maven/Tycho in the same project is largely undocumented. Each time an issue occurs, it requires extensive googling/experimenting. Most eclipse projects have no dedicated maven compiler, or are using various hacks to support it (e.g. Xtext merges several dependency jars into a single “uberjar” using file system operations, and manually copies it to the maven repository folder).

We are trying to minimize the effects by limiting the number of modules that have to combine both approaches; in our case it is the maven compiler, and the two helper modules that were changed in the commit mentioned in the thread.

>> > - 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
> Is there a conceptual issue or just a lack of time?
A bit of both. The documentation is a bit lacking, so I don’t know whether I have misconfigured something in the toolchains.xml file, or the jenkins/slave setup is the root of the problem.

Cheers,
Zoli
-- Zoltán Ujhelyi

Technology Expert
IncQueryLabs Ltd.