<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="content-type"
content="text/html; charset=windows-1251">
</head>
<body text="#000000" bgcolor="#ffffff">
Max, Nick,<br>
<br>
I've also opened issue for download site structure
<a class="moz-txt-link-freetext" href="https://jira.jboss.org/browse/JBIDE-6956">https://jira.jboss.org/browse/JBIDE-6956</a><br>
<br>
Before aggregation was introduced which is building final repowith
everything included we used to have simple hierarchical stucture<br>
<img src="cid:part1.01030203.09020509@exadel.com" alt=""><br>
<br>
jbosstools/builds/${type}/${branch/tag}/${timestamp}<br>
jbosstools/updates/${type}/${branch/tag}<br>
<br>
where ${type} is <b>nightly, stable, development </b><br>
<br>
nightly for nightly builds <br>
stable for GA releases<br>
development for M's, betas and CR's releases<br>
<br>
${branch/tag} was used to separate builds made from different branch
tags<br>
<br>
${timestamp} time stamp YYYYMMDDHHMMSS <br>
<br>
for example in jbosstools/builds/nightly<br>
<br>
jbosstools/builds/nightly/trunk would contains last three nightly
builds from trunk<br>
jbosstools/builds/nightly/3.1.X would contains last three nightly
builds from 3.1.X branch<br>
jbosstools/builds/nightly/3.1.1 would contains last several builds from
3.1.1 tag depends on what kind of problems was found in release
candidate build<br>
<br>
for example jbosstools/updates/nightly would contains last update sites
for tags/branches like <br>
<br>
jbosstools/updates/nightly/trunk - last update site built from trunk<br>
jbosstools/updates/nightly/3.1.X last update site built from 3.1.X
branch<br>
jbosstools/updates/nightly/3.1.1 last update site built from 3.1.1 tag<br>
<br>
All above is about aggregated builds what we need to do next is to find
place to put bits build/updates for sepate components aggregated into
JBT Update site like: teiid, drools, pi4soa and etc. <br>
<br>
Even jbosstools continuous build could be treated like separate
component included in aggregated build/update site.<br>
<br>
Lets say we have for aggregated builds:<br>
<ul>
<li>jbosstools/builds</li>
<li>jbosstools/updates</li>
</ul>
Then we can have for separate components only for nightly builds:<br>
<br>
jbosstools/${component}/builds/nightly<br>
jbosstools/${component}/builds/nightly/${version/branch}/${timestamp}<br>
jbosstools/${component}/updates/nightly/<br>
jbosstools/${component}/updates/nightly/${version/branch}<br>
<br>
another option is to have them under current nightly folder<br>
<br>
jbosstools/builds/nightly/${component}/${branch/tag}/${timestamp}<br>
jbosstools/updates/nightly/${component}/${branch/tag}<br>
<br>
Sure we have to restore build index.html with links to update
sites/drivers and zipped update sites
<a class="moz-txt-link-freetext" href="https://jira.jboss.org/browse/JBIDE-6958">https://jira.jboss.org/browse/JBIDE-6958</a>.<br>
<br>
WDYT?<br>
<br>
Thanks<br>
Denis<br>
<br>
</body>
</html>