Releases: e-Spirit/firstspirit-module-gradle-plugin
6.6.0
6.5.2
This releases restores compatibility with Gradle older than version 8.11.
6.5.1
This release fixes compatibility issues with Gradle 8.12.
6.5.0
The new task checkCompliance
can be used to verify that a module only uses stable elements of the fs-isolated-runtime.jar
. Internal classes and deprecated code elements may change or get removed in the future, so they will be reported in a parseable JUnit report.
It is possible to change the FirstSpirit version to check against with the parameter -PcomplianceCheckFsVersion=<version>
or setting firstSpirit.version
in the gradle.properties
file.
6.4.1
6.4.0
It is now possible to configure the scope of the Jar file which is built by the default jar task and automatically added to the FSM.
Example usage:
firstSpiritModule {
projectJarScope = "server"
}
6.3.0
You may now define custom parameters for UrlFactories using the new UrlFactoryComponent.Parameter
annotation. See FirstSpirit documentation for more info.
Example Usage:
@UrlFactoryComponent(
name = "MyUrlFactory",
parameters = {
@UrlFactoryComponent.Parameter(name = "useIRIs", value = "yes"),
@UrlFactoryComponent.Parameter(name = "useWelcomeFileNames", value = "yes")
}
)
public class MyUrlFactory {
}
Custom parameters are rendered into the module-isolated.xml when building the module.
6.2.1
6.2.0
Components may now be marked as "hidden" so they do not appear in ServerManager.
6.1.0
- Dependencies not defined using fs-configurations like
fsModuleCompile
will no longer be placed in thelib
directory. - If a project specifies multiple versions of the same library, this will now result in a build error pointing out that only a single version is going to be included in the FSM.
Please see the upgrade instructions for details.