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 #139 - "Can't find license-maven-plugin" (#1) #364

Closed
wants to merge 1 commit into from

Conversation

AndyGee
Copy link
Contributor

@AndyGee AndyGee commented Jan 15, 2020

Remove the POM plugin definition (which is what actually validates thi fix) - This is the test.
Use the PluginDescriptor so that the POM is not used/parsed to find the artifact.
Use the project properties for the invoker.

* Fix mojohaus#139 - "Can't find license-maven-plugin"

Use the PluginDescriptor.
Most painful checkstyle.
@AndyGee
Copy link
Contributor Author

AndyGee commented Jan 15, 2020

The issue was closed, but still exists.

It should not be required to define the plugin in the POM just to run the plugin from the command line,

@AndyGee AndyGee closed this Jan 16, 2020
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.

"Can't find license-maven-plugin" in 1.16 if plugin isn't configured in the POM
1 participant