This commit removes the usage of the Artifactory plugin and replaces
it with a standard repository structure using the -PdeploymentRepository
option.
This also updates the generated POM to be current.
This commit updates to the latest develocity conventions plugin. This
has the advantage, since 0.0.21, to include the correct relevant Gradle
Enterprise plugin.
Closes gh-1808
Repositories on repo.spring.io requires to be authenticated. This commit
configures the SPRING_REPOSITORY_USERNAME and SPRING_REPOSITORY_PASSWORD
properties accordingly.
Closes gh-1807
Added a LICENSE file at the root level directory. The license are as per the README file (https://github.com/spring-projects/spring-webflow/blob/main/README.md#license). The license is version 2.0 of the Apache License.
(Please note that the Copyright year and owner fields have been intentionally left empty since Google LLC doesn't own this repository)
This change publishes a build scan to ge.spring.io for every local
build from an authenticated Spring committer and for CI where
appropriate access tokens are available. The build will not fail if
publishing fails.
This change also allows the build to benefit from remote build caching,
providing faster builds for all contributors.
Additionally, the project will have access to all features of Gradle
Enterprise such as:
- Dashboards to view all historical build scans, along with performance
trends over time
- Build failure analytics for enhanced investigation and diagnosis of
build failures
- Test failure analytics to better understand trends and causes around
slow, failing, and flaky tests
This commit moves the asciidoctor *.adoc files to the default location
and removes the unnecessary asciidoctor plugin configuration as a
result.
This changes also reworks dependencies between tasks and adds the
missing publication configuration for generated artifacts. The entire
docs-specific script is moved from the main build.gradle file to a
"gradle/docs.gradle" script to improve readability of the main build.
Fixes gh-1797
To avoid any complications with functional changes between Hibernate 5
and Hibernate 6, this uses the hibernate-core-jakarta v5 module rather
than hibernate-core v6. This requires a specific dependency exclusion
in spring-webflow.gradle to make sure that hibernate-entitymanager
never causes both versions to be loaded. This can be simplified after
eventual adoption of Hibernate 6.
The Spring snapshot repository needs to be referenced in build.gradle
for this early stage work on SWF 3.
The java-library plugin is an extension of the older java plugin.
It introduces the api dependency configuration and helps us to get
the right scope in the generated POM.
Porting the JavaServer Faces support forward to Jakarta Server Faces
is outside my area of competence. Hopefully, someone with knowledge
of this area will be able to step up later.
Uses the new Java toolchain feature of Gradle to acquire Java 17.
Doing it this way means that you can start ./gradlew under any version
of Java and still use Java 17 for the build; it picks a candidate from
the environment or downloads one if required. It also takes care of
source and target compatibility, with the exception of ide.gradle
which is handled separately.
The maven plugin was removed in Gradle 7, so we need to replace it with
maven-publish. This uses a similar DSL, but operates in a slightly
different way. The simplest way of handling the differences is to
reorder its application within build.gradle so that appropriate
properties will have been applied by the time publish-maven.gradle
is invoked.
It is easier to standardise this now in one commit rather than
during later bulk changes where it would complicate the review process.
This is literally the result of running "dos2unix" on appropriate files.
There is no attempt here to likewise standardise the spaces/tabs
conventions in the codebase.
