| [rmf-dev] Conflict between papyrus and RMF on configuration extension |
|
Hi everyone, I come to you trying to solve this issue [1] When installing both Papyrus and RMF there is the following log on the console
!MESSAGE Both 'org.eclipse.papyrus.infra.viewpoints.configuration' and 'org.eclipse.rmf.reqif10.pror' register an extension parser for 'configuration' The main problem is that both papyrus and rmf define a
org.eclipse.emf.ecore.extension_parser for
type="configuration" I didn’t find any simple solution for that.
-
Advice to register only locally [2]
-
Maybe customizing the factories [3] Here are the questions :
-
Did anyone has any simple idea on how to solve it ?
-
How is generated the extension point in org.eclipse.rmf\org.eclipse.rmf.reqif10.pror\plugin.xml ?
o
If manually then it should be present in src
o
I tried a org.eclipse.rmf/org.eclipse.rmf.releng/mvn clean package. (Failed looking for
org.eclipse.rmf.releng.target\${platform.version.name}) Regards, Benoit Maggi [1]
https://bugs.eclipse.org/bugs/show_bug.cgi?id=460254 [2]
http://www.eclipse.org/forums/index.php?t=msg&th=131533/ [3]
http://www.eclipse.org/forums/index.php?t=msg&th=131533/ |