Re: Continuous Delivery with Maven now possible?

Hi Dan, Can you point me to Karl's blog please? I looked for it, but can't seem to find it. Thanks! Eric On May 3, 2017 8:56 PM, "Dan Tran" wrote: > I am able to bring it to production with very small project with few > modules. Where I hook up jenkins build number with

Re: Continuous Delivery with Maven now possible?

http://blog.soebes.de/blog/2017/04/02/maven-pom-files-without-a-version-in-it/ On Thu, May 4, 2017 at 7:48 AM, Eric B wrote: > Hi Dan, > > Can you point me to Karl's blog please? I looked for it, but can't seem to > find it. > > Thanks! > > Eric > > On May 3, 2017 8:56 PM,

Re: Continuous Delivery with Maven now possible?

Hi Robert, On 04/05/17 21:55, Robert Patrick wrote: With 3.5, you can now use a variable *but* that variable > has to be accessible to the POM prior to finding its > parent so the only solution is to move the > version number outside the POM hierarchy and into a -D defined variable.

RE: Continuous Delivery with Maven now possible?

Hi Karl, If I define the revision property in the top-level POM, I cannot refer to it in the module POMs' elements *and* still retain the ability to build from the module directory, right? I tried this and it failed because it was unable to resolve the revision property variable.

Re: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

Hi, On 04/05/17 22:52, Justin Georgeson wrote: Also I believe the partial reactor switches don't work for Tycho builds. You mean -pl ..option I suppose? As far as I know Tycho is handling that at the wrong time of the maven build and furthermore handles in this relationship some other

RE: Continuous Delivery with Maven now possible?

The problem is that I really want to control the version number for a project from a single place. Ideally, this would be the element of the project's top-level POM. The problem is that there is no way to do this because the module POMs have to declare a parent element that can be resolved

Re: Continuous Delivery with Maven now possible?

Sorry was to fast with the send button... On 04/05/17 22:01, Karl Heinz Marbaise wrote: Hi Robert, On 04/05/17 21:55, Robert Patrick wrote: With 3.5, you can now use a variable *but* that variable has to be accessible to the POM prior to finding its parent so the only solution is to move

Re: Continuous Delivery with Maven now possible?

Hi, On 04/05/17 19:53, Eric Benzacar wrote: I've read through Karl's blog (http://blog.soebes.de/blog/ 2017/04/02/maven-pom-files-without-a-version-in-it/), and while I understand the approach, there is still one critical issue that bothers me. I think this actually reopens an old thread that

RE: Continuous Delivery with Maven now possible?

Hard to train developers to break old habits but thanks... :-) -Original Message- From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] Sent: Thursday, May 04, 2017 3:16 PM To: Robert Patrick; Maven Users List; i...@soebes.de Subject: Re: Continuous Delivery with Maven now possible? Hi

Re: Continuous Delivery with Maven now possible?

Hi Robert, Ah now I see the issue. If you have a multi module build you should use mvn -pl moduleToBuild clean install but from root location and don't change into the module directory cause this can't work like this. Kind regards Karl Heinz Marbaise On 04/05/17 22:08, Robert Patrick

RE: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

Also I believe the partial reactor switches don't work for Tycho builds. -Original Message- From: Robert Patrick [mailto:robert.patr...@oracle.com] Sent: Thursday, May 4, 2017 3:18 PM To: Maven Users List ; i...@soebes.de Subject: [EXTERNAL] RE: Continuous

Re: Continuous Delivery with Maven now possible?

How about everybody read their mail? (see below) On Thu, May 4, 2017 at 6:10 PM Curtis Rueden wrote: > Hi Dan, Karl & everyone, > > > See Karl's Blog > > Link, please? > […] > > > > On 03/05/17 20:39, Dan Tran wrote: > > > > > > > >> Hi > > > >> > > > >> I have been

Re: Continuous Delivery with Maven now possible?

Hi Dan, Karl & everyone, > See Karl's Blog Link, please? Regards, Curtis -- Curtis Rueden LOCI software architect - https://loci.wisc.edu/software ImageJ2 lead, Fiji maintainer - https://imagej.net/User:Rueden On Wed, May 3, 2017 at 7:54 PM, Dan Tran wrote: > I am able

RE: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

Yup :) -Original Message- From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] Sent: Thursday, May 4, 2017 4:52 PM To: Justin Georgeson ; Maven Users List ; i...@soebes.de Subject: Re: [EXTERNAL] RE: Continuous Delivery with Maven now

Re: Continuous Delivery with Maven now possible?

I've read through Karl's blog (http://blog.soebes.de/blog/ 2017/04/02/maven-pom-files-without-a-version-in-it/), and while I understand the approach, there is still one critical issue that bothers me. I think this actually reopens an old thread that circulated on this list a few months ago, but

Re: Continuous Delivery with Maven now possible?

a couple corrections: * for Jenkins freeslyle, one can create a job parameter similiar to this format revision=x.y.x-${BUILD_NUMBER} to override the default maven version * for Jenkins Pipeline, the revision handling is part of projec's t Jenkinsfile The original blog is here

Re: Continuous Delivery with Maven now possible?

for trace-ability, i add this to top level pom org.codehaus.mojo buildnumber-maven-plugin this-has-scm-info-for-tagging-and-tracability-purpose prepare-package create-metadata

Re: [EXTERNAL] RE: Continuous Delivery with Maven now possible?

is flatten-maven-plugin threadsafe? if not, we have a problem with large project where multhreaded build is a must have maven 3.5 displays a warning on flatten-maven-plugin not thread safe Thanks -D On Thu, May 4, 2017 at 2:52 PM, Karl Heinz Marbaise wrote: > Hi, > > On

Re: Continuous Delivery with Maven now possible?

Hi, Thanks for the detailed response. You have a lot of great points in there, and most of them I agree with (and partially implement already). As a CI/CD server, I'm using Jenkins and constantly trying to find better ways to do things. > First if you make a release your release process must