René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Cache integration between `actions/setup-java` and `actions/cache` / `actions/cache/restore`","articleBody":"**Description:**\r\nExpose `cache-primary-key` as an output to allow integration with `actions/cache`and `actions/cache/restore`.\r\n\r\n**Justification:**\r\nCaching rules differ according to the build tool used (mvn/sbt/etc), and I would like to leverage the logic already implemented on `actions/setup-java` to handle the specifics for each build tool.\r\n\r\nThat being said, I have dependent jobs that I would like to guarantee that the same cache is used by forcing the same cache key.\r\n\r\nI understand that any advanced cache usage should be done manually using `actions/cache`, but just exposing the cache key used by `actions/setup-java` as an output, like `cache-hit`, would make it possible to extend the functionality from `actions/setup-java`.\r\n\r\nAnother possibility would be for `actions/setup-java` not only to set an output with the cache key but also to accept an input cache-key, but I think this goes into the realm of \"should be done using actions/cache\".\r\n\r\n\r\n**Are you willing to submit a PR?**\r\n\r\nMy understanding is that a small change [here](https://github.com/actions/setup-java/blob/7a445ee88d4e23b52c33fdc7601e40278616c7f8/src/cache.ts#L113) to set an output, and to `action.yml` to declare the output, would suffice.\r\nI would be more than happy to submit a PR, but before doing so, I would like to check with the team to see if this aligns with the vision for the future.\r\n","author":{"url":"https://github.com/caquino","@type":"Person","name":"caquino"},"datePublished":"2024-02-14T13:41:11.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":2},"url":"https://github.com/597/setup-java/issues/597"}