We have seen similar behavior like described in the following maven-compiler bug during the build-process of our tycho-maven rcp build.
https://issues.apache.org/jira/browse/MNG-5523 (just
think of it as a maven-tycho-project)
The default of tycho-maven is to build incrementally. So while this seems to be broken I wanted to evaluate the takari-incremental-compiler as
workaround.
Since this would not work as you said, I tested the alternative I mentioned before.
https://maven-incremental-build.java.net/site/usage.html
But this plugin doesn’t seem to like pomless tycho-maven builds, as it always detects it as changed pom. Have to inspect this in more detail.
So what is your suggestion on problems like described in MNG-5523 ? Always perform a clean before the actual goal?
Best regards
Ahmet Bilgin
Von: tycho-user-bounces@xxxxxxxxxxx [mailto:tycho-user-bounces@xxxxxxxxxxx]
Im Auftrag von Igor Fedorenko
Gesendet: Mittwoch, 10. August 2016 12:14
An: tycho-user@xxxxxxxxxxx
Betreff: Re: [tycho-user] Using Takari inkremental compiler with tycho
Not possible at the moment. Tycho projects use/require OSGi compilation classpath, and Takari only supports Maven.
Somebody will need to integrate Tycho and Takari incremental build tech, but this isn't trivial. I am also not sure how much you will gain from incremental compilation. You need to have really huge codebase and an "interesting" development
workflow to see the difference.
On Wed, Aug 10, 2016, at 04:42 AM, Ahmet Bilgin wrote:
Hello,
My company is using maven 3.3.9 and tycho 0.25.0 to build an eclipse rcp application and we wanted to try out the
Takari incremental compiler since incremental building seems to be broken in maven and in tycho.
It can be configured like described here
http://takari.io/2014/10/16/incremental-compilation.html#trying-takari-incremental-java-compiler.
In order to use the takari-compiler correctly, the tycho-compiler has to disabled/skipped, but the tycho-compiler
does not allow to be skipped.
The result is that both takari and tycho compilers are run.
There seems to be an alternative maven-plugin which just detects changes in an module and clears the target directory
previous to the compilation phase. So the module gets recompiled during compilation. This would be a less invasive workaround.
See
https://maven-incremental-build.java.net/site/usage.html
Do you have any suggestions for proper incremental build support?
Best regards
Ahmet Bilgin
MAGMA Gießereitechnologie Gesellschaft für Gießerei-, Simulations- und Regeltechnik mbH | Kackertstr. 11, 52072 Aachen, Germany | Rechtsform GmbH, Amtsgericht Aachen HRB 3912,
UST-ID-Nr. DE121745780 | Geschäftsführung: Dr. Marc C. Schneider (Vorsitzender), Dr.-Ing. Jörg C. Sturm
_______________________________________________
To change your delivery options, retrieve your password, or unsubscribe from this list, visit