In order to do away with some flawed logic related to applying the LabKey gradle plugins, I am planning to remove the server/modules/build.gradle file early next week in our develop branches, in time for LabKey Server version 21.3.0. If you are maintaining your own local modules, you may need to add or update your build.gradle files in order to apply the plugin that had been being applied from this file. See this page for more details.

After this file is removed, and we update to the 1.25.0 version of the LabKey Gradle plugins, if the Gradle plugin detects a module that has a module.properties file but does not have a module task, a warning like the following will be shown at the end of running the deployApp command:

The following projects have a 'module.properties' file but no 'module' task. These modules will not be included in the deployed server. You should apply either the 'org.labkey.build.fileModule' or 'org.labkey.build.module' plugin in each project's 'build.gradle' file.
        :server:modules:myModule
        :server:modules:otherModule

You can fix this by applying the appropriate plugin as suggested or by defining your own module task that creates the .module file needed for inclusion in your LabKey Server instance.

Also, if you previously had a build.gradle file that references configurations, tasks, etc. defined in the Gradle plugins, you may encounter errors during the configuration phase when running a Gradle task like the following.

FAILURE: Build failed with an exception.

* Where:
Build file '/path/to/Development/labkey/root/server/modules/myModule/build.gradle' line: 6

* What went wrong:
A problem occurred evaluating project ':server:modules:myModule'.
> Could not find method implementation() for arguments com.sun.mail:jakarta.mail:1.6.5 on object of type org.gradle.api.internal.artifacts.dsl.dependencies.DefaultDependencyHandler.

This is fixed in the same way, by applying the plugin that had been being applied in server/modules/build.gradle.

If you have questions or encounter problems, please let us know.

Susan