[jbosstools-issues] [JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds

[Nick Boldt (JIRA)]

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

Nick Boldt commented on JBIDE-18876:
------------------------------------

Outcome from today's build.next call is that we'd like to see statistics on how often and for whom this problem occurs. If every time it happens you ( [~dgolovin] ) could jot down some details here or in a Google spreadsheet, we can better prioritize how urgent this change is. 

> Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds
> ------------------------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-18876
>                 URL: https://issues.jboss.org/browse/JBIDE-18876
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.3.0.Alpha1
>            Reporter: Denis Golovin
>            Assignee: Denis Golovin
>             Fix For: 4.4.0.Alpha1
>
>
> Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task.
> So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus. 
> Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away.



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