[jbosstools-dev] How should we deal with components of projects which have not changed since JBT 4.1.0.Final (eg., jbosstools-base/runtime) ?

[Mickael Istria]

On 09/27/2013 07:28 PM, Denis Golovin wrote:
> I would prefer to have one place where we can configure what is included
> into release.
> Aggregate build seems to be a good candidate for this place. Why not
> just point to exact version
> 2.1.0.Final-v20130717-0450-B102 of runtime feature in aggregation update
> site?
>
Strict versions like this ones can't be used by continuous integration. 
We currently use the 0.0.0 "wildcard" version which let the build chose 
what to be included (and it is necessary to do so when the development 
stream is active).
However, selecting specific versions could indeed be a pre-release step, 
but would require more effort (and then more time) to perform the release).
-- 
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets 
<http://twitter.com/mickaelistria>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20130930/6c21fcd9/attachment.html