Eclipse Community Forums: Papyrus » Severe bug in Profile Diagram

Help

Home

Home » Modeling » Papyrus » Severe bug in Profile Diagram

Show: Today's Messages :: Show Polls :: Message Navigator

Severe bug in Profile Diagram [message #1724393]

Tue, 23 February 2016 15:44

Marc-Florian Wendland

Messages: 83
Registered: January 2013

Member

Hi all,

while working with Mars, I encountered a severe (really) bug in the Profile Diagram of Papyrus. It is not possible to establish associations (using the Palette entry) that route from a Stereotype to a Metaclass.

Would someone please confirm this bug. I will then file a critical bug at Bugzilla.

Best,
Marc-Florian

Report message to a moderator

Re: Severe bug in Profile Diagram [message #1724503 is a reply to message #1724393]

Wed, 24 February 2016 09:32

Camille Letavernier

Messages: 952
Registered: February 2011

Senior Member

Hi Marc-Florian,

Indeed, this is not possible (Neither from Diagram or ModelExplorer). The only way to achieve this is by cheating a little bit with the semantic model (e.g. creating another association, then changing the type of one of the member ends).

The bug also exists on Neon

Regards,
Camille

Camille Letavernier

Report message to a moderator

Re: Severe bug in Profile Diagram [message #1724510 is a reply to message #1724503]

Wed, 24 February 2016 09:55

Marc-Florian Wendland

Messages: 83
Registered: January 2013

Member

Hi Camille,

so this is known and also filed in Bugzilla?

Is it not intended to fix this bug in Mars SR1? In my opinion, being not able to easily develop UML profiles with Papyrus is a very critical issue.

Your suggestion (we already did so) is feasible but not endurable.

Best regards,
Marc-Florian

Report message to a moderator

Re: Severe bug in Profile Diagram [message #1724519 is a reply to message #1724510]

Wed, 24 February 2016 10:14

Camille Letavernier

Messages: 952
Registered: February 2011

Senior Member

Hi,

Quote:

so this is known and also filed in Bugzilla?

No; I didn't see it reported in Bugzilla. I simply verified that I could reproduce the issue on both Mars and Neon

Quote:

Is it not intended to fix this bug in Mars SR1? In my opinion, being not able to easily develop UML profiles with Papyrus is a very critical issue.

Mars SR1 was in September last year, and SR2 has been built last week (To be released on Friday), so it's too late as well. A fix would have to wait until either 1.1.5 (Which is not scheduled yet) or 2.0 (In June)

Quote: