[jboss-jira] [JBoss JIRA] Resolved: (JBRULES-1945) Migrating version 4 graphical ruleflows to version 5 in Eclipse plugin and the Guvnor

[Kris Verlaenen (JIRA)]

     [ https://jira.jboss.org/jira/browse/JBRULES-1945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kris Verlaenen resolved JBRULES-1945.
-------------------------------------

    Fix Version/s: 5.0.0.CR1
       Resolution: Done


Thanks a lot for the patch !
I applied the changes to trunk.

> Migrating version 4 graphical ruleflows to version 5 in Eclipse plugin and the Guvnor
> -------------------------------------------------------------------------------------
>
>                 Key: JBRULES-1945
>                 URL: https://jira.jboss.org/jira/browse/JBRULES-1945
>             Project: JBoss Drools
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: drools-compiler, drools-compiler (flow), drools-eclipse, drools-eclipse (flow), drools-guvnor
>    Affects Versions:  5.0.0.M4
>         Environment: n/a
>            Reporter: Shahad Ahmed
>            Assignee: Kris Verlaenen
>             Fix For: 5.0.0.CR1
>
>         Attachments: ruleflow_migratory.zip
>
>
> Add improved support for migrating version 4 ruleflows to version 5. Drools 5 does not support opening and migrating drools version 4 .rf (graphical) ruleflow files using the drools eclipse plugin. 
> There is also a BUG in the Guvnor  where version 4 ruleflow assets already in a repository cannot be archived, saved etc. as a NullPointerException is thrown on the server when any action is taken on such assets. 
> Also existing support for migrating .rfm ruleflow files in the compiler does not support import or global definition inside split, join nodes etc.
> Sorry for putting a whole bunch of ruleflow issues in a single JIRA, but they all turn out to be interrelated and I have a patch that resolves all these issues that will be attached to this JIRA
> Shahad

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira