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,
Camille
Hello team,
It is required to simplify the herarchy of
the project to make it align with the maven purpose. [1]
In this goal, I think to move the "codegen" folder one
level up, as the sibling of the releng folder.
Why such a decision? Because the codegen is not built into the
releng/pom.xml anymore, and the codegen has now it's own
Target platform to be run separately though the Hudson Job.
Thus, I would like to have your opinion for this modification
as I'm not used to work with the "codegen" of this project.
![]()
[1] -
https://bugs.eclipse.org/bugs/show_bug.cgi?id=493864
--
|
Céline
JANSSENS
Software
Engineer
+33 (0)2 44 47 23 23
|
|
Mail
:
cej@xxxxxxxxxxx
|
6
rue Léonard De Vinci - BP 0119 - 53001
LAVAL Cedex - FRANCE
www.all4tec.net
|
|