It's a tough call. It may or may not change the resultant artifact (eg if you change plugin.jelly's formatting...), so its better to err on the side of incrementing it.
I don't usually reorganise those things for the sake of it though - its usually at the same time as doing other changes so its irrelevant. Personally, I'd prefer not to have the version in the CVS version of the POM at all (or ignore it) and insert it into the deployed one at release time. That way its not a problem :) - Brett Quoting Dion Gillard <[EMAIL PROTECTED]>: > On Thu, 1 Jul 2004 12:49:50 +1000, Brett Porter <[EMAIL PROTECTED]> wrote: > > > So in summary I think: > > - bump project.xml version whenever the source code/meta data/dependencies > > change that will affect the resultant artifact > > So in this case, extrapolating onto Maven, fixing junit test cases > doesn't bump project.xml? Ditto code cleanup (checkstyle, imports) > etc. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
