[jbosstools-issues] [JBoss JIRA] Updated: (JBDS-1699) Product build should be able to source from upstream Updatesite build when set to RELEASE=Yes

[Denis Golovin (JIRA)]

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

Denis Golovin updated JBDS-1699:
--------------------------------

    Fix Version/s: 5.0.0.M2


> Product build should be able to source from upstream Updatesite build when set to RELEASE=Yes
> ---------------------------------------------------------------------------------------------
>
>                 Key: JBDS-1699
>                 URL: https://issues.jboss.org/browse/JBDS-1699
>             Project: Developer Studio (JBoss Developer Studio)
>          Issue Type: Bug
>          Components: installer
>    Affects Versions: 5.0.0.M2
>            Reporter: Nick Boldt
>             Fix For: 5.0.0.M2, 5.0.0.M3
>
>
> When RELEASE=Yes, zips are generated w/ a suffix such as http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_stable_branch.updatesite/extras-Update-2011-06-24_08-09-09-H8.zip
> When RELEASE=No, zips are generated w/ a static suffix: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_stable_branch.updatesite/extras-Update-SNAPSHOT.zip
> Currently, a number of files in JBDS product builder assume the filename for this file is static.
> For example, releng/org.jboss.ide.eclipse.releng/builders/jbds-all-package/build.properties, line 38, points at jar:file:${repoBaseLocation}/extras-Update-SNAPSHOT.zip!/ and cannot resolve variables like ${ZIPSUFFIX} or ${jbds.extra.build.archive} as defined in releng/org.jboss.ide.eclipse.releng/requirements/jbds-extra-update/build.properties. As such, this filename must currently be hard-coded and the upstream updatesite job must be set to RELEASE=No.
> Instead, any suffix should be supported via fetching the file's name from here:
> http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_stable_branch.updatesite/logs/build.properties

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