Re: [mdt-papyrus.dev] Maven build compiler improvement

[LETAVERNIER Camille <Camille.LETAVERNIER@xxxxxx>]

I agree on using JDT preferences in the Tycho build

 

I’ve noticed that having JDT/PDE, Buckminster and Tycho builds typically gives 3 different results for compile & tests. Sometimes it helps detecting bugs another build would miss. (Un)fortunately, we’re getting rid of the Buckminster build really soon now.

 

Regarding the Maven builder, I’m not sure it would scale right now, so let’s keep that in mind for later, but it’s too soon to implement it.

 

Camille

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Christian W. Damus
Envoyé : mercredi 11 février 2015 15:35
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Maven build compiler improvement

 

Thanks, Benoit.

 

My goal with this exercise is to try to make the Tycho build as much like the build in our developer workbenches as possible, not the other way around.  I have so many Papyrus projects in my workspace that I’m afraid if they all switched over to m2e build it just wouldn’t scale and my productivity would suffer from waiting for Eclipse at every turn.

 

Cheers,

 

Christian

 

 

On Wed, Feb 11, 2015 at 9:25 AM, MAGGI Benoit <Benoit.MAGGI@xxxxxx> wrote:

Hi everyone,

 

Christian made a very interesting proposition to improve the configuration of the compiler

used by the integration (maven-tycho-hudson)

 

See : [1] and [2]

ð  Some misconfigurations have already been detected

 

The main purpose it to replace

                                                           <groupId>org.eclipse.tycho</groupId>

                                                           <artifactId>tycho-compiler-plugin</artifactId>

                                                           <version>${tycho-version}</version>

                                                           <configuration>

                                                                          <source>${java.source.version}</source>

                                                                          <target>${java.target.version}</target>

                                                                          <optimize>true</optimize>

                                                                          <showWarnings>true</showWarnings>

                                                           </configuration>

By

               <plugin>

                              <groupId>org.eclipse.tycho</groupId>

                              <artifactId>tycho-compiler-plugin</artifactId>

                              <version>${tycho-version}</version>

                                             <configuration>

                                                                          <optimize>true</optimize>

                                                                          <showWarnings>true</showWarnings>

                    <!-- Tycho build using the project's JDT settings. -->

                    <useProjectSettings>true</useProjectSettings>

                                                           </configuration>

                                            </plugin>

 

ð  It will ensure that the integration use the same parameters as the developers but will allow different build configuration for each plugin.

If we agree on that, the best would be to promote the behavior to each top-pom-*

(We can also create a real unique top configuration that should be inherited by all configurations)

 

The other solution would be to add/use the maven nature to each plugin

ð  It will also ensure the same compilation between the integration and the developer.

 

Any thoughts about that?

 

Regards,

Benoit Maggi

 

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=459566

[2] https://git.eclipse.org/r/#/c/41536/