OK that one is done now r1039453...
I'll see what the story is about pushing a release of m-r-p soonish...
Last step is the v-m-p...
-Stephen
On 25 November 2010 16:14, Stephen Connolly wrote:
> http://jira.codehaus.org/browse/MRELEASE-621 will be needed to get the
> hooks in place for v-m-p.
http://jira.codehaus.org/browse/MRELEASE-621 will be needed to get the hooks
in place for v-m-p... once I have that done (and pushed a m-r-p release)
then I will do the v-m-p stuff (assuming I have got v-m-p's integration
tests portable by then!)
-Stephen
On 24 November 2010 20:02, Stephen Connol
That's an enhancement to versions-maven-plugin
This is the hook for deployment (aka shipping)
- Stephen
---
Sent from my Android phone, so random spelling mistakes are a direct result
of using swype to type on the screen
On 24 Nov 2010 18:45, "Yanko, Curtis" wrote:
I though the idea we talked
tanding, to really embrace CD, there would have to be no
>difference between a snapshot and a release.
> -Original Message-
> From: jhumble [mailto:j...@jezhumble.net]
> Sent: Wednesday, November 10, 2010 12:47 PM
> To: users@maven.apache.org
> Subject: Re: RE: Continuo
gt; think would be happening in the near future.
>>
>> > -Original Message-
>> > From: Stephen Connolly [mailto:[hidden
>> > email]<http://user/SendEmail.jtp?type=node&node=3258691&i=0>]
>>
>> > Sent: Wednesday, November 10, 20
architecture of maven which I don't
> think would be happening in the near future.
>
> > -Original Message-
> > From: Stephen Connolly [mailto:[hidden
> > email]<http://user/SendEmail.jtp?type=node&node=3258691&i=0>]
>
> > Sent: Wednesday,
don't think would be
happening in the near future.
> -Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> Sent: Wednesday, November 10, 2010 8:29 AM
> To: Maven Users List
> Subject: Re: RE: Continuous Delivery and Maven
>
> Imho
Imho taking a snapshot artefact and renaming as a release artefact and
pushing to the remote repo will never be supported by maven, but my
ship-maven-plugin (not ready for publishing yet) and some extra mojos added
to versions-maven-plugin should enable CD in a way that is in keeping with
the "mave
Stephen's solution makes sense to me. It doesn't try to conflate the meaning
of SNAPSHOTs and it retains the metadata in trunk that keeps everything in
the Maven build instead of relying on an outside tool.
Anyone see any issues with this approach? I think I like it from what I
understand so far.
: Tuesday, November 09, 2010 4:10 PM
To: Maven Users List
Subject: Re: RE: Continuous Delivery and Maven
But if we do it my way, the tag has the resolved versions, while trunk
keeps the ranges... Best of all worlds ;-)
On 9 Nov 2010 16:21, "Yanko, Curtis" wrote:
Because I thought we want t
But if we do it my way, the tag has the resolved versions, while trunk keeps
the ranges... Best of all worlds ;-)
On 9 Nov 2010 16:21, "Yanko, Curtis" wrote:
Because I thought we want to keep the version ranges in SCC for developers
and just package the POM fully versioned for that build.
___
Then I'm not sure you get it
On 8 Nov 2010 17:21, "Thiessen, Todd (Todd)" wrote:
> Except you won't know until you go to start up CD that you CD process
> got broken.
Why wouldn't your CI build tell you? You can test everything with your CI
build. No need to mandate going to a customer server t
12 matches
Mail list logo
