[ https://issues.jboss.org/browse/JBTIS-471?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBTIS-471: ---------------------------------- In https://github.com/droolsjbpm/droolsjbpm-tools/commit/d96ca9479a8a70c8fe3... you hard coded a build number of "212" which is not a recommended practice. Either you omit that or you include a REAL value. Here's how you can omit it for local builds and include it for Jenkins builds: https://github.com/droolsjbpm/droolsjbpm-tools/pull/45 https://github.com/droolsjbpm/droolsjbpm-tools/pull/46 To build locally, just do: mvn clean install To build in Jenkins, you would configure the job to use a "hudson" profile; you can mock that up locally like this: mvn clean install -Phudson -DBUILD_NUMBER=1234 I'm assuming your job is http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/SOATo... so reconfiguring the job after the above PRs are applied should be pretty simple. Let me know if you need assistance with that. -- This message was sent by Atlassian JIRA (v6.4.11#64026)