[jbosstools-issues] [JBoss JIRA] Resolved: (JBIDE-9647) next/current/previous staging component cycler not working in 3.2.x branch

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-9647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt resolved JBIDE-9647.
-------------------------------

    Resolution: Done


Also affected publishing of http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-4.1_stable_branch.updatesite/ but that too appears fixed now.

> next/current/previous staging component cycler not working in 3.2.x branch 
> ---------------------------------------------------------------------------
>
>                 Key: JBIDE-9647
>                 URL: https://issues.jboss.org/browse/JBIDE-9647
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng, updatesite
>    Affects Versions: 3.2.2.M1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>            Priority: Blocker
>             Fix For: 3.2.2.M1
>
>
> This is a result of changes done in JBIDE-8667 backported to the 3.2.x branch.
> Instead of having staging.previous/jbosstools-3.2_stable_branch.aggregate/ and staging/jbosstools-3.2_stable_branch.aggregate.next/, we're getting staging/jbosstools-3.2_stable_branch.aggregate/ and staging/jbosstools-3.2_stable_branch.aggregate.next/ -- suggests a problem writing to staging.previous folder?

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira