[
https://issues.apache.org/jira/browse/MASSEMBLY-818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15338085#comment-15338085
]
Robert Scholte commented on MASSEMBLY-818:
------------------------------------------
Yes, I'm aware of your suggestion, though I don't like it. Upgrading to a new
major should always be done with care. When will we remove the exception?
3.0.1, 3.1.0? Problem stays the same if people come from 2.x and go the first
version which doesn't throw the exception anymore.
Maybe it is a bit too late, but Maven should be more critical when using
deprecated or unknown parameters and there should be an option to fail in such
case.
> 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.
> - classifier; instead the assemblyId (id in assembly xml) is used
> - descriptorId; instead use descriptorRefs
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
