| Re: [papyrus-rt-dev] [Codegen] Move the folder one level up |
|
Hi, Codegen and Papyrus-RT should still be unified with a Common parent [1]. The reason is that they share a lot of common
things: -
Some common dependencies (At least between the Papyrus-RT profile and the Codegen plug-ins). A common “abstract”
TP is required to ensure that we don’t introduce any version conflict (It is even more important, as Papyrus-RT is not in the release train, so it doesn’t benefit from the strict validation of versions compatibility) -
It is possible to use several Target Platforms in a single build. Papyrus uses 5 different TPs referencing each
other, and still has a parent POM which can be built in one pass. There are also a few other points to take into account: -
Having a different layout for Codegen compared to other Features doesn’t seem a good idea. If you want to enforce
conventions, then they need to be consistent. Also, be careful about Maven conventions; you’ll often find out that they are contradicting Eclipse and/or OSGI conventions -
Changing the conventions for a specific project is not a decision to be taken lightly. Changing the file structure
will make it very difficult for Git/EGit/Gerrit to work properly [1] 70225: Bug 469722: [Releng] Configure Maven build for Papyrus-RT https://git.eclipse.org/r/#/c/70225/ Regards, De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx]
De la part de Céline JANSSENS Hello team, It is required to simplify the herarchy of the project to make it align with the maven purpose. [1]
[1] -
https://bugs.eclipse.org/bugs/show_bug.cgi?id=493864 --
| |||||||||
