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

metadata-copy should follow recommendation #579

Closed
fniephaus opened this issue Mar 6, 2024 · 2 comments
Closed

metadata-copy should follow recommendation #579

fniephaus opened this issue Mar 6, 2024 · 2 comments
Labels
bug Something isn't working

Comments

@fniephaus
Copy link
Member

On the GraalVM website, we recommend to put metadata into directory following this pattern:

foo.jar has its configurations in META-INF/native-image/foo_groupID/foo_artifactID
bar.jar has its configurations in META-INF/native-image/bar_groupID/bar_artifactID

It seems that the metadata-copy copies metadata into just /META-INF/native-image.
Would be great if we could adjust it so that it follows our recommendation.

@vjovanov
Copy link
Member

@dnestoro is this issue fixed?

@dnestoro
Copy link
Collaborator

Kind of... for gradle we are just suggesting (in our docs) where should user copy metadata files (and we won't have default value for it in the plugin implementation), while maven has actual default directory for metadataCopy task.

So this issue can be closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants