Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[mdt-papyrus.dev] Maven build compiler improvement

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/


Back to the top