[
https://jira.codehaus.org/browse/MCHECKSTYLE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=361048#comment-361048
]
Herve Boutemy commented on MCHECKSTYLE-275:
-------------------------------------------
notice the parameters are not available in aggregate report, which was added in
maven-checkstyle-plugin 2.8
this confirms that there is a really good chance nobody uses old parameters
> remove old deprecated parameters from report
> --------------------------------------------
>
> Key: MCHECKSTYLE-275
> URL: https://jira.codehaus.org/browse/MCHECKSTYLE-275
> Project: Maven Checkstyle Plugin
> Issue Type: Task
> Components: checkstyle:checkstyle
> Affects Versions: 2.13
> Reporter: Herve Boutemy
> Priority: Minor
>
> there are a bunch of parameters that are deprecated since 2005 (I don't even
> tried to find the version form the plugin: it was before 2.0):
> - format: Use configLocation instead
> - propertiesFile: Use propertiesLocation instead
> - propertiesURL: Use propertiesLocation instead
> - headerFile: Use headerLocation instead
> - suppressionsFile: Use suppressionsLocation instead
> - packageNamesFile: Use packageNamesLocation instead
> removing these will clean up source code
> in fact, we should have a general policy for parameter deprecation:
> 1. add a warning when detecting deprecated parameter usage exactly at the
> same time as deprecating the parameter,
> 2. a few versions later (no hurry), change warning to failure
> 3. then a few versions later remove the code
> for this case, I intend to go to step 3 directly if nobody is against it
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
