With revision 47849 in trunk, we have merged the SVN branch where development on the Gradle build was being done into trunk. This is an important checkpoint for our conversion of the build process from Ant to Gradle, but the conversion is not yet complete. We need to do some more extensive testing and further development to complete this conversion.

In the meantime, though, you should see no differences in behavior and can continue to use the ant build commands as you did before. It may happen that IntelliJ will recognize that you have a new build.gradle file and it will ask you if you want to do an import of the project using that build file. At this point, you should refrain from doing this import because default behavior of IntelliJ when doing this import is to remove some important configuration files and to modify others in ways that make your project not able to find many of the files it depends on.

We will be working on the remaining conversion of build tasks and stabilization of the Gradle build process in the 17.1 release cycle and hope to complete the conversion by the 17.2 release.

Let us know if there are questions or problems.

Susan

As one of our final steps in the conversion from Ant to Gradle, in May we will start removing the files that are used exclusively for the ant build. This includes:
- all build.xml files
- the jar files checked in to version control in directories such as external/lib and the individual modules' lib directories
- the Intellij project based in the server directory and all associated .iml files

If you are building LabKey locally and have not yet had a chance to convert to using Gradle, please do so soon and let us know if you encounter any problems. Please refer to our documentation (https://labkey.org/Documentation/wiki-page.view?name=gradleBuild) and the webinar about building LabKey with Gradle (https://youtu.be/Yso6c7V8GPU) for more details about converting.

Susan