Allow BRMS to store graphical .rf file version of a ruleflow under version control ---------------------------------------------------------------------------------- Key: JBRULES-1579 URL: http://jira.jboss.com/jira/browse/JBRULES-1579 Project: JBoss Drools Issue Type: Feature Request Security Level: Public (Everyone can see) Components: drools-brms Affects Versions: 4.0.4 Environment: n/a Reporter: Shahad Ahmed Assigned To: Mark Proctor Would it be possible to allow the BRMS to use the graphical (.rf) versions of a ruleflow file, as well as the non-graphical .rfm version? I believe the .rf file contains all the details in a .rfm file, but also includes graphical data about the node positions etc. Even if this were not possible, would it be possible to allow the .rf version of a rule flow to be simply stored alongside the .rfm version in the BRMS repository so that they can both be put under version control. The reason I ask is that the current situation means that the .rf (graphical) files are the one thing in a rules project that have to be stored and versioned external to the BRMS. Consequently, whenever you want to change your ruleflow you have to go and find the .rf file that you stored out with the BRMS and hope it is the correct version etc. With either of the two changes proposed above, then at least the BRMS repository holds and versions all the important parts of a rules package, and the user can always download the correct .rf file and edit it in eclipse. I suppose the ultimate solution would be the ability to edit ruleflows within the BRMS (as requested in JBRULES-851) so that this feature request is not needed, but until then this request would help with version controlling and modifying graphical ruleflows and bring all the important parts of a rule package under the control of the BRMS repository. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira