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.

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

Expose artifact information in DirectoryConfiguration #665

Open
snicoll opened this issue Jan 2, 2025 · 0 comments · May be fixed by #667
Open

Expose artifact information in DirectoryConfiguration #665

snicoll opened this issue Jan 2, 2025 · 0 comments · May be fixed by #667
Labels
enhancement New feature or request

Comments

@snicoll
Copy link
Collaborator

snicoll commented Jan 2, 2025

Is your feature request related to a problem? Please describe.
DirectoryConfiguration is the API level object that one can interact as a result of a search in the repository.

The object exposes the path, as well as high-level method to copy the metadata to a target location, for the purpose of creating the necessary metadata based on input dependencies.

The problem right now is that, while the public constructor of the object takes a GAV, it is not exposed. As a user of the API you can't say to which artifact a DirectoryConfiguration relates to.

Describe the solution you'd like
Getters for the groupId, artifactId, and version. This will help reporting tool that provides feedback to the user regarding the dependencies that were managed successfully by the repository.

Describe alternatives you've considered
Reflection (but, no).

@snicoll snicoll added the enhancement New feature or request label Jan 2, 2025
melix added a commit to melix/native-build-tools that referenced this issue Jan 8, 2025
melix added a commit to melix/native-build-tools that referenced this issue Jan 8, 2025
@melix melix linked a pull request Jan 8, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant