RE: when to touch changes.xml/project.xml version RE: cvs commit: maven-plugins/java project.xml

[Brett Porter <br...@apache.org>]

Yeah, you're right - I got a bit side tracked from the original point. I was
only thinking that project.xml of a plugin doesn't need to change when the
plugin-test is modified as the plugin-test is a separate project altogether.

I definitely think changes.xml only needs to have user-needs-to-know, hopefully
non-technical, changes added though, regardless of what in the project is changing.

Cheers,
Brett

Quoting Maczka Michal <mi...@imtf.ch>:

> 
> 
> > -----Original Message-----
> > From: Vincent Massol [mailto:vmassol@pivolis.com]
> > Sent: Thursday, July 01, 2004 7:46 AM
> > To: 'Maven Developers List'
> > Subject: RE: when to touch changes.xml/project.xml version RE: cvs
> > commit: maven-plugins/java project.xml
> > 
> > 
> > Brett,
> > 
> > Why not take the easy route, that is, if not already bumped 
> > then bump the
> > plugin version for whatever change you're bringing. It just won't be
> > released before there are any significant changes to it.
> > 
> +1
> 
> Simple and clear rule.
> 
> I would add that new entry in changes.xml file must be added to explain what
> already happen and why the version was bumped.
> Even (I think it is not good idea) if somebody will find some information in
> this file irrelevant for
> end users - they still can be removed during the release process.
> 
> Michal
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
> 



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org