Re: [ease-dev] modeling modules in ease

[Jonah Graham <jonah@xxxxxxxxxxxxxxxx>]

Hi Jeff,

(I have cc'ed in ease-dev so that others know what is going on here)

Thanks for that. I will try rebasing your changes on top of one or two
of mine that prepares for Neon. I will probably get to that tomorrow
or Thursday.

However, that does not resolve the bigger question that we are going
to have to resolve. That is how and if we support Mars and Neon (and
others?) going forward. Some options:

1- Combination of reflection + optional OSGi dependencies
2- Branch EASE for different major Eclipse versions
3- Drop Mars support or don't support Neon (yet)
4- Push Modelling modules to the modelling projects they are
supporting or otherwise split them out of the main EASE repos.

Obviously none of those are great solutions at the moment.
Furthermore, at least for the foreseeable future, supporting Mars and
Neon is a requirement.

My suggestion is to go with 1, using reflection and optional OSGi to
enable these modules to operate even where sysml has different names.
However, I see this as a short term solution, and hope that EASE does
not have to support every combination of every external API out there
going forward.

Thanks,
Jonah
~~~
Jonah Graham
Kichwa Coders Ltd.
www.kichwacoders.com


On 14 June 2016 at 13:18, ROLLAND, JEAN FRANCOIS
<jean-francois.rolland@xxxxxxxx> wrote:
> Hi Jonah,
> I raised a bug and committed my modifications. The build fails due to a dependence to org.eclipse.uml2.uml.
> I still can't build on my machine due to a dependency to org.eclipse.wst.jsdt.ui
> I'm trying to solve this problem.
> I removed the dependency to the sysml plugins because currently both sysml1.2 and sysml1.4 can be installed on the same platform. Anyway the impact for users is minimal.
>
> Thanks
> jeff
>
>
> -----Original Message-----
> From: Jonah Graham [mailto:jonah@xxxxxxxxxxxxxxxx]
> Sent: Monday, June 13, 2016 3:28 PM
> To: ROLLAND, JEAN FRANCOIS
> Subject: Re: modeling modules in ease
>
> Please raise a bug. If we find a dup later we'll sort it out then :-)
>
> Thanks,
> Jonah
> ~~~
> Jonah Graham
> Kichwa Coders Ltd.
> www.kichwacoders.com
>
>
> On 13 June 2016 at 12:59, ROLLAND, JEAN FRANCOIS <jean-francois.rolland@xxxxxxxx> wrote:
>> Hello Jonah,
>> We talked and we tried to compile ease modeling modules last Friday.
>> I want to push my modification on gerrit but I can’t find any bug
>> related to modeling modules.
>> Should I open a bug before pushing my modification?
>>
>> Regards
>> Jeff Rolland
>>
>> Ce message et toutes les pièces jointes (ci-après le "message") sont
>> établis à l’intention exclusive des destinataires désignés. Il
>> contient des informations confidentielles et pouvant être protégé par
>> le secret professionnel. Si vous recevez ce message par erreur, merci
>> d'en avertir immédiatement l'expéditeur et de détruire le message.
>> Toute utilisation de ce message non conforme à sa destination, toute
>> diffusion ou toute publication, totale ou partielle, est interdite,
>> sauf autorisation expresse de l’émetteur. L'internet ne garantissant
>> pas l'intégrité de ce message lors de son acheminement, Atos (et ses
>> filiales) décline(nt) toute responsabilité au titre de son contenu.
>> Bien que ce message ait fait l’objet d’un traitement anti-virus lors
>> de son envoi, l’émetteur ne peut garantir l’absence totale de
>> logiciels malveillants dans son contenu et ne pourrait être tenu pour
>> responsable des dommages engendrés par la transmission de l’un d’eux.
>>
>> This message and any attachments (the "message") are intended solely
>> for the addressee(s). It contains confidential information, that may be privileged.
>> If you receive this message in error, please notify the sender
>> immediately and delete the message. Any use of the message in
>> violation of its purpose, any dissemination or disclosure, either
>> wholly or partially is strictly prohibited, unless it has been
>> explicitly authorized by the sender. As its integrity cannot be
>> secured on the internet, Atos and its subsidiaries decline any
>> liability for the content of this message. Although the sender
>> endeavors to maintain a computer virus-free network, the sender does
>> not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.
> Ce message et toutes les pièces jointes (ci-après le "message") sont établis à l’intention exclusive des destinataires désignés. Il contient des informations confidentielles et pouvant être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de détruire le message. Toute utilisation de ce message non conforme à sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse de l’émetteur. L'internet ne garantissant pas l'intégrité de ce message lors de son acheminement, Atos (et ses filiales) décline(nt) toute responsabilité au titre de son contenu. Bien que ce message ait fait l’objet d’un traitement anti-virus lors de son envoi, l’émetteur ne peut garantir l’absence totale de logiciels malveillants dans son contenu et ne pourrait être tenu pour responsable des dommages engendrés par la transmission de l’un d’eux.
>
> This message and any attachments (the "message") are intended solely for the addressee(s). It contains confidential information, that may be privileged. If you receive this message in error, please notify the sender immediately and delete the message. Any use of the message in violation of its purpose, any dissemination or disclosure, either wholly or partially is strictly prohibited, unless it has been explicitly authorized by the sender. As its integrity cannot be secured on the internet, Atos and its subsidiaries decline any liability for the content of this message. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.