Skip to content

[IMPROVEMENT] Upgrade gradle's required version #32

Closed

Description

@henryx

At the moment, the project is built using Gradle 5.6.4. According to this issue, this version cannot be used with Java greather than 11. This is a problem because it doesn't allow updating the Java version used for project development. therefore it is necessary to carry out the activities necessary to allow Gradle to be updated, in particular by rewriting the deprecated parts in the new versions. An alternative is change the build system (with Maven or other), but it is preferrable to adopt this way as extrema ration

Activity

  1. kLeZ commented on Apr 29, 2023

    @kLeZ

    Trying to help on this. Just forked.

  2. HomeOfTheWizard commented on Jun 8, 2023

    @HomeOfTheWizard

    Hi @henryx ,

    I have created the following PR #39, a minimum work just to unblock #22.

    Tested the unitTest all is working, however I realized that 3 integrationTests don't pass with the latest version of the Vault image because the API returns 204 instead of 200.
    I did not change the tests in case you use a specific version of the image in your CI environment.

    io.github.jopenlibs.vault.api.AuthBackendPkiTests > testRevocation FAILED
        junit.framework.AssertionFailedError at AuthBackendPkiTests.java:168
    io.github.jopenlibs.vault.api.AuthBackendPkiTests > testIssueCredential FAILED
        junit.framework.AssertionFailedError at AuthBackendPkiTests.java:100
    io.github.jopenlibs.vault.api.AuthBackendPkiTests > testIssueCredentialWithCsr FAILED
        junit.framework.AssertionFailedError at AuthBackendPkiTests.java:141
    

    But I think we must fix them and alway run the tests with the latest image of Vault.

    @kLeZ please continue feel free to continue your work in case you see other improvements or changes related to the new APIs of gradle. I am new to gradle so I may have missed some things.

  3. henryx commented on Jun 15, 2023

    @henryx
    CollaboratorAuthor

    @HomeOfTheWizard Thank you so much for you PR, I've merged it in mainline before check the CI result

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions