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

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.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... When RELEASE=No, zips are generated w/ a static suffix: http://www.qa.jboss.com/binaries/RHDS/builds/staging/devstudio-5.0_stable... 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... -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira