Bug 518457 - [Diagrams] Revert workaround for the CSS Factory priority
Summary: [Diagrams] Revert workaround for the CSS Factory priority
Status: ASSIGNED
Alias: None
Product: Papyrus-rt
Classification: Modeling
Component: tool (show other bugs)
Version: 0.9.0   Edit
Hardware: All All
: P3 normal
Target Milestone: 1.0.2   Edit
Assignee: Camille Letavernier CLA
QA Contact:
URL:
Whiteboard: depends_on_papyrus
Keywords:
Depends on: 518455
Blocks:
  Show dependency tree
 
Reported: 2017-06-19 09:12 EDT by Camille Letavernier CLA
Modified: 2017-10-17 14:35 EDT (History)
3 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Camille Letavernier CLA 2017-06-19 09:12:27 EDT 
When targetting Photon, or after Bug 518455 is fixed on Oxygen, the workaround used in Bug 517688 should be reverted.

I've increased the order of the Papyrus-RT CSS Factory (Providing custom CSS properties) from 45 to 9, because the order of the default UML one has changed from 50 to 10. Bug 518455 (Oxygen) and/or the Photon release (Already fixed) should restore the order of the default factory to 50, so we should revert our own to 45 (Although this is less of an issue for our factory, as it only applies if the UML-RT language is installed, so the risk of conflicts is low).
Comment 1 Simon Redding CLA 2017-07-04 13:37:36 EDT 
Hi Camille - will this be fixed this week or should it be pushed out to a later release?
Comment 2 Camille Letavernier CLA 2017-07-05 03:02:37 EDT 
Hi Simon,

It depends on a release build for Papyrus 3.0.1 (Oxygen SR1), so this is definitely not a short-term perspective. At the earliest, it may be fixed on a Nightly build, after PapyrusRT 1.0.0 is released.
Comment 3 Charles Rivet CLA 2017-07-05 08:00:16 EDT 
(In reply to Camille Letavernier from comment #2)
> Hi Simon,
> 
> It depends on a release build for Papyrus 3.0.1 (Oxygen SR1), so this is
> definitely not a short-term perspective. At the earliest, it may be fixed on
> a Nightly build, after PapyrusRT 1.0.0 is released.

Moving to 1.0.1 to assess if we can/should have a 1.0.1 release or concentrate on 1.1.0 (Oxygen.1)
Comment 4 Ernesto Posse CLA 2017-10-17 14:35:45 EDT 
Mass changing all 1.0.1 bugs to target milestone 1.0.2, because Bug 520039 depends on Bug 526168 which depends on Bug 526167 which modifies plugin MANIFEST files and therefore requires a new service version number in accordance to the guidelines at https://wiki.eclipse.org/Version_Numbering#When_to_change_the_service_segment. Hence the solution to these bugs must be merged as a new version (1.0.1) and therefore all old 1.0.1 bugs should become 1.0.2.