Re: [jbosstools-dev] How should we deal with components of projects which have not changed since JBT 4.1.0.Final (eg., jbosstools-base/runtime) ?
On Mon, Sep 30, 2013 at 11:35:28AM +0200, Mickael Istria wrote:
On 09/30/2013 11:17 AM, Max Rydahl Andersen wrote:
>+1
>This is similar to what JBTIS does.
This also requires to have components pushing a version they want to
get aggregated. This version should be moved to a stable URL, and
components owner should provide PR on the aggregator category.xml to
use the right URL and the right version.
Yes - and this url could even be a "snapshot" site for use during CI builds.
Then at release time it gets updated to point to the actual release.
Aggregator shouldn't consume the "continuous" composite
site.
i'm leaning more and more towards the continous composite site is causing more damage
and hiding more issues
than it is worth having.
My biggest concern on moving to this is that some components (such as JST) probably have
too high a dependency on Common in base to make it feasible...but if we could have these
components explicitly point to a "snapshot" of the site (not the composited
site) until release time this might be doable.
/max