> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 02, 2004 8:52 AM
> To: 'Maven Developers List'
> Subject: RE: when to touch changes.xml/project.xml version
> RE: cvs commit: maven-plugins/java project.xml
>
> -Original Message-
> From: Carlos Sanchez [mailto:[EMAIL PROTECTED]
> Sent: vendredi 2 juillet 2004 00:08
> To: 'Maven Developers List'
> Subject: RE: when to touch changes.xml/project.xml version RE: cvs commit:
> maven-plugins/java project.xml
>
> I agree, I don't like doing things twice ;)
>
> One question about SNAPSHOT, when you decide to increase version number
> should it be:
> new.version.number-SNAPSHOT
>
> This generates artifactId + version + snapshot info.
> Is this ok or should be artifactId + snapshot info?
>
During the dev
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> Sent: Thursday, July 01, 2004 9:52 PM
> To: 'Maven Developers List'
> Subject: RE: when to touch changes.xml/project.xml version
> RE: cvs commit: maven-plugins/java project.xml
>
> -Original Message-
> From: Maczka Michal [mailto:[EMAIL PROTECTED]
> Sent: jeudi 1 juillet 2004 09:52
> To: 'Maven Developers List'
> Subject: RE: when to touch changes.xml/project.xml version RE: cvs commit:
> maven-plugins/java project.xml
>
ay, 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, i
> -Original Message-
> From: Vincent Massol [mailto:[EMAIL PROTECTED]
> 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
>
&g
[EMAIL PROTECTED]
> Sent: jeudi 1 juillet 2004 07:39
> To: Maven Developers List
> Subject: Re: when to touch changes.xml/project.xml version RE: cvs commit:
> maven-plugins/java project.xml
>
> It's a tough call. It may or may not change the resultant artifact (eg if
> you
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 ir
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
doe
> 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 chang
> -Original Message-
> From: Dion Gillard [mailto:[EMAIL PROTECTED]
> Sent: Wednesday, June 30, 2004 12:25 PM
> To: Maven Developers List
> Subject: Re: cvs commit: maven-plugins/java project.xml
>
>
> Oh well,
>
> if we can come up with something cons
he usage of changes.xml
>
> -Vincent
>
>
>
> > -Original Message-
> > From: Dion Gillard [mailto:[EMAIL PROTECTED]
> > Sent: mercredi 30 juin 2004 08:34
> > To: Maven Developers List
> > Subject: Re: cvs commit: maven-plugins/java project.xml
>
-Original Message-
> > > From: Dion Gillard [mailto:[EMAIL PROTECTED]
> > > Sent: mercredi 30 juin 2004 06:29
> > > To: Maven Developers List
> > > Subject: Re: cvs commit: maven-plugins/java project.xml
> > >
> > > Done.
> > >
>
i.e
> changes that interest the plugin users). For all other changes we have the
> changelog report.
>
> Thanks
> -Vincent
>
>
>
> > -Original Message-
> > From: Dion Gillard [mailto:[EMAIL PROTECTED]
> > Sent: mercredi 30 juin 2004 06:29
>
i 30 juin 2004 06:29
> To: Maven Developers List
> Subject: Re: cvs commit: maven-plugins/java project.xml
>
> Done.
>
> I'm assuming from this that any changes to the plugin tests is not to
> be recorded other than in the commit message, and that this includes
> adding
Done.
I'm assuming from this that any changes to the plugin tests is not to
be recorded other than in the commit message, and that this includes
adding plugin test projects as well.
Is this right?
On Wed, 30 Jun 2004 12:05:35 +1000, Dion Gillard <[EMAIL PROTECTED]> wrote:
>
> I'm happy to go ba
I'm happy to go back and remove them.
Let me know if u want it done.
On Wed, 30 Jun 2004 10:08:19 +1000, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> dIon,
>
> Bumping the version of the plugin because the test changed seems backwards to
> me. Isn't that why a plugin test has a project of its ow
dIon,
Bumping the version of the plugin because the test changed seems backwards to
me. Isn't that why a plugin test has a project of its own?
Probably likewise for the changes entry. I don't believe non-functional changes
should go in changes.xml.
Cheers,
Brett
Quoting [EMAIL PROTECTED]:
> di
19 matches
Mail list logo
