CUBA Studio Changelog

Version 1.5.2

1. Statistics button in the project properties panel shows the number of entities, screens, etc.
2. Root package field have been made read-only. If you want to change the root package, close the project in Studio, move all your classes to the new package and edit the metadata.xml and spring.xml files.
3. Notification about platform updates is more descriptive now.
4. Added icons for the chart components.
5. Fixed service name validation.
6. Fixed copyright variable names to conform IntelliJ IDEA supported variables.
7. The list of samples is read from cuba-platform.com resource instead of the GitHub unauthenticated API.
8. More descriptive log messages.

Version 1.5.1

1. If the project uses the charts base project, the component palette contains charts and MapViewer.
2. The local Maven repository can be added to build.gradle: see Advanced tab on the project properties page.
3. Support for Vaadin 6 is now disabled for projects based on the platform version 5.5+.
4. Fixed bug which prevents reading project settings after importing the project.

Version 1.5.0

• Common
  1. Platform release 5.5 support.
     Automatic migration of existing projects changes the platform XSD version to 5.5 in all XML files.
  2. Projects can be opened from any location on the file system. The Workspace field is removed from the server window.
  3. Remote connections to your Studio server can be established only if you set the Enable remote connections in the server window. By default, only connections from localhost are possible.
  4. Sample projects can be easily downloaded from GitHub and opened in Studio. See the Samples button in the Select project window.
  5. Show changes button enables you to review changes before saving them to disk. It is available in all designer pages, as well as in the confirmation dialog which appears on closing a page containing unsaved changes.
  6. Now you can replace the modules and artifacts prefix (app by default). See the Advanced tab on the project properties page. For example, if you change the prefix to sales, the resulting web applications will be named sales and sales-core.
  7. Additional dependencies can be added on the Advanced tab of the project properties page. They will be preserved in case of full regeneration of the build scripts, for example, if you add a base project.
  8. HSQL database files are now located inside the project folder in build/hsqldb subdirectory. The database created in the previous Studio version will be automatically copied to this directory on the project opening.
  9. Added hot deploy for service implementations. Service interfaces are not deployed.
  10. Studio logs can be viewed in the console panel.
  11. Console panel wraps long lines.
  12. On the Settings page, you can change the XML formatting rules. By default, each XML attribute is printed on a separate line. You can disable this to break lines only after exceeding the maximum line length.
• Entity designer
  1. Better handling of changing the entity attribute type.
  2. When you create a mandatory (non-null) attribute, or make an existing attribute mandatory, Studio generates DB scripts, which update empty fields to default values.
  3. Now you can exclude an update script and do not execute it. Unlike removed scripts, Studio will ignore changes, corresponding to the excluded scripts when you generate scripts next time. This allows you to have differences between the database and the model entities. For example, you may want to add a database field to a table, corresponding to a project entity, but do not map it to an entity attribute. When Studio generates a script to delete the field from the database, just exclude it, and Studio will never generate it again.
  4. The Do not delete columns started with field of the Settings page allows you to specify a prefix for table columns, that should not be tracked by Studio. See details in the context help.
  5. The DDL preview tab shows also constraints and indexes.
• Screen designer
  1. If the project is based on the platform version 5.5+, you can edit the application main window layout similarly to any regular screen. See Create/Edit main window link on the Screens navigator panel.
  2. Changes to a Table identifier are reflected in all components that use it (button actions, etc.).
  3. Tab identifiers are generated automatically.
  4. New Embedded attributes are added to existing screens.
• Over 50 other bug fixes, enhancements and usability improvements.