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 thousands of old build versions > IS > > a nightmare. T

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
I just glanced through the current article but I suspect that this doesn’t work with POMs that have parent references where the version is the same as the project (e.g., the parent is the aggregate POM in the directory above each module). In my current projects, I would only have a single ver

Re: Maven & Continuous Delivery

2016-04-21 Thread Dan Tran
does it upload the pom with its version fully translated? Thanks -D On Thu, Apr 21, 2016 at 6:40 PM, Benson Margulies wrote: > On Thu, Apr 21, 2016 at 2:52 PM, Dan Tran wrote: > > Hi Benson > > > > Sounds promissing > > > > does it support jenkins env BUILD_NUM? > > I doubt it. I dislike Jenk

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: > https://axelfont

Re: Maven & Continuous Delivery

2016-04-21 Thread Benson Margulies
On Thu, Apr 21, 2016 at 2:52 PM, Dan Tran wrote: > Hi Benson > > Sounds promissing > > does it support jenkins env BUILD_NUM? I doubt it. I dislike Jenkins and avoid having anything to do with it. Feel free to make a PR. > does it push the actual version to maven repo at install/deploy time? if

Re: Why did the Maven Site Plugin 3.4.1 vanished

2016-04-21 Thread Hervé BOUTEMY
Hi, 3.4.1? This version never existed http://svn.apache.org/viewvc/maven/plugins/tags/ Didn't you look for 3.5.1? Regards, Hervé Le jeudi 21 avril 2016 23:52:25 Oliver B. Fischer a écrit : > Hi, > > I just recognized that version 3.4.1 of the Maven Site Plugin vanished > from Maven Central. D

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 build is a potential re

Why did the Maven Site Plugin 3.4.1 vanished

2016-04-21 Thread Oliver B. Fischer
Hi, I just recognized that version 3.4.1 of the Maven Site Plugin vanished from Maven Central. Does someone how why? Oliver -- N Oliver B. Fischer A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany P +49 30 44793251 M +49 178 7903538 E o.b.fisc...@swe-blog.net S oliver.b.fischer J oliv

Re: Maven & Continuous Delivery

2016-04-21 Thread Dan Tran
Hi Benson Sounds promissing does it support jenkins env BUILD_NUM? does it push the actual version to maven repo at install/deploy time? Thanks -Dan On Thu, Apr 21, 2016 at 4:00 AM, Benson Margulies wrote: > https://github.com/basis-technology-corp/auto-version-maven-extension > > On Sat, Ap

Re: Maven & Continuous Delivery

2016-04-21 Thread Benson Margulies
https://github.com/basis-technology-corp/auto-version-maven-extension On Sat, Apr 16, 2016 at 2:23 PM, Jeff Jensen wrote: >> >> Jason van Zyl also mentioned he was working on CD solution for Maven last >> year, not sure what the progress on this front. > > > Yes, I've been curious about the progr