Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Papyrus-RT/Releases/Oxygen v1.0 Release Notes"
(→Notes, Tips, and Warnings: Reordered entries from most to less critical, added "snap to grid" new defaults) |
(→Warnings, Notes, and Tips: Added architectural context release note) |
||
Line 47: | Line 47: | ||
{{warning |Path Names| The long-standing pathname issue when installing in deeply nested directories in Windows appears to still be an issue with the Windows installation. If you get errors extracting the RCP archive or running Papyrus-RT, consider either installing in a directory closer to the root of your system or using a recent archive tool such as 7-zip. }} | {{warning |Path Names| The long-standing pathname issue when installing in deeply nested directories in Windows appears to still be an issue with the Windows installation. If you get errors extracting the RCP archive or running Papyrus-RT, consider either installing in a directory closer to the root of your system or using a recent archive tool such as 7-zip. }} | ||
+ | |||
+ | {{warning | UML-RT Architectural Context | Papyrus 3.0 (Oxygen) brings the concept of architectural context to projects and models. When creating Papyrus-RT projects, please make sure you selet the ''“UML-RT”’ architectural context so your projects and models are properly configured. }} | ||
{{note |Beta Features| I guess we didn't hide this well at ll ;-)... There are two features available in Papyrus-RT 1.0 under an early availability ''"Beta"'' approach so that we get feedback from our users on their capabilities: RSA Import and Textual modeling. If you use either of those features, we would appreciate your feedback! But remember: '''use at your own risk!'''}} | {{note |Beta Features| I guess we didn't hide this well at ll ;-)... There are two features available in Papyrus-RT 1.0 under an early availability ''"Beta"'' approach so that we get feedback from our users on their capabilities: RSA Import and Textual modeling. If you use either of those features, we would appreciate your feedback! But remember: '''use at your own risk!'''}} |
Revision as of 09:45, 20 July 2017
Oxygen v1.0 Release Notes
Back to Papyrus-RT v1.0 release
WARNING: Working version of the release notes! This page WILL CHANGE prior to release!
What have we done!
The best part is that we have finished what we originally wanted to accomplish in MVP2 (and maybe a bit more) -- and we managed to move to Oxygen!
These were the goals we have set for this release, along with what we have done:
- Migrate to Papyrus Oxygen - accomplished!
- This was more work than anticipated, as many changes were done in Papyrus to make it better and more flexible - and that meant we needed to adapt. Luckily, we had great collaboration with the Papyrus team and most of our issues were addressed. As we release Papyrus-RT 1.0, there are still somePapyrus bugs blocking Papyrus-RT that will need monitoring to see about doing something when they are fixed...
- Complete work on hierarchical state machine behaviour - accomplished!
- Improving the usability of the state machine editor for UML-RT was a priority and much work was done to improve this. We have tried and, we believe, achieved in implementing a good user interface for creating and navigating UML-RT state machines (there were so many corner cases in doing so!).
- Complete work on structural Inheritance - accomplished!
- This barrel of
monkeyspoisonous snakeslaughs from v0.9 was emptied and our developers are on the way to full recovery thanks to summer holidays! - There are still a few little quirks (see "Known Issues" ), so we will need to see what can be done in subsequent releases.
- This barrel of
- Complete work on behavior Collaborative modeling (hierarchical state machine compare/merge) - accomplished!
- Many improvements were done with regards to both structure and behaviour compare/merge.
- Complete work on basic support from code snippet view - accomplished!
- The code snippet view is now better integrated into the workflow and available in more contexts. If you want to work in a full-blown, target language-aware editor for, you still need to start a separate view - but that is still functionality for the future.
- Complete work on pervasive default language support - accomplished!
- Target language can now set when creating a model or through the model's properties and is used whenever a target language can be used.
- Complete work on behavior Inheritance - accomplished!
- More monkeys taken out of that barrel...
- Complete work on runtime support - Partially accomplished!
- Some work was done to improve Windows support.
- Improved Documentation on the wiki to help with command line parameters and debugging commands (which can already be accessed from the command line help).
- Threading support will be added to the wiki shortly after the release.
- Plus, we got all the improvements from the Papyrus Oxygen release!
- Beta
- We did not do too well with the Beta. We learned our lesson in that an unstructured beta is not the best approach. Next time, we will do better! In the mean time, we are hiding two "early availability" features in the relese - if you find them (hint: look further down on this page for a hint), we would appreciate your feedback!
Warnings, Notes, and Tips
- Bug519052
- Bug510188
Known Issues
Yes...we are still painfully aware that there are still issues with the tool. A list of known issues is provided below, with workarounds, when available.
Note that the descriptions of the known issues, below, are summarized from their corresponding bug discussions.
Bugs are listed from most recent to oldest, with bugs found after the official release indicated with a leading "[new]" tag and those updated post-release indicated by an [updated] tag.
-
512317Copy/Paste of state from one diagram to another drops duplicate edit parts - This bug has been solved in that there is no longer duplication of parts. However, cut and paste from diagrams only works for single states - so "patterns" can not be copied in that manner. However, copy and paste of elements sets from one state machine to another using the model explorer will result in a correct copy. See also bug 519854 for related issues to be addressed in a future release to add the copy and paste capability from diagrams.
- 519052 To build generated code on Windows users must use cmake from Cygwin not from CMake website
- When building generated code on Windows with Cygwin, users must install and use cmake from Cygwin, rather than CMake from cmake.org, otherwise the build fails with several CMake errors, such as being unable to load several of the RTS .cmake files even if they exist and are in the correct location.
Closed Bugs
There were 152 bugs closed as part of this release. That's too many to list here!
So I'll be lazy efficient and give you a link to the complete list of closed bug in Papyrus-RT 1.0.
Back to v1.0 release]