Updated data object is not take into account when the project is redeployed in the "development mode"

When a data object is updated in already deployed project (in development mode), the change is not taken into account. However, this works fine if the project is saved in the production mode. 

Steps to reproduce:

1. Create new project (leaving the default "development mode" in the Project Settings), add new data object..for instance: person (name as String and surname as String) and save this asset.
2. Add new Business Process Asset with simple start -> user task -> stop. 
3. In the Business Process add person object as process data;
4. Navigate to user task and set the following:
   1. :kie-server as Group,
   2. add person as Task output and assignments
   3. in the "OnExit" Action add:System.out.println("name: "+person.getName());

System.out.println("surname: "+person.getSurname());
 

1. Save the change and create all forms;
2. Deploy this project;
3. Execute the process (the server.log file should show values for name and surname);
4. Make the change in the person data object and add "email" for instance;
5. Save the change;
6. Add "System.out.println("email: " + person.getEmail()); to the process's "OnExit" Action;
7. Save the change;
8. Remove previously created forms and create new ones;
9. Redeploy this project and execute it again;
10. As a result, name and surname will be properly shown in the server.log file but we will have email: null instead of the proper value:
    1. 10:56:00,018 INFO [stdout] (default task-34) name: biljana
       10:56:00,019 INFO [stdout] (default task-34) surname: kramer
       10:56:00,019 INFO [stdout] (default task-34) email: null
11. If the project is saved in the production mode, then this redeployment works fine.  

If the project is saved in the production mode, then redeployment works fine and the data object is updated. Also, when the server is restarted, the updated data object is taken into account for the project in the "development mode". 

Attached file contains detailed instructions to reproduce this issue.