> IMO: Everytime any of the project's files is touched version number in pom > should be increased.
I think the issue is that the plugin tests are actually a subproject that are not used in the resulting artifact - so I don't think changes in them should increase the version of the plugin or changes.xml. Michal's right - looking at changes.xml should indicate the need for a release. Changes to tests and code refactoring/reformatting, don't indicate a need to release, nor do they assist the user deciding if they should upgrade. But project.xml should be bumped for some of these things because the resulting artifact will change. So in summary I think: - bump project.xml version whenever the source code/meta data/dependencies change that will affect the resultant artifact - add changes.xml for any functional changes to the project - bugfixes, additions, etc - but not internal changes. This might include refactoring if it affects a public API, but not if it changes a private function. - use the changelog from CVS etc to see what other non-functional changes have happened such as reformatting, additional test cases, changes to documentation, etc. changes.xml is a bit of a judgement call really. Does this sound ok? Michal, I don't think lack of information is the problem with Maven at the moment - it is the quality of it. It has gaps, but it is also incorrect and distributed across mailing lists/wikis/sites/etc. Quality documentation will be quantity of doco any day :) - Brett --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
