[ https://issues.jboss.org/browse/JBIDE-25138?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-25138 at 10/3/17 1:49 PM: ------------------------------------------------------------- The fix is threefold: a) when publishing a new milestone [3], regen the composite metadata in the /updates/rhamt/ folder. cc: [~manaRH] {code:title=https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/windup-eclipse-plugin-release/jobConfigHistory/showDiffFiles?timestamp1=2017-09-13_07-21-13&timestamp2=2017-10-03_17-29-45} # regenerate metadata in http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/ so we don't have to manually update /updates/rhamt/composite/ ! rm -f jbosstools-cleanup.sh curl -s -k https://raw.githubusercontent.com/jbosstools/jbosstools-build-ci/master/u... > jbosstools-cleanup.sh chmod +x jbosstools-cleanup.sh ./jbosstools-cleanup.sh --regen-metadata-only --no-subdirs --link 1 -d ${DEPLOY_URL%%/${TAG_NAME}} --exclude composite {code} [3] https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/wind... b) change the RHAMT updates/rhamt/composite/ folder so it reuses the ../ folder (/updates/rhamt/) instead of being hardcoded [4]. This URL is only useful if you're installing RHAMT outside of Central, by hand. cc: [~jsteele]. Added bonus is that when you release a new RHAMT milestone, the script above will just update your ../ folder and you don't need to wait for me to approve a PR to update these files [4] any more. Woo! [4] https://github.com/jbosstools/jbosstools-download.jboss.org/commit/ad16e4... c) update the discovery plugins to use the new ../ folder's composite site too [5] [5] https://github.com/jbosstools/jbosstools-discovery/commit/fcf3a1e9f829ec9... was (Author: nickboldt): The fix is threefold: a) when publishing a new milestone [3], regen the composite metadata in the rhamt folder. cc: [~manaRH] {code:title=https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/windup-eclipse-plugin-release/jobConfigHistory/showDiffFiles?timestamp1=2017-09-13_07-21-13&timestamp2=2017-10-03_17-29-45} # regenerate metadata in http://download.jboss.org/jbosstools/oxygen/development/updates/rhamt/ so we don't have to manually update /rhamt/composite/ ! rm -f jbosstools-cleanup.sh curl -s -k https://raw.githubusercontent.com/jbosstools/jbosstools-build-ci/master/u... > jbosstools-cleanup.sh chmod +x jbosstools-cleanup.sh ./jbosstools-cleanup.sh --regen-metadata-only --no-subdirs --link 1 -d ${DEPLOY_URL%%/${TAG_NAME}} --exclude composite {code} [3] https://jenkins.hosts.mwqe.eng.bos.redhat.com/hudson/view/Windup/job/wind... b) change the RHAMT /composite/ folder so it reuses the ../ folder instead of being hardcoded [4]. This URL is only useful if you're installing RHAMT outside of Central, by hand. cc: [~jsteele]. Added bonus is that when you release a new RHAMT milestone, the script above will just update your ../ folder and you don't need to wait for me to approve a PR to update these files [4] any more. Woo! [4] https://github.com/jbosstools/jbosstools-download.jboss.org/commit/ad16e4... c) update the discovery plugins to use the new ../ folder [5] [5] https://github.com/jbosstools/jbosstools-discovery/commit/fcf3a1e9f829ec9... -- This message was sent by Atlassian JIRA (v7.2.3#72005)