Platform and Studio 6.10 BETA

Announcements
#1

The BETA version of the upcoming platform release 6.10 is now available. It is feature-complete and we are working on minor fixes and documentation. The final release is scheduled for the end of September.

Please see the Release Notes and updated documentation:

Developer’s Manual
Business Process Management
Charts and Maps
Full Text Search
Report Generator

We will greatly appreciate if you test your project with the beta version and let us know about any issues.

The platform 6.10.0.BETA artifacts are available in both repo.cuba-platform.com and Bintray repositories, so you will be able to use them if you download and install the latest CUBA Studio SE Nightly Build.

We are looking forward to your feedback!

5 Likes
#2

Hi there.

I imported my project and, sure enough, I’ve got a tool window (IntelliJ) for Gradle

But how do I run my tests. Each time I try to run, I get this error:

java.lang.IllegalStateException: Entity 'com.test.peer.entity.Institute-03323e2e-bd4d-ad37-3491-40df7c83a49c [managed]' is a ChangeTracker but has no PropertyChangeListener

I’m guessing this has something to do with the entity enhancement?

#3

Could you check if Studio correctly changed your build.gradle? See the first item here.

#4

No, it didn’t do that, even though I opened the project in the Studio 6.10

The section of the file looked like this:

configure(globalModule) {
    task enhance(type: CubaEnhancing)


}

So I changed it to this:

configure(globalModule) {

    entitiesEnhancing {
        main {
            enabled = true
            persistenceConfig = 'custom-persistence.xml' // optional
        }
        test {
            enabled = true
            persistenceConfig = 'test-persistence.xml'
        }
    }

}

which still doesn’t work.

IntelliJ flags up an error though. It says that can’t resolve symbol ‘entitiesEnhancing’

#5

After you opened the project in Studio 6.10 and changed the platform version to 6.10.0.BETA1, Studio had to show you the migration dialog:

image

And after the migration, build.gradle should have something like this:

configure(globalModule) {
    entitiesEnhancing {
        main { enabled = true }
    }    
}

Did you see the migration dialog?

#6

Okay, yep. It’s done that. Now do I import the build.gradle into IntelliJ or do I just open the ipr file as normal?

Do I need to set up gradle wrappers or anything like that?

#7

Okay, I think I’ve got it.

  1. Create a fresh empty project in IntelliJ
  2. Import the build.gradle file as a module into the empty project.
  3. Remember to set the Gradle runner settings to delegate the build/run processes to Gradle:

55

This seems to work fine now.

#8

The generated project causes an exception in IntelliJ

 Module 'app-web-themes_main' and module 'app-web-themes' have the same content root:

which means you cannot do anything with the project structure without fixing it.

#9

Hi,

i wanted to give it a try. So i went and downloaded the dmg file for mac. Normally I use the zip distribution, because I run it from the cmd line. However, since it is not available, i just used it through DMG. What I found was, that it is not able to be executed if java is installed via SDKMAN, because the mac does not understand that (as it seems).

Perhaps you can additionally add the zip based variant to the download selection.

Thanks
Bye
Mario

#10

We still recommend that you generate IPR file using gradle idea command. Full Gradle support in Intellij will be available only with Studio and platform 7.0.

With 6.10 there are couple of minor problems if you use Gradle import: themes module, copyrights are not set and so on.

1 Like
#11

Hi Mario,

Could you try to create a bash script for starting the Studio from the command line like this one:

#!/usr/bin/env bash

"/Applications/CUBA Studio SE Unstable.app/Contents/MacOS/CUBA Studio SE Unstable"
1 Like
#12

Version 7, which will include support for Kotlin?

#13

From the original roadmap, I think they said that Kotlin support was more of an opportunity now that they’re going to reimplement Studio as an IntelliJ plugin. I don’t think they have a hard timetable for supporting Kotlin just yet.

Someone will jump in if I’ve not understood that correctly.

1 Like
#14

Okay, the exception you get when you open the project:

Module 'app-web-themes_main' and module 'app-web-themes' have the same content root:

can be fixed by just deleting the app-web-themes-main from the project structure.

#15

Sure, it can be a workaround. But still, please note, integration with Gradle import in 6.10 is not fully functional.

#16

Understood. :slight_smile:

Actually, I’ve just noticed that the IDE has the facility to load and unload modules. How long has that been there??

#17

It is available since 2017.2 as far as I know

#18