[prev in list] [next in list] [prev in thread] [next in thread] 

List:       maven-dev
Subject:    Re: Maven Release Version Policy
From:       Robert Scholte <r.f.scholte () hisphone ! nl>
Date:       2015-10-31 20:16:39
Message-ID: 8u36u4gwsqgfrmxq870f9i2m.1446322599757 () email ! android ! com
[Download RAW message or body]

[Attachment #2 (text/plain)]

I'm probably the only one who could answer that, although I can't recall this \
question. yes,some handling of version specific parts have been improved,but this \
looks like regression to me. I might have misunderstood the issue.

Robert(cruising down highway 1)


Verzonden vanaf Samsung Mobile.

-------- Oorspronkelijk bericht --------
Van: Stephen Connolly
Datum:31-10-2015 12:16 (GMT-08:00)
Aan: Maven Developers List
Onderwerp: Re: Maven Release Version Policy

On Saturday 31 October 2015, Hervé BOUTEMY <herve.boutemy@free.fr> wrote:

> if there is a regression, why not just open a Jira issue and fix it?


IIRC when I pointed out the bug 6-9 months ago Robert or somebody said that
the new behaviour was by design...


> 
> I had a look at code, and it seems there is not any unit test against
> default
> version policy
> 
> Regards,
> 
> Hervé
> 
> Le samedi 31 octobre 2015 17:41:45 Stephen Connolly a écrit :
> > On Saturday 31 October 2015, Hervé BOUTEMY <herve.boutemy@free.fr
> <javascript:;>> wrote:
> > > I don't know what "Cloudbees conventions" are, and how they are
> superior
> > > to
> > > everything else = what I understand from the README
> > 
> > I jusj had to put a readme quickly.
> > 
> > It is basically increment the least significant segment (which is what
> the
> > release plugin *used* to do) I added some extra bits like if the last
> > segment is -alpha then that goes to -beta-1 and -beta goes to -rc-1
> > 
> > In any case if moving the code to ASF I would be removing the CloudBees
> > references
> > 
> > > if we were able to better describe this policy, and compare different
> > > policies,
> > > that would give a meaning to adding more and providing them by default
> in
> > > the
> > > plugin to let users configure in the plugin policy to match the
> effective
> > > convention they use
> > > 
> > > So, as the code currently says "cloudbees convention" without saying
> what
> > > it
> > > is, but just that it fixes everything (which is an assertion I can't
> > > trust), I
> > > don't see the point in integrating it in the plugin
> > > 
> > > but I see the interest in adding more version policies, describing
> them in
> > > a
> > > neutral way (= strictly what they do), to let end users choose an
> > > implementation matching their need (ie their effective convention)
> > > 
> > > Regards,
> > > 
> > > Hervé
> > > 
> > > Le vendredi 30 octobre 2015 12:16:35 Stephen Connolly a écrit :
> > > > Hey, so...
> > > 
> > > > Do we want to accept this implementation I knocked together:
> > > 
> https://github.com/CloudBees-community/cloudbees-maven-release-version-pol
> > > ic>
> > > > y
> > > > 
> > > > If not I'm fine leaving it where it is... but I can get it donated to
> > > > the ASF if there is interest
> > > > 
> > > > -Stephen
> > > > 
> > > > ---------------------------------------------------------------------
> > > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> <javascript:;> <javascript:;>
> > > > For additional commands, e-mail: dev-help@maven.apache.org
> <javascript:;>
> > > 
> > > <javascript:;>
> > > 
> > > 
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> <javascript:;> <javascript:;>
> > > For additional commands, e-mail: dev-help@maven.apache.org
> <javascript:;> <javascript:;>
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org <javascript:;>
> For additional commands, e-mail: dev-help@maven.apache.org <javascript:;>
> 
> 

-- 
Sent from my phone



[prev in list] [next in list] [prev in thread] [next in thread]