[jbosstools-issues] [JBoss JIRA] (JBTIS-240) JBTIS Stable Kepler update site contains children which are not update sites
Paul Leacu (JIRA)
issues at jboss.org
Tue Apr 15 15:14:33 EDT 2014
[ https://issues.jboss.org/browse/JBTIS-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Paul Leacu resolved JBTIS-240.
------------------------------
Fix Version/s: 4.1.4.Final
Resolution: Done
Looks good - fixed by Nick.
<?xml version='1.0' encoding='UTF-8'?><?compositeArtifactRepository version='1.0.0'?>
<repository name='JBoss Tools Integration Stack Stable Release' type='org.eclipse.equinox.internal.p2.artifact.repository.CompositeArtifactRepository' version='1.0.0'>
<properties size='2'><property name='p2.timestamp' value='1397157529000'/><property name='p2.compressed' value='true'/></properties>
<children size='1'>
<child location='4.1.4.Final/'/>
</children>
</repository>
> 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
> Fix For: 4.1.4.Final
>
>
> http://download.jboss.org/jbosstools/updates/stable/kepler/integration-stack/aggregate/ 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
More information about the jbosstools-issues
mailing list