You can go ahead and open another thread for this on the beta forum. Probably best not to move this one so the original opener of the topic doesn't keep getting notifications. We can just put a link to this thread in the new one, so it won't be confusing looking back later.
Losing the check state for the gradle wrapper: is there a gradlew or gradlew.bat in the root of the project? I think we might be seeing that file and assuming it should use the wrapper. I'll look into that.
For the sub-projects you're not picking up source for, has SlickEdit created matching .vpj files for those sub-projects? It may be there's a bug in how we detect and set up those projects, but it's not something I've run into with the test projects I've worked with.
That failure to build is odd. There may be a failure to pick up from GROOVY_HOME in the setup, but it should prompt in the case that it thinks there is no groovy home is set. There were some problems in the past with tasks having hard coded parts (or depending on gradle being on the path), but running Gradle Options on the project should have forced the tasks to be updated. The task names are case insensitive.
I'll have to look into the compiler tagging. Changing the default compiler in the Java Compiler properties page should change up the tag files used for lookups, so there may be something wrong there.
Probably the easiest thing to start with is to collect some files from you. In a zip or tar, or whatever, could you pack up the following things:
- Your user.config.xml file that's in your configuration directory.
- Your workspace .vpw file
- The .vpj file for one of the projects that has that build problem.
- Go to "Build -> Gradle Options..." and step through the wizard pages again. Once that's done, there will be some output I can use for debugging down in the Output tool window. Right click in the Output window, and "Save As...", and save it to a file like output.log, and put that in the archive.
- And your settings.gradle from the root of your project.
We'll PM you with the instructions on how to upload the archive to support. Create a new thread in the beta forum to let me know when it's uploaded, and we'll go from there.
Thanks for the detailed report.