[jbosstools-issues] [JBoss JIRA] (JBTIS-471) Unify component versions

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBTIS-471?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13169116#comment-13169116 ] 

Nick Boldt commented on JBTIS-471:
----------------------------------

In https://github.com/droolsjbpm/droolsjbpm-tools/commit/d96ca9479a8a70c8fe3eea7e370b64620363d6bb 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/SOATooling/job/droolsjbpm-tools/ so reconfiguring the job after the above PRs are applied should be pretty simple. Let me know if you need assistance with that.

> Unify component versions
> ------------------------
>
>                 Key: JBTIS-471
>                 URL: https://issues.jboss.org/browse/JBTIS-471
>             Project: JBoss Tools Integration Stack
>          Issue Type: Enhancement
>          Components: distribution
>    Affects Versions: 8.0.3.GA
>            Reporter: Andrej Podhradsky
>            Assignee: Robert (Bob) Brodt
>             Fix For: 4.3.0.Beta1
>
>         Attachments: junit4.8vs4.12.png
>
>
> Currently, JBDS-IS 8.0.3.CR2 contains components with different version format such as
> BPMN2 1.1.3.Final
> Fuse 7.3.1.v20150728-1330-H54-Final
> Teiid Designer 9.0.3.Final-v20150728-2029-B1148
> I suggest to use the format used by Teiid Designer.



--
This message was sent by Atlassian JIRA
(v6.4.11#64026)