Re: Maven and Continous Integration / Continous Delivery

2016-04-21 Thread Dan Tran
you can tag each build using JFrog Artifactory, so deletions are manageable -D On Thu, Apr 21, 2016 at 9:19 PM, Laird Nelson wrote: > On Thu, Apr 21, 2016 at 7:31 PM Robert Patrick > wrote: > > > I can tell you first-hand that deleting

Re: Maven and Continous Integration / Continous Delivery

2016-04-21 Thread Laird Nelson
On Thu, Apr 21, 2016 at 7:31 PM Robert Patrick wrote: > I can tell you first-hand that deleting thousands of old build versions IS > a nightmare. That's why we are using SNAPSHOTs and only switch to version > numbers for end of sprint builds. > +1 Best, Laird

RE: Maven and Continous Integration / Continous Delivery

2016-04-21 Thread Robert Patrick
To: Maven Users List Subject: Re: Maven and Continous Integration / Continous Delivery the big issue with that technique is that the pom deployed to maven repo, its version is the real version, will be maintaining nightmare -D On Wed, Apr 20, 2016 at 2:17 AM, Francois-Xavier Bonnet < franc

Re: Maven and Continous Integration / Continous Delivery

2016-04-21 Thread Dan Tran
the big issue with that technique is that the pom deployed to maven repo, its version is the real version, will be maintaining nightmare -D On Wed, Apr 20, 2016 at 2:17 AM, Francois-Xavier Bonnet < francois-xavier.bon...@centraliens.net> wrote: > Maybe this article could help: >

Re: Maven and Continous Integration / Continous Delivery

2016-04-21 Thread Francois-Xavier Bonnet
Maybe this article could help: https://axelfontaine.com/blog/dead-burried.html 2016-04-20 11:07 GMT+02:00 Hohl, Gerrit : > Hello everyone, :-) > > > > I'm currently sitting on the book "Continuous Delivery" written by Jez > Humble and David Farley. > > They write that each

RE: AW: Maven and Continous Integration / Continous Delivery

2016-04-20 Thread Robert Patrick
: Wednesday, April 20, 2016 7:54 AM To: Maven Users List Subject: AW: Maven and Continous Integration / Continous Delivery Hello, thanks Robert, thanks Stephen and thanks Irfan for your replies. Somehow it seems no easy to handle this. And it also seems to break the principals of that book in one point

AW: Maven and Continous Integration / Continous Delivery

2016-04-20 Thread Hohl, Gerrit
- Von: Robert Patrick [mailto:robert.patr...@oracle.com] Gesendet: Mittwoch, 20. April 2016 14:24 An: Maven Users List Betreff: Re: Maven and Continous Integration / Continous Delivery While having the developers update the POM may sound ok, it turns out to be problematic in practice when

Re: Maven and Continous Integration / Continous Delivery

2016-04-20 Thread Robert Patrick
the >> project A. Otherwise I will get problems in the IDE as it maybe don't >> realize that project B uses the project A which I currently have >> checked-out. Means if I do debugging I will always end up in the sources of >> the artifact downloaded from the artifact repository and not in the sou

Re: Maven and Continous Integration / Continous Delivery

2016-04-20 Thread Stephen Connolly
f I do debugging I will always end up in the sources of > the artifact downloaded from the artifact repository and not in the source > code of project A which I also have checked-out. > > Regards, > Gerrit > > -Ursprüngliche Nachricht- > Von: Stephen Connolly [mailto:stephen

Re: AW: Maven and Continous Integration / Continous Delivery

2016-04-20 Thread Robert Patrick
sources of the artifact > downloaded from the artifact repository and not in the source code of project > A which I also have checked-out. > > Regards, > Gerrit > > -Ursprüngliche Nachricht- > Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] &g

Re: Maven and Continous Integration / Continous Delivery

2016-04-20 Thread Irfan Sayed
the one which you have checked-out in your IDE. > > Regards, > Gerrit > > > -Ursprüngliche Nachricht- > Von: Hohl, Gerrit [mailto:g.h...@aurenz.de] > Gesendet: Mittwoch, 20. April 2016 12:08 > An: Maven Users List > Betreff: AW: Maven and Continous Integration

AW: Maven and Continous Integration / Continous Delivery

2016-04-20 Thread Hohl, Gerrit
have checked-out in your IDE. Regards, Gerrit -Ursprüngliche Nachricht- Von: Hohl, Gerrit [mailto:g.h...@aurenz.de] Gesendet: Mittwoch, 20. April 2016 12:08 An: Maven Users List Betreff: AW: Maven and Continous Integration / Continous Delivery Hello Stephen, thank you very much for your

AW: Maven and Continous Integration / Continous Delivery

2016-04-20 Thread Hohl, Gerrit
-Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Mittwoch, 20. April 2016 11:47 An: Maven Users List Betreff: Re: Maven and Continous Integration / Continous Delivery If I were doing this myself here is what I would do: I would use a

Re: Maven and Continous Integration / Continous Delivery

2016-04-20 Thread Stephen Connolly
If I were doing this myself here is what I would do: I would use a MRM that has staging support and setup a Jenkins Pipeline that starts by doing `mvn release:prepare release:perform -B -DpushChanges=false -DlocalCheckout=true "-DdevelopmentVersion=dev-SNAPSHOT" "-DreleaseVersion=${BUILD_ID}"

Maven and Continous Integration / Continous Delivery

2016-04-20 Thread Hohl, Gerrit
Hello everyone, :-) I'm currently sitting on the book "Continuous Delivery" written by Jez Humble and David Farley. They write that each build is a potential release candidate. And each build should be triggered by the check-in into the SCM. So far, so good. But how do I realize that in