[
https://issues.apache.org/jira/browse/MCHANGES-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17900594#comment-17900594
]
ASF GitHub Bot commented on MCHANGES-439:
-----------------------------------------
slawekjaranowski commented on PR #56:
URL:
https://github.com/apache/maven-changes-plugin/pull/56#issuecomment-2495515129
> 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.
> Deprecate changes.useJql
> ------------------------
>
> Key: MCHANGES-439
> URL: https://issues.apache.org/jira/browse/MCHANGES-439
> Project: Maven Changes Plugin
> Issue Type: Task
> Reporter: Elliotte Rusty Harold
> Assignee: Elliotte Rusty Harold
> Priority: Minor
>
> /**
> * Use the JIRA query language instead of the JIRA query based on HTTP
> parameters. From JIRA 5.1 and up only JQL is
> * supported. JIRA 4.4 supports both JQL and URL parameter based queries.
> From 5.1.1 this is obsolete, since REST
> * queries only use JQL.
> *
> * @since 2.10
> */
> @Parameter(property = "changes.useJql", defaultValue = "false")
> private boolean useJql;
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
