-
Notifications
You must be signed in to change notification settings - Fork 18
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
[MCHANGES-439] Deprecate useJql #56
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we cen remove such preparing next major
and issue - MCHANGES-439?
We should also fix documentation - https://maven.apache.org/plugins/maven-changes-plugin/examples/customizing-jira-report.html |
good point on docs; done |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I still think that we can simply remove, even more that is not used in code.
Simply users will have a warning that use not existing parameter,
with deprecated they will have warning abut deprecation,
so will be similar from user perspective.
What specifically do you want to remove? We shouldn't take out the parameter without a deprecation cycle because it likely still exists in some folks' poms. |
Yes we should do a deprecate cycle for so minor versions in major version I hope we can simply remove parameter. But as you wish it can be deprecated. |
No description provided.