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

set-property without newVersion property doesn't give a useful error message #315

Closed
smithkm opened this issue Oct 20, 2018 · 0 comments · Fixed by #667
Closed

set-property without newVersion property doesn't give a useful error message #315

smithkm opened this issue Oct 20, 2018 · 0 comments · Fixed by #667

Comments

@smithkm
Copy link

smithkm commented Oct 20, 2018

If the set-property goal is executed but newVersion isn't set (in my case I had set new.version instead) the execution simply fails without any useful error message. With the -X flag the error is shown to be a NullPointerException which doesn't give any idea what the problem is, Giving a useful error that included the name of the missing parameter would make this kind of problem far easier to resolve.

@github-actions github-actions bot added the Stale label Sep 29, 2021
@github-actions github-actions bot closed this as completed Oct 6, 2021
@slachiewicz slachiewicz removed the Stale label Oct 6, 2021
@slachiewicz slachiewicz reopened this Oct 6, 2021
jarmoniuk added a commit to jarmoniuk/versions-maven-plugin that referenced this issue Sep 3, 2022
…pty if the properties file is not provided
slawekjaranowski pushed a commit that referenced this issue Sep 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
2 participants