<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Mar 1, 2017 at 12:16 AM, Max Rydahl Andersen <span dir="ltr"><<a href="mailto:manderse@redhat.com" target="_blank">manderse@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On 28 Feb 2017, at 21:42, Mickael Istria wrote:<br>
<br>
> On 02/28/2017 07:24 PM, Max Rydahl Andersen wrote:<br>
>> sounds awesome if you guys found a way to deal with having to<br>
>> manually eep these from not overlapping and avoid rerelasing<br>
>> different bits with the same version number.<br>
> This was:<br>
> * <a href="https://issues.jboss.org/browse/JBIDE-13671" rel="noreferrer" target="_blank">https://issues.jboss.org/<wbr>browse/JBIDE-13671</a><br>
> * <a href="https://issues.jboss.org/browse/JBIDE-19056" rel="noreferrer" target="_blank">https://issues.jboss.org/<wbr>browse/JBIDE-19056</a><br>
> * <a href="https://issues.jboss.org/browse/JBIDE-22689" rel="noreferrer" target="_blank">https://issues.jboss.org/<wbr>browse/JBIDE-22689</a><br>
<br>
</span>none of these seem to be new ? these was what was fixe ages ago.<br>
<br>
So the version changes provides no benefits and becomes harder to keep<br>
track on ?<br>
<br>
Before it could be done more or less automated. Just thought it was<br>
changing because you guys found a benefit to do so.<br></blockquote><div>No, just to lower the load during updates. It is now possible because less components are being changed now (mainly OpenShift; server and base) </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<span class=""><br>
>> Will this mean that builds and release now only update the actual<br>
>> changed plugins ?<br></span></blockquote><div>Yes </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
>> and download diff will be smaller too ?<br></span></blockquote><div>Yes </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
> At least, the build infrastructure makes it possible and safe to<br>
> update plugins only when necessary, with the benefit mentioned above<br>
> (among others)<br>
<br>
</span>So is that a yes or no ?<br>
<span class=""><br>
>> btw. how come stopping to do the 3.3.0, 3.3.100 etc. as is standard<br>
>> in<br>
>> p2/eclipse ?<br>
> This versioning pattern is only useful if JBoss Tools properly manages<br>
> API versions and relies on API tools for guidance and checks. Last<br>
> time I heard about it, it was far from being the case.<br>
<br>
</span>Not really, it is to allow updates by us or others in both branches<br>
without colliding in p2 updates without having to rely on the fragile<br>
date/timestamp pattern.<br>
<br>
API versioning was secondary concern here.<br>
<div class="HOEnZb"><div class="h5"><br>
/max<br>
<a href="http://about.me/maxandersen" rel="noreferrer" target="_blank">http://about.me/maxandersen</a><br>
______________________________<wbr>_________________<br>
jbosstools-dev mailing list<br>
<a href="mailto:jbosstools-dev@lists.jboss.org">jbosstools-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/<wbr>mailman/listinfo/jbosstools-<wbr>dev</a><br>
</div></div></blockquote></div><br></div></div>