Skip to content

Conversation

@anton-haubner-sonarsource
Copy link
Contributor

@anton-haubner-sonarsource anton-haubner-sonarsource commented Nov 4, 2025

SONARJAVA-5829

WIP API design, not final.

@hashicorp-vault-sonar-prod hashicorp-vault-sonar-prod bot changed the title Add internal API for accessing classpath information SONARJAVA-5829 Add internal API for accessing classpath information Nov 4, 2025
@anton-haubner-sonarsource anton-haubner-sonarsource force-pushed the ahbnr/add-classpath-resolution-to-internal-api branch from a424511 to a2a71be Compare November 4, 2025 14:56
* This is an extension that is instantiated per-project (per-module in Maven terms) and can be injected when needed.
*/
@ScannerSide
public interface ClasspathResolver {

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was thinking about adding the @org.sonar.java.annotations.Beta annotation here, it's an explicit way to say "use with care, not fully supported"

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In an earlier version, I made a copy of @Beta and called it @Internal, to not only say that the API might change, but also to say that it is not supposed to be accessed by Sensors outside of the SonarSource org.

Does the @Beta annotation have any practical effect beyond documentation purposes?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it's for documentation only, I like the idea of having @Internal, we could go for that

@sonarqube-next
Copy link

sonarqube-next bot commented Nov 5, 2025

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants