[jbossts-issues] [JBoss JIRA] (JBTM-2061) blacktie-all pom was not uploaded to nexus for CR2? - strange!

Tom Jenkinson (JIRA) issues at jboss.org
Thu Dec 12 05:34:32 EST 2013


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

Tom Jenkinson commented on JBTM-2061:
-------------------------------------

A temporary workaround would be to try to upload that pom to nexus directly. If you do ./build.sh clean install deploy -f blacktie/pom.xml it will try to re-release everything so that doesn't work. Maybe we can do mvn deploy:deploy-file ...?
                
> blacktie-all pom was not uploaded to nexus for CR2? - strange!
> --------------------------------------------------------------
>
>                 Key: JBTM-2061
>                 URL: https://issues.jboss.org/browse/JBTM-2061
>             Project: JBoss Transaction Manager
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: BlackTie, Build System
>    Affects Versions: 5.0.0.CR2
>            Reporter: Tom Jenkinson
>            Assignee: Gytis Trikleris
>            Priority: Blocker
>             Fix For: 5.0.0.CR3
>
>
> For some reason the blacktie-all pom.xml was not uploaded with CR2. I don't think anything should have changed so I think it could be an issue with Nexus. 
> First thing is to verify if there were any changes to that pom (or its parent between CR1 and CR2)? Maybe the NRP instructions don't include the exact steps that would get that pom into Nexus?

--
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