Hi Patrick,
> Would like to see the build version passed as a parameter so the pom
> file does not get changed during the build.
Definitely. You can use buildnumber-maven-plugin [1, 2] to embed your SCM
revision in the JAR. For an actual build number, you can pass it as a
parameter from your CIS (e.g., Jenkins uses ${BUILD_NUMBER}).
-Curtis
[1] http://mojo.codehaus.org/buildnumber-maven-plugin/
[2] Sample configuration:
https://github.com/scijava/scijava-common/blob/a7f2089ccd3f1451b75bd0170b16d399aa73cb9c/pom-scijava/pom.xml.
Search for "buildnumber" for all the important bits.
On Tue, Feb 12, 2013 at 12:01 PM, Patrick Haggerty <[email protected]>wrote:
> Here are the steps in my proccess:
>
> Edit code,
> Local build and test,
> Check code in,
> Apply Label to all files in my application,
> Request Build based on label using Corporate Build system. (It gets code
> based on the label and builds it, packages it and deploys it to Nexus then
> to the Target App WAS servers.
>
>
> During this process the pom file gets changed to satisfy the build #.
> Now the POM files is different from the one that has been labeled.
> Audit does not like the fact that the pom file changes during the build.
> Would like to see the build version passed as a parameter so the pom file
> does not get changed during the build.
>
> Thanks,
>
> PDH
>
>
> On Tue, Feb 12, 2013 at 12:36 PM, Wayne Fay <[email protected]> wrote:
>
> > > Let's say I make a label on my application and I build that application
> > > based on that label.
> >
> > What does "make a label on my application" mean? Are you talking about
> > tagging a build in source code?
> >
> > > I still need to modify the POM file to set the version. I do not want
> to
> > > change files that have been labeled. Is my understanding wrong?
> >
> > You need to describe things more completely if you want a better
> > answer from this list.
> >
> > Wayne
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>
>
> --
>
> Patrick D. Haggerty
>
