[jbossts-issues] [JBoss JIRA] (JBTM-1902) Build number of Narayana is not resolved, says ${buildNumber}

Paul Robinson (JIRA) jira-events at lists.jboss.org
Thu Aug 29 06:07:26 EDT 2013

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

Paul Robinson commented on JBTM-1902:


Can you take a look at this as I don't have time at the moment. We already have the buildnumber-maven-plugin in our root pom and it is now set to a version that supports git. We also seem to have the scm block set in the root pom. However, ${buildNumber} is still not resolving. We don't have it configured as it suggests in the following doc, which may be the problem. However, I have tried configuring it as suggested, but it is still not being resolved. 


Also, I think we need the following config, when you do get it working:

           <!-- gives us a short SHA1 instead of the full commit id -->
           <!-- allows us to do a build with un-committed files. Essential for development -->
           <!-- Doesn't do a git update during build. Essential for development -->

> Build number of Narayana is not resolved, says ${buildNumber}
> -------------------------------------------------------------
>                 Key: JBTM-1902
>                 URL: https://issues.jboss.org/browse/JBTM-1902
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: Build System
>            Reporter: Radoslav Husar
>            Assignee: Paul Robinson
>            Priority: Minor
>             Fix For: 5.0.0.M5
> Logs say..
> {noformat}
> 	at com.arjuna.ats.internal.jbossatx.jta.XAResourceRecoveryHelperWrapper.getXAResources(XAResourceRecoveryHelperWrapper.java:51) [narayana-jts-integration-5.0.0.M3.jar:5.0.0.M3 (revision: ${buildNumber})]
> {noformat}
> which is not very useful :-)

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

More information about the jbossts-issues mailing list