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

also trace back to my note on this thread, I use buildnumber-m-p for build definition and traceability purpose -D On Tue, May 9, 2017 at 7:46 PM, Bernd Eckenfels wrote: > You can use the Jenkins environment variable for the build number of a job > as a read-only

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

You can use the Jenkins environment variable for the build number of a job as a read-only parameter. And I think ${env.BUILD_NUMBER} should also work on the command line. Gruss Bernd -- http://bernd.eckenfels.net From: Eric Benzacar Sent:

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

Thanks for the detailed explanation. A couple of questions come to mind: 1) can the element only contain a variables, or can it be a combination of fixed + variable? for instance: 1.2-${changelist} I see in your examples that it only is a combination of variables with no additional text. 2)

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

Hi I am in the process of switching our 250+ modules to version-less poms. There are 2 phases 1. Activated flatten poms. Every thing seems ok, except those external modules which depends on a full pom.xml at maven repo. This is fixable 2. Switched versionless using ${revision} at a dev

maven shade multi module setup

Hi, I am facing a problem with correctly setting up shading in a multi module maven project. Currently all the original code is removed / filtered out from the user-jar even though. http://stackoverflow.com/questions/43873608/maven-shade-in-multi-project-setup-filtering-too-much Looking forward

How to use global checkstyle.xml that have SuppressionsFilter included

So here in my case I want use remote checkstyle file located in https://github.com/openmrs/openmrs-core/blob/master/checkstyle.xml?#L45 in another project. In my project's pom I have config location set as follows: