CUBA Studio Changelog

Version 1.1.2

Version 1.1.1

Version 1.1.0

1. Platform 5.1 release support.
   Automatic migration of existing projects is provided, the following files are changed by the migration procedure:
   • build.gradle: clearMessagesCache added.
   • modules/web/src/web-app.properties: cuba.metadataConfig property now includes cuba-gui-metadata.xml and cuba-web-metadata.xml; cuba.persistenceConfig property added.
   • modules/desktop/src/desktop-app.properties (if exists): cuba.metadataConfig property now includes cuba-gui-metadata.xml; cuba.persistenceConfig added.
   • Spring XSD changed from 3.0 to 3.1 in all *-spring.xml files.
   Known issue 1: the migration misses the portal module, so if you have created it, make the following changes manually:
   • Add to modules/portal/src/portal-app.properties:
     cuba.persistenceConfig = cuba-persistence.xml persistence.xml
   • Class com.haulmont.cuba.portal.command.LoginUserCommand was removed from the platform, so if you use LoginController from the Portal template, create your own LoginUserCommand POJO and import it into the LoginController.
   Known issue 2: the migration does not update XSD version in XML screen descriptors and configuration files. You can easily do it by searching http://schemas.haulmont.com/cuba/5.0/ string in all XML files of your project and replacing it to http://schemas.haulmont.com/cuba/5.1/.
2. Basic VCS integration.
   Open Project properties page and select Git or Subversion in VCS field. After that all project files added, changed or removed by Studio will be submitted to the VCS. Of course the project folder must be a valid working copy.
   Intergration works through command line interface, so appropriate executable files must be on your system PATH.
3. Option to create web UI module based on Vaadin 6. This option is recommended only if you have to support Internet Explorer 8 clients and your screens are rendered too slowly on Vaadin 7 due to this problem.
   See Project Properties > Base projects > Vaadin version field.
4. Automatically generated standard browse screen can be immediately added to the main menu. See Menu field in Create standard screens dialog.
5. Better support for entities extension: @Extends annotation, correct DB scripts generation.
6. Create database and Update database buttons are added to the DB scripts page.
7. Messages cache is cleared on hot deploy, so changes to screen's localized messages are immediately reflected in the running application.
8. Support for hot deploy of arbitrary directories inside the project: see Screens > Instant hot deploy > Settings. By default only source directories of GUI and Web modules are monitored and deployed, but you can add your own. This is very useful if you develop a Portal module with some HTML/JS stuff: for example, just add modules/portal/web/somedir as source and build/tomcat/webapps/app-portal/somedir as destination, and contents of somedir will be automatically copied on changes.
9. Support for embedded UI component.
10. Ctrl-Shift-F9 keyboard shortcut restarts application server. Known issue: the shortcut may not work if focus is inside the navigator's tree.
11. Offline mode can be set explicitly - see Offline checkbox in the Studio Server window. We recommend to use it in case of unstable Internet connection.
    Keep in mind, however, that offline work is possible only if you have built your project online previously, and all required artifacts are cached locally by Gradle and Studio.
12. Anonymous usage statistics sending.
    Please help us to improve Studio by automatically sending anonymous usage statistics and crash reports to Haulmont. You can review what will be sent by looking at ~/.haulmont/studio/stat directory. Statistics is accumulated while you are working with Studio. It is sent on project close or exception and then removed from the directory.
13. Plugins support. The main goal is to adapt Studio for building product extensions. Among other things, the plugin can add base projects, so the project can be based not only directly on CUBA, but on an existing CUBA application.
14. Bug fixes, including:
    • View is duplicated in Studio UI after several clicks on "Apply"
    • Attribute 'trackSelection' for action disappears after screen modification
    • Unable to save existing screen after changing its reference
    • No update script generated when adding column to extended entity with Single Table strategy
    • Unable to create FileDescriptor attribute in entity
    • Extended screen controller doesn't call super.init()
    • Incorrect localized entity name saving
    • It is impossible to use relationships from inside of an embedded class