We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Since 2.3.0, the setup-java GitHub actions have a built-in cache mechanism which simplifies configuration of the workflow.
It will simplify this: https://github.com/com-pas/contributing/blob/e0e6ccbc2160d9ad05cf0dadea5faa33a977d8c1/docs/GITHUB_ACTIONS.md?plain=1#L147
see also com-pas/contributing#62
User Story
As a com-pas maintainer
I want to have the simpler code to maintain
So that I can develop faster
Acceptance criteria
Please describe the initial acceptance critera.
Same feature level with less and simpler code
The text was updated successfully, but these errors were encountered:
chore(305): use built-in Maven cache mechanism of setup-java GitHub
49dc4c2
Action fixes com-pas#305 Signed-off-by: Aurélien Pupier <[email protected]>
f799421
Successfully merging a pull request may close this issue.
Since 2.3.0, the setup-java GitHub actions have a built-in cache mechanism which simplifies configuration of the workflow.
It will simplify this: https://github.com/com-pas/contributing/blob/e0e6ccbc2160d9ad05cf0dadea5faa33a977d8c1/docs/GITHUB_ACTIONS.md?plain=1#L147
see also com-pas/contributing#62
User Story
As a com-pas maintainer
I want to have the simpler code to maintain
So that I can develop faster
Acceptance criteria
Please describe the initial acceptance critera.
Same feature level with less and simpler code
The text was updated successfully, but these errors were encountered: