license v1.0 is now deprecated (see ), and it’s
recommended to move to EPL v2.
understanding when simply moving from EPLv1 to EPLv2
there is no legal complexity
and headers and
other files should be updated accordingly (See ).
train release, I will publish a SysML 1.4 version
compatible with Papyrus 4.0.0 (Photon)
This version will
be number 1.3.0 and I want to take this opportunity
to update the license.
I created a
dedicated bug  and also a patch 
Any comments ? It
would be nice if someone can check the patch.
the shared license concept in feature. (It would be
nice to use it in Papyrus core)
Can we agree
to change the name of Bundle-Vendor from Eclipse
Modeling Project to (one of them)
patterns used by other projects but I’m open to
anything containing “Papyrus”)
main reason is to remove Papyrus prefix from the name
of the plugins (should improve the clarity)
1 : https://www.eclipse.org/legal/epl-2.0/faq.php#h.60mjudroo8e5
2 : https://www.eclipse.org/legal/epl-2.0/faq.php#h.tci84nlsqpgw