Hi Mark, I looked in master branch, which is the branch where I expected to found the latest version. The parser registration is indeed present in develop branch [1](L 30) but not in master [2].
My bad, I missed the part in the Development process [3] describing the chosen workflow. I posted a feature [4] to improve the repository description, it may be good to add the link [5] to the CONTRIBUTING.md file Regards, Benoit Maggi [1] : https://git.eclipse.org/c/rmf/org.eclipse.rmf.git/tree/org.eclipse.rmf.reqif10.pror/plugin.xml?h=develop [2] : https://git.eclipse.org/c/rmf/org.eclipse.rmf.git/tree/org.eclipse.rmf.reqif10.pror/plugin.xml [3] : https://wiki.eclipse.org/RMF/Contributor_Guide/Development_Process [4] : https://bugs.eclipse.org/bugs/show_bug.cgi?id=460319 [5] : http://nvie.com/posts/a-successful-git-branching-model/ De : rmf-dev-boun...@eclipse.org [mailto:rmf-dev-boun...@eclipse.org] De la part de Mark Brörkens Envoyé : vendredi 20 février 2015 13:48 À : Developer mailing list for the Requirements Modeling Framework Objet : Re: [rmf-dev] Conflict between papyrus and RMF on configuration extension 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 Am 20.02.2015 um 13:33 schrieb MAGGI Benoit <benoit.ma...@cea.fr<mailto:benoit.ma...@cea.fr>>: 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 De : rmf-dev-boun...@eclipse.org<mailto:rmf-dev-boun...@eclipse.org> [mailto:rmf-dev-boun...@eclipse.org] De la part de "Mark Brörkens | itemis.de<http://itemis.de>" Envoyé : vendredi 20 février 2015 13:15 À : Developer mailing list for the Requirements Modeling Framework Objet : Re: [rmf-dev] Conflict between papyrus and RMF on configuration extension Hi all, 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. Regards Mark Am 20.02.2015 um 11:34 schrieb Michael Jastram <mich...@jastram.de<mailto:mich...@jastram.de>>: 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: 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 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] 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 fororg.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/ _______________________________________________ rmf-dev mailing list rmf-dev@eclipse.org<mailto:rmf-dev@eclipse.org> 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 http://jastram.de<http://jastram.de/> Geschäftsführer Formal Mind GmbH http://formalmind.com<http://formalmind.com/> Gründer rheinjug e.V. http://rheinjug.de<http://rheinjug.de/> Project Lead Eclipse Requirements Modeling Framework http://eclipse.org/rmf _______________________________________________ rmf-dev mailing list rmf-dev@eclipse.org<mailto:rmf-dev@eclipse.org> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/rmf-dev _______________________________________________ rmf-dev mailing list rmf-dev@eclipse.org<mailto:rmf-dev@eclipse.org> To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/rmf-dev
_______________________________________________ rmf-dev mailing list rmf-dev@eclipse.org To change your delivery options, retrieve your password, or unsubscribe from this list, visit https://dev.eclipse.org/mailman/listinfo/rmf-dev
