[
https://issues.jboss.org/browse/JBTIS-240?page=com.atlassian.jira.plugin....
]
Nick Boldt commented on JBTIS-240:
----------------------------------
I was referring to the integration-stack/aggregate/ folder, not the integration-stack/
folder. Suspect that got updated the last time you used the promote.sh script (eg., with
jbosstools-promote).
This is due to this bit of code:
{code:title=https://raw.github.com/jbosstools/jbosstools-build-ci/master/publish/promote.sh}
jbosstools-cleanup.sh --dirs-to-scan
"updates/${BUILD_TYPE}/${TARGET_PLATFORM}/${PARENT_FOLDER}"
--regen-metadata-only
{code}
So... the next time that runs we can verify if my fix worked & close this.
Or I can call cleanup.sh w/ the --regen-metadata-only and see what happens.
JBTIS Stable Kepler update site contains children which are not
update sites
----------------------------------------------------------------------------
Key: JBTIS-240
URL:
https://issues.jboss.org/browse/JBTIS-240
Project: JBoss Tools Integration Stack
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: distribution
Affects Versions: 4.1.3.Final
Reporter: Nick Boldt
Assignee: Paul Leacu
http://download.jboss.org/jbosstools/updates/stable/kepler/integration-st...
contains composite metadata which reads:
{code}
<children size="2">
<child
location="jbosstools-integration-stack-sources-4.1.3.Final.zip.MD5/"/>
<child location="4.1.3.Final/"/>
</children>
{code}
Was this generated by a script or manually produced?
If scripted, looks like a bug upstream in my code - please reassign this to me so we can
ensure that MD5 is not seen a child folder to be composited into the site.
If manual, you should remove the link to the MD5 file as it's not an update site.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira