| Re: [mdt-papyrus.dev] Broken test builds |
|
Hi all, More precisions about this build refactoring. The idea is to provide a main pom (Which we currently don’t have) to build all components of Papyrus at the same time (Especially useful for Gerrit and Sonar) However, we made several bad choices in the current build implementation, which means that simply adding a top-level pom is not sufficient. An important build refactoring is required -
Top poms will be moved to a different location (Because we can’t have several Poms in the same folder) -
Top poms will be renamed (Because they all had the same artifact ID) -
Shared artifacts (Especially the test framework) will have to be built/deployed separately Additionally, some changes are required in the test framework, to be able to run tests for each test plug-in separately. We also need to distinguish plug-ins which provide helpers for the tests (diagram.tests,
junit.framework, ...), and actual test plug-ins These changes will be more disruptive than I expected, so i’d like to push them on both Mars maintenance and Neon, to keep builds and Hudson jobs as consistent as possible between branches. Feature branches and
existing Gerrit contributions affecting POMs/Releng will need to be updated accordingly. The mars-maintenance branch will be created when this refactoring is complete (Soon after, but we still need to clarify the next steps) Regards, Camille De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx]
De la part de LETAVERNIER Camille Hi all,
I will fix this, along with a general build refactoring/improvement, but it might take a few hours Sorry for the inconvenience, Camille |