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

./gradlew check fails with JDK11 #5599

Open
izeye opened this issue Oct 19, 2024 · 3 comments
Open

./gradlew check fails with JDK11 #5599

izeye opened this issue Oct 19, 2024 · 3 comments
Labels
build A change in our build-system type: task A general task

Comments

@izeye
Copy link
Contributor

izeye commented Oct 19, 2024

./gradlew clean check fails as follows:

...
* What went wrong:
Could not determine the dependencies of task ':micrometer-osgi-test:test'.
> Could not create task ':micrometer-osgi-test:testingBundle'.
   > Could not create task of type 'Bundle'.
      > Could not create an instance of type aQute.bnd.gradle.BundleTaskExtension.
         > Cannot change attributes of configuration ':micrometer-osgi-test:compileClasspath' after it has been locked for mutation
...
@jonatan-ivanov
Copy link
Member

Thank you for letting us know!
I was able to repro it even with simply ./gradlew check. ./gradlew test is ok though. It seems the order of configuring things is different depending on which task you want to execute.

@jonatan-ivanov jonatan-ivanov added build A change in our build-system type: task A general task labels Oct 19, 2024
shakuzen added a commit that referenced this issue Oct 22, 2024
@shakuzen
Update build command example
c04ffec 
See #5599
@shakuzen
Copy link
Member

Until this is fixed, I have been using the default task (which is build) via ./gradlew, which will also run the check task. I've updated the contributing guide to not suggest using ./gradlew check for now.

@ngocnhan-tran1996 ngocnhan-tran1996 mentioned this issue Dec 7, 2024
Merged
@shakuzen shakuzen changed the title "./gradlew clean check" fails ./gradlew check fails with JDK11 Jan 22, 2025
shakuzen pushed a commit that referenced this issue Jan 22, 2025
@ngocnhan-tran1996
Fix gradle check with JDK17+ (#5735)
826166a 
The new version of the BND plugin does not have the same issue when running the `check` command, but the new version of the BND plugin requires JDK 17, so we can't use it when JDK 11 is being used to build the project.

See gh-5599
@shakuzen
Copy link
Member

I updated the issue title to reflect this is only a problem with JDK 11 with #5735 having been merged.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
build A change in our build-system type: task A general task
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@izeye @jonatan-ivanov @shakuzen