Hi, Ernesto,
That’s a good point. We should also clone the codegen Gerrit job for the Neon branch.
Céline, Rémi, could one of you do that before we merge my change into the Neon branch? It would be nice to ensure that this change is sound within itself before proceeding.
On 5 April, 2016 at 11:52:23, Ernesto Posse (eposse@xxxxxxxxxxxxx) wrote:
Hi Christian.
I was not aware of change-set 69349.
Thanks for doing that. I'll
take a look, but I don't expect it to need any additional changes,
at least at this point.
One
thing though: I noticed that change-set is being built with the
Hudson PapyrusRT-Gerrit-for-Neon job,
which builds with the top-level releng/pom.xml, but the codegen pom
(releng/codegen/pom.xml) is not (yet) a submodule of that one, so
in your Hudson job, codegen is not being built.
We have discussed with Remi in the past the possibility of
unifying the poms, (perhaps refactoring some common elements
between the top pom and the codegen pom). I don't know if we should
do that now with the Neon build or not. But if/when we do it, I
think it would be a good idea structure the poms so that we retain
the capability to build codegen and tooling separately.
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev
|