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

Gytis Trikleris (JIRA) issues at jboss.org
Thu Dec 12 11:54:32 EST 2013

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

Gytis Trikleris commented on JBTM-2061:

I did a demo upload to the staging repo and everything worked fine. I'd say it was a temporal issue with Nexus during your deployment.
> 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