| Hi,
if I look into the sources in git repository (branch develop) I can see several plugin.xml files which register extension parsers:
(1) org.eclipse.rmf.ext.prostep registers extension parser for „prostep“ => the extension parser should be removed
(2) org.eclipse.rmf.reqif10.pror registers extension parser for „configuration“ => the extension parser should be removed
(3) org.eclipse.rmf.reqif10.serialization registers extension parser for „reqif“ => correct. We should keep this extension parser
(4) org.eclipse.rmf.reqif10.xhtml registers extension parser for „xhtml“ => the extension parser should be removed
Where did you expect the registration of the extension parsers? Did you search in the git repository or in the deployed source bundles?
kind regards
Mark
Hi, Thanks, it would be perfect for us if you remove the configuration parser from RMF. Do you have an explanation for the fact that it not present in the source but in the package plugins ? Regards, Benoit Maggi RMF should register the file name extensions "reqif" and "reqifz" only. Thus, we (RMF project) should remove the other extension parsers (e.g. "configuration") I can fix it for the upcoming release 0.12.0. Hi Benoit,
I CC'd Matthieu (also from CEA), who may be able to help you: He worked on the Papyrus integration with RMF in the openETCS-Project.
Hope this helps!
Best,
- Michael
On 19.02.2015 15:26, MAGGI Benoit wrote: 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 aorg.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] - 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 fororg.eclipse.rmf.releng.target\${platform.version.name})
_______________________________________________ rmf-dev mailing list rmf-dev@xxxxxxxxxxx To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/rmf-dev
-- Dr. Michael Jastram | +49 (162) 274 83 94 | | Geschäftsführer | Formal Mind GmbH | | Gründer | rheinjug e.V. | | Project Lead | Eclipse Requirements Modeling Framework | |
_______________________________________________ rmf-dev mailing list rmf-dev@xxxxxxxxxxxTo change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/rmf-dev
|
