closure-compiler-unshaded v20240317 embeds jakarta.annotation-api

[tmortagne]

It can cause some conflicts when you depend on both closure-compiler-unshaded and jakarta.annotation-api directly or through other dependencies.

I would have expected it to be a dependency, along with the others declared in the pom file.

[brad4d]

Thanks for pointing this out.
We're unlikely to do anything about it immediately,
but I expect we will fix it before doing another release.

[tmortagne]

Thanks @brad4d, that's definitely good enough for me 🙂

[gkdn]

@tmortagne Do you know if this has regressed in the latest release?

[niloc132]

Yes, it appears this is a regression in the latest release:

• https://repo1.maven.org/maven2/com/google/javascript/closure-compiler-unshaded/v20231112/closure-compiler-unshaded-v20231112.jar doesn't have these javax.annotation files, but
• https://repo1.maven.org/maven2/com/google/javascript/closure-compiler-unshaded/v20240317/closure-compiler-unshaded-v20240317.jar does

[tmortagne]

Yes, as detailed by @niloc132 and as I should have mentioned a bit more explicitly in the issue description, it's indeed a regression from v20231112.

[gkdn]

4bf1cb0 will fix the issue in the next release.

[mflorea]

Are there any plans for a new release to fix this issue? It's been one year since it was reported... Maybe you just need to publish the released artifacts on Maven Central. I see 7 published releases for 2023, only one for 2024 and none for 2025 so far on https://central.sonatype.com/artifact/com.google.javascript/closure-compiler-unshaded . At the same time I see very recent tags at https://github.com/google/closure-compiler/tags . Thanks.

[brad4d]

@lauraharker implemented the creation of the tags for each of our internal-to-Google releases.
@jDramaix is working on automation that will use those tags for the next and future releases to Maven.

[lauraharker]

Update: we've pushed a new Maven release - v20250402.