Home » Modeling » Papyrus » How to evaluate Eclipse Papyrus?
| | |
Re: How to evaluate Eclipse Papyrus? [message #485001 is a reply to message #484954] |
Thu, 10 September 2009 08:39 |
Emilien Perico Messages: 36 Registered: July 2009 |
Member |
|
|
Hi Dmitry,
Some information:
- org.eclipse.papyrus.def: compilation errors come from the xpand
templates but it doesn't affect Papyrus execution.
- org.eclipse.papyrus.diagram.statemachine: this plugin is still
experimental and contains remaining errors. I advice you to close it for
now because it's not usable yet.
- org.eclipse.papyrus.tabbedproperties.uml: this one need emf.eef plugin
but requires a specific revision of it. We plan to update
tabbedproperties plugin to work with the head of eef sources, a task is
opened for this. You can close the plugin too. You could work with
advanced properties tab to manage element properties.
You should be able to launch Papyrus in an Eclipse runtime and create
some diagrams.
Regards,
Emilien
Dmitry Semikin a écrit :
> Hi, Emilien.
>
> I would like to evaluate eclipse papyrus either. As update site still is
> not available, I've tried to build papyrus from source. I've completed
> the steps described in previous two posts (including getting source of
> ..emf.eef.runtime). But automatic build still results in multiple errors
> (1304). The most of them are in the org.eclipse.papyrus.def, but some
> are in the org.eclipse.papyrus.diagram.statemachine and
> org.eclipse.papyrus.tabbedproperties.uml I tried to run eclipse
> application configuration, but it crashes, when I just start working
> with class diagram (create class and try to do something with it - I can
> give more details, if needed).
>
> Please, tell me if I miss something in building papyrus, as I'm not too
> familiar with java development at all and for eclipse in particular.
>
> Thanks in advance.
>
> Dmitry.
>
|
|
| | |
Re: How to evaluate Eclipse Papyrus? [message #495746 is a reply to message #495424] |
Thu, 05 November 2009 21:30 |
|
Hi Werner,
There is confusion between two different tools once again : Papyrus 1,
that was developped by the CEA team and Eclipse MDT papyrus, which is a
recent component hosted by the Eclipse foundation to provide a fully
usable modeling tool including full UML and SysML implementations. This
tool merges experiences from three projects : Papyrus 1, TOPCASED UML,
and Moskitt.
This mailing list concerns the new papyrus, which is planned to be
delivered for 0.7.0 release on next Helios train.
You can find all information here : http://wiki.eclipse.org/MDT/Papyrus
regards
raphaël
Werner Keil a écrit :
> Hi,
>
> I also found Papyrus during ESE and gave it a try recently.
> We use StarUML in a very large model dominated project with significant
> BOM (UML) model size and special requirements like translating model
> items betwen languages.
>
> While some features look good even compared to StarUML, I found the
> diagram part still needs improvement (as of 1.12 version)
> StarUML has problems when items are inserted into one diagram and cannot
> automatically update others, but Papyrus I found so far completely
> unable to do this.
>
> If properties or other items are added in the model browser, no diagram
> shows them. and if you add stuff in diagram A, the browser's updated,
> but never any other diagram.
> This applies to all attributes including links or relations between
> objects.
>
> Is this a known problem, or should I file a Bugzilla issue?
>
> Thanks,
> Werner
|
|
| | | |
Re: How to evaluate Eclipse Papyrus? [message #590924 is a reply to message #484954] |
Thu, 10 September 2009 08:39 |
Emilien Perico Messages: 36 Registered: July 2009 |
Member |
|
|
Hi Dmitry,
Some information:
- org.eclipse.papyrus.def: compilation errors come from the xpand
templates but it doesn't affect Papyrus execution.
- org.eclipse.papyrus.diagram.statemachine: this plugin is still
experimental and contains remaining errors. I advice you to close it for
now because it's not usable yet.
- org.eclipse.papyrus.tabbedproperties.uml: this one need emf.eef plugin
but requires a specific revision of it. We plan to update
tabbedproperties plugin to work with the head of eef sources, a task is
opened for this. You can close the plugin too. You could work with
advanced properties tab to manage element properties.
You should be able to launch Papyrus in an Eclipse runtime and create
some diagrams.
Regards,
Emilien
Dmitry Semikin a écrit :
> Hi, Emilien.
>
> I would like to evaluate eclipse papyrus either. As update site still is
> not available, I've tried to build papyrus from source. I've completed
> the steps described in previous two posts (including getting source of
> ..emf.eef.runtime). But automatic build still results in multiple errors
> (1304). The most of them are in the org.eclipse.papyrus.def, but some
> are in the org.eclipse.papyrus.diagram.statemachine and
> org.eclipse.papyrus.tabbedproperties.uml I tried to run eclipse
> application configuration, but it crashes, when I just start working
> with class diagram (create class and try to do something with it - I can
> give more details, if needed).
>
> Please, tell me if I miss something in building papyrus, as I'm not too
> familiar with java development at all and for eclipse in particular.
>
> Thanks in advance.
>
> Dmitry.
>
|
|
| | |
Re: How to evaluate Eclipse Papyrus? [message #594958 is a reply to message #495424] |
Thu, 05 November 2009 21:30 |
|
Hi Werner,
There is confusion between two different tools once again : Papyrus 1,
that was developped by the CEA team and Eclipse MDT papyrus, which is a
recent component hosted by the Eclipse foundation to provide a fully
usable modeling tool including full UML and SysML implementations. This
tool merges experiences from three projects : Papyrus 1, TOPCASED UML,
and Moskitt.
This mailing list concerns the new papyrus, which is planned to be
delivered for 0.7.0 release on next Helios train.
You can find all information here : http://wiki.eclipse.org/MDT/Papyrus
regards
raphaël
Werner Keil a écrit :
> Hi,
>
> I also found Papyrus during ESE and gave it a try recently.
> We use StarUML in a very large model dominated project with significant
> BOM (UML) model size and special requirements like translating model
> items betwen languages.
>
> While some features look good even compared to StarUML, I found the
> diagram part still needs improvement (as of 1.12 version)
> StarUML has problems when items are inserted into one diagram and cannot
> automatically update others, but Papyrus I found so far completely
> unable to do this.
>
> If properties or other items are added in the model browser, no diagram
> shows them. and if you add stuff in diagram A, the browser's updated,
> but never any other diagram.
> This applies to all attributes including links or relations between
> objects.
>
> Is this a known problem, or should I file a Bugzilla issue?
>
> Thanks,
> Werner
|
|
| |
Goto Forum:
Current Time: Fri Sep 27 03:06:27 GMT 2024
Powered by FUDForum. Page generated in 0.05355 seconds
|