Hi Camille,
I can understand that the migration and the planned diagram editor refactorings are not trivial
(we are very aware - and very wary! - about that).
We do support the idea of clearly separating SysML1.1 and SysML1.4 and keeping both maintained until this is all stabilized.
But to that aim, why not reorganize slightly the repo and features to have something like that? :
plugins/
core/
uml/
sysml11/
sysml14/
... with sysml11 being just a renaming/move of the current sysml folder,
and with syml14 having the very same structure & java namespaces as sysml11, with just the new version of the profile,
and new diagram editors using the new diagram customization mechanisms (based on viewpoints I guess?).
That way, they would be even more clearly separated.
The only restriction would be that one cannot have SysML1.1 and SysML1.4 active in the same Eclipse configuration,
but that could be acceptable, couldn't it?
(and one could still have a single install of Papyrus with the two configurations available I think).
Those wanting to do legacy SysML1.1 would use the first configuration with the legacy set of SysML plugins active.
Those wanting to go SysML 1.4 would use the second configuration, whose org.eclipse.papyrus.sysml profile could contain both the static 1.4 and dynamic 1.1 SysML profiles.
I don't think having both at once in a single running instance of Papyrus would be that useful, or would it?