Hi,
I’ll have a look into this again, since I can now use Gerrit for my tests (Back in 2015, Gerrit was broken and I could
only use Windows, so I was unable to test anything)
I think at least the following elements need to be shared:
-
Repositories for dependencies (Eclipse, Papyrus), so that Codegen and Tooling use the exact same versions
-
Common Maven plugins and versions, because we can’t mix different versions of the same Maven plugins in the
same build (That’s not an issue today as we use separate builds)
Camille
De : papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx]
De la part de Ernesto Posse
Envoyé : jeudi 7 avril 2016 21:51
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : Re: [papyrus-rt-dev] Papyrus-RT p2 Repositories
Sorry for the late response. I think some of these questions have already been clarified.
As for the reasons, first, we ended up having separate p2 repos for codegen/runtime on one hand and core/profile/tooling on the other because we have been working in two largely independent teams on these two sides and each side made their
own decisions.
As for the codegen side, I don't know exactly why we ended up with that particular structure of build/ and update/ folders. I don't know who created those top-level folders (but I did create the builds/gerrit and builds/repo folders).
I would expect that once we have a unified build we can publish to updates/nightly. Wouldn't that make sense?
As for being unable to build on Windows, that is expected because our side included the (C++) runtime, which, at least for now, only supports Linux, as that was chosen from the beginning as the first target platform for the runtime. There
is some Windows support, but I don't know how complete that is. I think the priority for 1.0 is still Linux.
On several occasions I've mentioned that we could unify the maven builds, but I won't touch the top-level pom, as I don't know what are the consequences for core/profile/tooling, and perhaps someone with more maven experience than me could
take a look at our pom(s) to see what we could refactor and move up to share, while retaining the capability to build separately.
Papyrus-RT-Master-All was designed to actually be all-in-one, but since I couldn’t get
the codegen part to compile on Windows, this has never been completed [1]
This was almost one year ago, so I guess this contribution can be abandoned now. XT-UML-RT
arrived a little bit later, so at the time, it was “All but codegen”
[1] 49755: Bug 469722: [Releng] Configure Maven build for Papyrus-RT [I7bdedf5e]
https://git.eclipse.org/r/#/c/49755/
De :
papyrus-rt-dev-bounces@xxxxxxxxxxx [mailto:papyrus-rt-dev-bounces@xxxxxxxxxxx]
De la part de Peter Cigéhn
Envoyé : jeudi 7 avril 2016 15:04
À : papyrus-rt developer discussions <papyrus-rt-dev@xxxxxxxxxxx>
Objet : Re: [papyrus-rt-dev] Papyrus-RT p2 Repositories
Welcome to the confusion! :)
I have been asking myself these questions also several times. I can try to explain my understanding of your questions. Hopefully someone
with better insight can correct if I am wrong.
On 7 April 2016 at 14:54, Christian Damus <give.a.damus@xxxxxxxxx> wrote:
Hi, Team,
I am trying to track down reliable p2 repositories for assembly of Papyrus-RT in a new Oomph setup model, and I have some questions:
-
the “Papyrus-RT-Master-All” build on Hudson produces a repository containing only the core and tooling plug-ins, not xtumlrt nor codegen. Why? That doesn’t sound like “all” of Papyrus-RT to me
The "why" part I really don't know. I guess no one has had the time to get it "all" of Papyrus-RT together in one place.
-
it appears that the only p2 repositories for the codegen and xtumlrt plug-ins are the following. Is that correct?
This repo is built by a CM tigger, i.e. it should be built triggered by pushes to master.
The same as the other one, but instead of being trigger by a push to master, it is trigger nightly (independent of if something has
been pushed or not).
As I understood it, this was planned to get in place post-0.7.2. But since we have not built anything post-0.7.2, I
guess that could explain why it is empty.
Nope, the nightly builds (triggered by pushing to master, and not trigger each night as for the code-generator/run-time) of core/profile/tooling
parts
is only available on the p2 repo on Hudson.
_______________________________________________
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
_______________________________________________
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
|
