Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update build process to use Maven #3820

Closed
14 tasks done
fmbenhassine opened this issue Dec 15, 2020 · 3 comments
Closed
14 tasks done

Update build process to use Maven #3820

fmbenhassine opened this issue Dec 15, 2020 · 3 comments
Labels
in: build status: for-internal-team Issues that are planned to be resolved by the Spring Batch team, and not open for contributions. type: task
Milestone
5.0.0-M1

Comments

@fmbenhassine
Copy link
Contributor

  • Configure maven-compiler-plugin to compile source code
  • Configure maven-surefire-plugin to run unit tests (mvn test)
  • Configure maven-failsafe-plugin to run integration tests (mvn verify)
  • Configure maven-ant-plugin to run the JSR TCK as part of maven's integration-test phase (no custom profile)
  • Configure maven-javadoc-plugin to generate javadocs (individual modules and aggregate docs)
  • Configure maven-source-plugin to generate source jars
  • Configure asciidoctor-maven-plugin to generate reference documentation in html/pdf
  • Configure maven-assembly-plugin to generate a single distribution of docs/schemas
  • Configure jacoco-maven-plugin to run test coverage and generate report (with a test-coverage profile)
  • Configure maven-flatten-plugin to optimize pom files before distribution
  • Configure maven-gpg-plugin to sign jars before distribution
  • Configure maven-deploy-plugin to deploy artifacts to artifactory
  • Add maven wrapper files
  • Update build process documentation
@fmbenhassine fmbenhassine added this to the 5.0.0-M1 milestone Dec 15, 2020
@fmbenhassine fmbenhassine mentioned this issue Dec 15, 2020
Closed
@fmbenhassine fmbenhassine linked a pull request Dec 15, 2020 that will close this issue
Update build process to use Maven #3821
Closed
@fmbenhassine
Copy link
Contributor Author

Resolved with #3821 .

fmbenhassine referenced this issue Mar 12, 2021
@fmbenhassine
Update build to use Maven instead of Gradle
fa53dde
@maoshuai
Copy link

Why move back from Gradle to maven?

@fmbenhassine
Copy link
Contributor Author

Spring Batch used maven since its creation. Switching to gradle was an attempt to achieve consistency across the portfolio. Unfortunately, this consistency was not achieved, so we decided to go back to maven.

@fmbenhassine fmbenhassine added the status: for-internal-team Issues that are planned to be resolved by the Spring Batch team, and not open for contributions. label Jun 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
in: build status: for-internal-team Issues that are planned to be resolved by the Spring Batch team, and not open for contributions. type: task
Projects
None yet
Milestone
5.0.0-M1
Development

Successfully merging a pull request may close this issue.

Update build process to use Maven fmbenhassine/spring-batch
2 participants
@fmbenhassine @maoshuai