Skip to content

ci: build and publish javax flavour #522

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.

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

Merged
merged 4 commits into from
Jun 14, 2023

Conversation

federicorispo
Copy link
Member

The 'release' github action has a new job to build the javax flavour of this project. This job has three main steps:

  • Replace all the jakarta imports and dependencies with the javax ones
  • Downgrade springframework dependency to the version 5.*
  • Using jdk 11 to build the project and publish it

The cold migration from jakarta to javax is done via a new bash script .github/replaceJakartaWithJavax.sh that uses mainly the sed command to perform the replacement operations.

In gradle.properties the SOURCE_COMPATIBILITY and the TARGET_COMPATIBILITY constants are downgraded to 11 in order to allow the users to use the latest version of this library even in projects where the jdk11 is mandatory.

Updated the README with a brief explanation of the difference between the two flavours of this project.

The 'release' github action has a new job to build the javax flavour of
this project. This job has three main steps:
 - Replace all the jakarta imports and dependencies with the javax ones
 - Downgrade springframework dependency to the version 5.*
 - Using jdk 11 to build the project and publish it

The cold migration from jakarta to javax is done via a new bash script
`.github/replaceJakartaWithJavax.sh` that uses mainly the sed command to
perform the replacement operations.

In gradle.properties the SOURCE_COMPATIBILITY and the TARGET_COMPATIBILITY
constants are downgraded to 11 in order to allow the users to use the
latest version of this library even in projects where the jdk11 is mandatory.

Updated the README with a brief explanation of the difference between
the two flavours of this project.
@oliemansm
Copy link
Member

@federicorispo Could you merge the two snapshot workflows as well the same way you did with release? So that when a snapshot is published it also publishes one for javax.

@federicorispo
Copy link
Member Author

@oliemansm no problem, I will do it! What about tags? For now there is only one tag for both flavours: is it ok for you?

@oliemansm
Copy link
Member

Yeah now that it's on one branch again that sounds ok 👍🏻

- Refactored bash scripts to accept only javax flavour
- Removed snapshot-suffix.yml action
- Added test-javax jobs in release action
@oliemansm oliemansm merged commit 160ff2c into graphql-java-kickstart:master Jun 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants