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

Fix: Allow setting of outputDir and reportfileName (dependencyUpdates) #36

Merged
merged 1 commit into from
Oct 25, 2019

Conversation

usr42
Copy link
Contributor

@usr42 usr42 commented Oct 24, 2019

This fixes issue #33

Copy link
Owner

@patrikerdes patrikerdes left a comment

Choose a reason for hiding this comment

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

This looks great. Could you please update the README as well?

}

private static String ensureOutputDirIsAbsolute(String outputDir, Project project) {
if (!outputDir.startsWith('/')) {
Copy link
Owner

Choose a reason for hiding this comment

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

This will not work for Windows, right? (I would like for the plugin to work on Linux, macOS and Windows)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Good point. I now use Paths.get(outputDir).isAbsolute().
gradle check is currently running. I'll commit and push afterwards.

@usr42
Copy link
Contributor Author

usr42 commented Oct 25, 2019

This looks great. Could you please update the README as well?

What should I add to the README? That changing the outputDir and reportfileName for the dependencyUpdates plugin is supported?
How to change these values is part of the dependency update plugin documentation

@patrikerdes
Copy link
Owner

Ah sorry, I though there were new flags introduced. LGTM.

@patrikerdes patrikerdes merged commit 1e99e44 into patrikerdes:master Oct 25, 2019
@patrikerdes
Copy link
Owner

Sorry, I was confused and merged prematurely 😫

@usr42
Copy link
Contributor Author

usr42 commented Oct 25, 2019

No problem. I'll open a new PR.

@usr42 usr42 mentioned this pull request Oct 25, 2019
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