[
https://issues.apache.org/jira/browse/MASSEMBLY-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15331212#comment-15331212
]
Anders Hammar edited comment on MASSEMBLY-818 at 6/15/16 6:14 AM:
------------------------------------------------------------------
Not sure if we could somehow help users upgrading detect if this affects their
build.
One idea would be to keep the params and break the build if used. In MJAR-210
we kept the param but if used it would throw an exception.
was (Author: afloom):
Not sure if we could somehow help users upgrading detect if this affects their
build.
One idea would be to keep the params and break the build if used. But I would
rather like to get rid of the params from the docs but I'm not sure that is
possible then as it is generated.
> Remove deprecated parameters for the single goal
> ------------------------------------------------
>
> Key: MASSEMBLY-818
> URL: https://issues.apache.org/jira/browse/MASSEMBLY-818
> Project: Maven Assembly Plugin
> Issue Type: Improvement
> Reporter: Anders Hammar
> Priority: Minor
> Fix For: 3.0.0
>
>
> For the 3.0.0 release, we should clean up (remove) parameters in the single
> goal that are marked as deprecated.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
