<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 09/30/2013 11:50 AM, Max Rydahl
Andersen wrote:<br>
</div>
<blockquote cite="mid:20130930095027.GO9638@slowbeard.local"
type="cite">i'm leaning more and more towards the continous
composite site is causing more damage and hiding more issues
<br>
than it is worth having.
<br>
</blockquote>
The big benfit of this continuous composite site is what you
describe here:<br>
<blockquote cite="mid:20130930095027.GO9638@slowbeard.local"
type="cite">[...]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.
<br>
</blockquote>
We'll need standardized URLs, and we'll need each component to
define its dependencies in a pom.<br>
Then we can go for configuation such as<br>
<pre><properties>
<buildType>snapshot</buildType> <!-- Can be snapshot, integration, release -->
</properties>
<repository>
<layout>p2</layout>
<url><a class="moz-txt-link-freetext" href="http://download.jboss.org/jbosstools/updates/jbosstools-base/1.4.0/$">http://download.jboss.org/jbosstools/updates/jbosstools-base/1.4.0/$</a>{buildType}</url>
</repository></pre>
The URL pattern needs to control required version (set in pom), and
buildType (default value in pom, overridable via command-line).<br>
We can't easily use a target definition for that as they don't allow
properties.<br>
<br>
<div class="moz-signature">-- <br>
Mickael Istria<br>
Eclipse developer at <a href="http://www.jboss.org/tools">JBoss,
by Red Hat</a><br>
<a href="http://mickaelistria.wordpress.com">My blog</a> - <a
href="http://twitter.com/mickaelistria">My Tweets</a></div>
</body>
</html>