[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [mdt-papyrus.dev] [papyrus-ic] [PMC] Problem with maintenance and product line
|
Hi,
You also can consider contribute your extension to Papyrus itself in order to enable all other Papyrus extensions (including Papyrus-RT) to benefit its usage?
I also add the Papyrus dev list that may be concerned by the subject of the discussion
My two cents,
Sébastien.
Sébastien Gérard
Head of the LISE labs
CEA Research Director
Papyrus project Leader (www.eclipse.org/papyrus)
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
sebastien.gerard@xxxxxx www-list.cea.fr
-----Message d'origine-----
De : papyrus-ic-bounces@xxxxxxxxxxx [mailto:papyrus-ic-bounces@xxxxxxxxxxx] De la part de hili
Envoyé : jeudi 22 février 2018 09:43
À : papyrus-ic@xxxxxxxxxxx
Objet : Re: [papyrus-ic] [PMC] Problem with maintenance and product line
Hi all,
Actually, the action language is so far a pure addition but the code snippet view has been forked to support it. To seamlessly integrate it to Papyrus-RT, it would be better to support the definition of target language/action languages in a more generic way using the existing code snippet view which implies modifying the source code of Papyrus-RT.
As for the observer/gateway, this is a simple extension. For both the action language and the observer, these are extensions baed on the 1.0 RCP so far.
Nicolas
On 22.02.2018 00:41, Juergen Dingel wrote:
> Thanks, Ernesto. This does help. The action language is a pure
> addition, I think, as is the observer/gateway.
> However, the MQTT support and the support for (the generation of)
> distributed applications are not conservative and sure modify the
> RTS.
>
> Juergen
>
> On 2/21/2018 1:33 PM, Ernesto Posse wrote:
>
>> Hi Juergen.
>>
>> Are these extensions based on the 1.0 RCP or on some more recent
>> nightly build? And by "extensions" do you mean plugins that modify
>> the Papyrus-RT source code, or only add new plugins (that do not
>> modify the source code)? If they are based on the 1.0 RCP and are
>> only additions, you shouldn't be blocked: you can always make plugins
>> that extend a stable version (e.g. the 1.0 RCP), independently of the
>> status of the nightly builds. On the other hand, if your extensions
>> are actually modifying Papyrus-RT code, then yes, this would be a
>> bigger problem and you could not use the existing maven/tycho.
>>
>> The build issue only affects Papyrus-RT developers and developers of
>> extensions of Papyrus-RT (as in extensions that modify the -RT
>> sources) and which either try to setup their development environment
>> using the Oomph setup model, and those who try to use maven/tycho for
>> building the product, which is what you would do if you are modifying
>> the Papyrus-RT sources.
>>
>> In any case, I'm working on getting the build up again, but it is
>> time-consuming. I'm making progress, but I don't know when it will be
>> done.
>>
>> --
>> Ernesto Posse
>> Zeligsoft (2009) Ltd.
>>
>> On Feb 21, 2018, at 1:14 PM, Juergen Dingel <dingel@xxxxxxxxxxxxx>
>> wrote:
>>
>> Charles,
>>
>> thank you very much for looking into this.
>>
>> We have several significant extensions of Papyrus-RT (e.g., dedicated
>> action language with full smart editor support, a gateway/observer
>> service/capsule, and an MQTT extension for IoT applications) in the
>> pipeline that are difficult to make public at the moment due to the
>> broken build.
>>
>> Juergen
>>
>> On 2/20/2018 4:46 PM, charles+zeligsoft.com [2] wrote:
>> 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 [3] 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 [1]
>>
>> _______________________________________________
>> 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 [1]
>
> _______________________________________________
> 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 [1]
>
>
>
> Links:
> ------
> [1] https://dev.eclipse.org/mailman/listinfo/papyrus-ic
> [2] http://zeligsoft.com
> [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=531432
>
> _______________________________________________
> 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
_______________________________________________
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
