We (Quentin in cc and I thank him for the time spent on that) did some investigation on our side, here is the answer of Quentin:
“
Hi Séb,
This seems strange to me that a dependency to Photon plugins has been found inside the maintenance branch as, illustrated by the attached documents, there should not be any such dependencies on the Oxygen branch.
I would assume, judging from the pointed trace of the Master-core job, that Papyrus-RT team are mixing dependencies in their target platforms as they are depending on the Oxygen release and the Master-developper (which is Photon).
The issue they might be encountering is that the junit test framework is not yet released with Papyrus and therefore they are depending on released plugins but also on nightly ones.
Anyhow I do fail to understand why the oxygen-developer reference has been removed from the papyrurelease/**core.target as this does not seem to break my local build which resolves fine with it (in fact it breaks with the provided error when it is removed). I tried to be as close to the job configuration as I could decipher from the trace, i.e. mvn clean install –Dpapyrus.kind=papyrusrelease –Dtarget.kind=core –Pcore.
There is a task on my todo list for a release of the junit framework at the same time of the main one, as well as an integration of API tools to the build process that should prevent any kind of mishap like the one mentioned from happening.
Regards
Quentin
“
About the last comment of Quentin, any help and contribution are welcome.
Thanks,
Best,
Sébastien.
| |
<image001.png> | | | Sébastien Gérard Head of the LISE labs CEA Research Director <image002.jpg> Commissariat à l’énergie atomique et aux énergies alternatives Institut List | CEA Saclay Nano-INNOV | Bât. 862- PC174 F-91191 Gif-sur-Yvette Cedex M. +33 6 88 20 00 47 T. +33 1 69 08 58 24 |
| | | | <image004.png> <image005.jpg> |
| | | | | |
Charles,
thanks for looking into this. It is indeed an unfortunate situation...
Juergen
This is in relation to
It appears that a back port from Photon to the Papyrus 3.0 maintenance stream has dependencies on Photon (4.0) bundles… and the use of a unit test component has results in problems for Papyrus-RT (go read bug 531432 for more information). The result is that it is no longer possible to build Papyrus-RT, which means that we cannot provide fixes. This has the side effect (reported by one user thus far) that it is no longer possible to install the Papyrus-RT development environment by following the instructions in the wiki. This means that currently, Papyrus-RT cannot be used as a base for further customization, as indicated by an affected external user (who may not be a user for long…).
This is an example of a “very bad thing” that could easily be called a lack of “industrialness” in Papyrus and our approach. I am hopeful that it is not worse and not a manifestation of siloed thinking by our teams.
I do understand that, this particular problem has been going on for some time and that it has been discussed already. This should make finding a solution.
We now have a risk identified, let's work at establishing governance for this risk and implement compliance checks.
This needs to be addressed in the context of the joint PMC-Arch efforts on delivery governance and quality.
We were lucky in that this does not seem to have affected many users. We may not be as lucky next time…
If the Papyrus IC (and Papyrus product line) wants to be taken seriously, it can never happen again!
I would like to invite anyone interested in the Papyrus IC product line Delivery Governance, including the Quality Framework & Testing to contact either the Architecture Committee lead (Rémi Schnekenburger) or myself (for the Product Management Committee).
Regards / cordialement,
Charles Rivet
Senior Product Manager / directeur principal de produits - Zeligsoft
Chairman, Papyrus IC Product Management Committee / président du comité de gestion de produits du consortium industriel de Papyrus
charles@xxxxxxxxxxxxx
_______________________________________________
papyrus-ic mailing list
papyrus-ic@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-ic
