[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [papyrus-rt-dev] Dependency on Core Papyrus
|
Actually, this is a good point.
That fix for connector ends post Neon.2 is required for capsule structure inheritance to work. Without this fix, a new connector created by the user will not be inherited by capsule subclasses until the editor is closed and reopened because the Connector edit helper uses the wrong EFactory to create the ends.
To work around this in Papyrus-RT would require overriding the entire connector edit-helper.
cW
On Jan 10, 2017, 04:02 -0500, Peter Cigéhn <peter.cigehn@xxxxxxxxx>, wrote:
Hi,
I am not fully sure that I understand the implications of "pinning" the builds of Papyrus-RT to the Neon.2 release. As Christian indicates, what about picking up the bug fixes that has been made after the Neon.2 release? When checking the Papyrus Git repo there are at least 2 commits after the Neon.2 release (since the Neon.2 release has not been tagged in the repo it is a bit hard to know exactly which commit was used for building Neon.2), one made by Christian related to the creation of ConnectorEnds and one by Asma related to a fix in the RSA model import.
If we pin to Neon.2, will that mean that we will not pick up the needed bug fixes made after Neon.2? And will that really be sufficient for a 0.9/1.0 release of Papyrus-RT?
Or is this a more "internal" issue? Can a "consumer" of Papyrus-RT still install it on top of the latest nightly of Papyrus, to get the latest fixes anyway, e.g. any further fixes in the RSA model importer for example?
/Peter Cigéhn
_______________________________________________
papyrus-rt-dev mailing list
papyrus-rt-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/papyrus-rt-dev