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

buildFileName parameter does not allow full control over build file name #4

Open
mseaton opened this issue Dec 2, 2024 · 0 comments

Comments

@mseaton
Copy link

mseaton commented Dec 2, 2024

The plugin accepts a configuration parameter named buildFileName. I would expect this to allow one to configure the exact file name that should be created that contains the dependency report information, but this is not the case. Instead, this is given a fixed suffix of -dependencies.txt.

So if I pass in a buildFileName of dependencies.properties, then the resulting filename that is produced is named dependencies.properties-dependencies.txt. I would expect the file name is just named dependencies.properties.

@rbuisson FYI

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

No branches or pull requests

1 participant