Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Collaborative-Modeling Target Platform
Thanks, Camille.  I didn’t realize that there was a separate TP for Compare.  And thanks, Benoit for pointing out that the TP so far had only one SysML bundle:  I’ve updated the tests TP to pull the whole SysML 1.4 feature because we need also the customization artifacts in the diagram bundles for these tests.

I see also that there doesn’t seem to be any location on the download server for publication of nightly nor milestone builds for the Papyrus Components as there is for the main Papyrus project.  Is there a plan to implement at least milestone builds for the Components?  It would be a much more stable situation for downstream builds like Compare to have static update sites available instead of the highly volatile Hudson builds.

Thanks,

Christian

On Nov 17, 2017, 02:49 -0500, Camille Letavernier <cletavernier@xxxxxxxxxxxxxxxxx>, wrote:
Hi Christian,

The trick with Papyrus Compare is that it no longer uses Collaborative Modeling's build or target platform, but rather its own. It's still embedded in the Collaborative Modeling build however.

The actual target platforms for Papyrus Compare are located under plugins/compare/targetplatforms. You can also check the build locally by building Papyrus Compare only via:

cd plugins/compare
mvn verify

or

mvn verify -Dtarget.stream=nightly

The first one will build against a more stable set of dependencies (I won't call it release, as it includes an integration build for EMF Compare), whereas the second one will build against nightlies. If you only need to add a dependency for your tests, then it should be sufficient to modify compare.tests-nightly and compare.tests-release (Both need to work, but the Collaborative Modeling Gerrit job is currently configured to build the Nightly stream)

You may find some more info on the new wiki page for Papyrus Compare [1]


HTH,
Camille



On Thu, Nov 16, 2017 at 8:44 PM, Christian W. Damus <give.a.damus@xxxxxxxxx> wrote:
Thanks for the replies.

I don't know why some of the tests previously used the SysML component’s profile, but it is particularly useful for my case because it includes diagram definitions, CSS, and more customizations that are integrated via the architecture framework.  If there are more suitable implementors of such integrations, I’ll be happy to look at them.

Anyways, I’ll try updating the target definition and let the code reviewers sort it out in Gerrit if that’s a problem.  I am concerned about using nightly builds (perhaps there is a stable milestone available?) but that’s something the Papyrus projects have regularly done before.

Thanks again!

Christian

On Nov 16, 2017, 10:25 -0500, MAGGI Benoit <Benoit.MAGGI@xxxxxx>, wrote:

Hi Christian,

 

In short :

-        The target platform only import the sysml14.profile plugin [1]

-        You add a dependency to sysml14.architecture which is unknown to the target platform [2]

ð  Exception! Add the SysML 1.4 Feature to the target platform and it will fix your problem.

 

More on that (IMHO):

-        Alll components should use tpd only on latest released version

-        Developer tooling should be moved in SDK feature (Removing dependency to hudson update site)

-        Collaborative shouldn’t depend from SysML 1.4 (From what I see, it’s for testing purposes. If possible use the UML standard profile that is provided by Papyrus core and UML Project)

 

Regards,

Benoit

 

1 : https://git.eclipse.org/c/papyrus/org.eclipse.papyrus-collaborativemodeling.git/tree/releng/targetplatforms/org.eclipse.papyrus.collaborativemodeling.targetplatform/org.eclipse.papyrus.collaborativemodeling.targetplatform.tpd

2 : https://git.eclipse.org/r/#/c/111656/3/plugins/compare/tests/org.eclipse.papyrus.compare.diagram.tests/META-INF/MANIFEST.MF

 

 

De : mdt-papyrus.dev-bounces@eclipse.org [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de LE MENEZ Quentin
Envoyé : jeudi 16 novembre 2017 15:50
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [PROVENANCE INTERNET] Re: [mdt-papyrus.dev] Collaborative-Modeling Target Platform

 

Hi Christian,

 

From what I can see the target used for the builds is the main one (under releng/targetplatforms) that includes the released [1] version of sysml14 on a lazy basis hence the latest oxygen’s 1.0.0. There is a parameter for the nightly of compare main and tests, that do require sysml14, but even they point to the released version of sysml14 from what I can see.

If all that is needed is to point to the nightly of sysml14 that could be possible by modifying the **.tpd. A little warning though, those are just here to ease the creation/visualization of the target files so those would have to be recalculated as well using Mikael’s tool [2].

As for the question about the particular platform needed to be followed by compare, I will let Camille or Philip answer. J

 

I could not reproduce the problem locally but I will try to build the repo on a linux VM  and clean m2t o see if it changes anything.

 

HTH,

Quentin

 

[1] http://download.eclipse.org/modeling/mdt/papyrus/components/sysml14

[2] https://github.com/mbarbero/fr.obeo.releng.targetplatform

 

 

De : mdt-papyrus.dev-bounces@eclipse.org [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Christian W. Damus
Envoyé : jeudi 16 novembre 2017 14:03
À : Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
Objet : [mdt-papyrus.dev] Collaborative-Modeling Target Platform

 

Hi, Team,

 

What is the target platform of the Collaboration Modeling builds (specifically, Papyrus Compare) supposed to be?  I have a Gerrit patch that is failing [1] because it is doesn’t find the Architecture Definition bundles from SysML14 version 1.1.  Is the TP not supposed to be at least Oxygen for nightly builds in the Photon development stream?

 

Perhaps it’s just a matter of updating the target definition to take another SysML build, which is only a test dependency, anyways.  Would it be okay if I did that?  I ask the more general question because this problem reminds me that I don't know how the TP is intended to be maintained, what platform versions this (sub-)project wants to support, and how that may all be different to what EMF Compare is doing (and formerly did with these plug-ins).


_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev



--
Camille Letavernier

Senior Software Engineer
EclipseSource France

Phone: +33 1 85 41 09 21

EclipseSource France SAS
Palaiseau-Entreprises
7 rue de la Croix Martre
91120 Palaiseau

General Manager: Remi Schnekenburger
Registered Office: 7 rue de la Croix Martre, 91120 Palaiseau, France
Commercial Register 824 977 516  R.C.S. EVRY
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

Back to the top