rmannibucau commented on pull request #90: URL: https://github.com/apache/maven-shade-plugin/pull/90#issuecomment-828131563
> removing the @Parameter annotation is the compromise that will let this PR be merged. Just the property value (you can keep it to get it configurable in the pom and have a properly documented default. > Thus removing the parameter helps newbies but irks experts. As explained before it is not really true. What about not adding a skip parameter but a skipClassified parameter which can have a property (hopefully you find a shorter name ;))? Issue is only about the default artifact, not all other executions. Would it make everyone happy? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
