Vincent Siveton wrote:
IMHO it will be an overhead for nothing...
Well, enabling the doc filtering is a one-time task and I wouldn't say it's for nothing. The problem I see with those version-less POM snippets is that users just use them as is, without further thought. Nobody is going to read each and every doc page, people do some googling to find a solution for their task, grab the XML bits of interest and expect their builds to work. That is to say I believe this single page where we recommend to lock down the plugin version will easily be overlooked. From JIRA and IRC I can't fight the feeling that the practice of locking down plugin versions is still not too common among users so I believe it's valuable to promote this practice by having all our docs demonstrate it.
Last but not least, there are plans to remove auto-versioning for POM plugins in future Maven versions. That means version-less plugin blocks in the POM will be rejected as an invalid model, i.e. the example snippets will not only be bad practice, they will not work at all. If users already fill JIRA tickets for outdated plugin versions in the examples, I would imagine they do the same for non-working examples as well...
Benjamin --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
