Ways To Contribute

Other Ways To Contribute (for both API / TCK projects)

(The "Other" refers to the "everything else" except working on new spec/API features and corresponding TCK tests).

Refactoring, documenting, and otherwise improving the project.

At this point the project has not collectively prioritized anything, so these are just ideas

Organization

• Reading through legacy issues to decide which ones to reopen

Code formatting

• Tabs/whitespace, Java style/formatting - let’s do as a one-time mass replacement.

  • As of now, the batch-tck master branch uses IDEA formatting shown here: https://gist.github.com/thadumi/ffafd8f1273247cf30dd50e10b575baf.

  • Enforcement/checks during build? Check copyrights too?

• IDEAS:

  • https://maven.apache.org/plugins/maven-checkstyle-plugin/

  • eclipse-settings-maven-plugin as with https://gist.github.com/dashorst/b80f4a8a13fb945a41e5f7b2ffc7e31f

  • What are other Jakarta projects using?

TCK

• convert to Arquillian?

  • e.g. see here where the JSONB TCK was converted.

• use JUnit 5?

  • Note this conversation where some issues integrating JUnit 5 and Arquillian have been raised. Would this affect porting the Batch TCK?

• this conversation discusses about what to do in Batch TCK

Build/Doc

• Build/release - Set up real CI pipeline, (either the one used by other Jakarta projects or a new one). Right now the release is manual, and nothing like Travis either.

• Website - e.g. the official EE4J Eclipse project page here and/or adding a github.io GitHub Pages site.

• Spec doc issues - should we separate out the spec project, for easier issue tracking etc.?

• Contributor’s guide