Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [papyrus-sysml-users] Development setup

Hi Klaas,


Here are some basics information :

Check your installation by a basic checkout, compilation

·        Clone the sysml 14 git repository git clone

·        Run maven at the root of the repo: mvn clean install; it should pass

·        Get sysml14 plugins in your eclipse (papyrus) workspace (You require an Eclipse Mars with papyrus installation)

·        Et “Voila” you are good to go.

You can check the website [1] and the pdf [2] to have more information.

(Both are nightly build, under construction documentation)


Example of a minimal iteration: from bug, to requirement, to code integration through gerrit review.

·        Describe in Bugzilla the bug, feature you are working on. Please use the component SysML. And begins with [SysML 1.4] for Summary.

·        Get the code from the master with git,git clone, and work on a local branch,

·        Add the new requirement in the different sysml 1.1 models located in the doc folder of the relevant plugin. have a look to SOP4: Requirement

·        Modify the code

·        Push on Gerrit ssh://{ECLISPEUSERLOGIN}

·        Ask for a review

·        After a few iteration, you code should be merged and accessible in the master.

Feel free to make returns so we can improve the process and the documentation.



Benoit MAGGI


1 :

2 :



De : papyrus-sysml-users-bounces@xxxxxxxxxxx [mailto:papyrus-sysml-users-bounces@xxxxxxxxxxx] De la part de Klaas Gadeyne
Envoyé : mercredi 23 septembre 2015 16:39
À : papyrus-sysml-users@xxxxxxxxxxx
Objet : [papyrus-sysml-users] Development setup


(maybe a little off topic for the sysml-users mailinglist, but there's not devel yet :-)




What would be the recommended (=fast and easy) way to have a development environment for papyrus-sysml based on mars?

- Install eclipse-mars with papyrus-sdk and import the plugins from the (clone of the) papyrus-sysml git repository?

- Oomph?

- ...


Are there any gotcha's to take into account?


Secondly, is there any documentation yet on (parts of) the workflow?


For instance, suppose I would like to work on/think about Small square box notation for an internal property

A value property may optionally be shown by a small square box, with the name and other specifications appearing in a text string close to the square box. The text string for such a value property may include all the elements that could ordinarily be used to declare the property in a compartment of a block, including an optional default value. The box may optionally be shown with one edge flush with the boundary of a containing property. Placement of property boxes is purely for notational convenience, for example to enable simpler connection from the outside, and has no semantic significance. If a connector is drawn to a region where an internal property box is shown flush with the boundary of a containing property, the connector is always assumed to connect to the innermost property.


It seems like the first step I would have to perform would  be to add a requirement to 



Is there any documentation on that flow yet?





Back to the top