<div dir="ltr">I didn't like the Idea of locking JBT release to Specific Service Release because there was no way for user to understand what is going on when JBoss Tools update fails with 'encripted' error in install dialog.<div>Then we got remediation step in that tries to solve the problem and suggests solutions. </div><div>I don't say I like the idea making JBossTools to require specific service release, but should not we reevaluate it with remediation step in place? <span style="line-height:1.5">How would that work now? Would it ask to install Eclipse Update? Is it good workflow for installation/update when some people who doesn't want to update eclipse have to choose?</span></div><div><br></div></div><br><div class="gmail_quote"><div dir="ltr">On Wed, Dec 9, 2015 at 8:22 AM Alexey Kazakov <<a href="mailto:alkazako@redhat.com">alkazako@redhat.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
-1 to have hard dependencies to Mars.1<br>
If user has Mars.1 then good. It will work fine.<br>
If no, and still using Mars.0 then he/she should update if he wants
to have this bug fix.<br>
IMO this is not critical enough to force users to use Mars.1</div><div bgcolor="#FFFFFF" text="#000000"><br>
<br>
<div>On 12/09/2015 10:25 AM, Nick Boldt
wrote:<br>
</div>
<blockquote type="cite">
<div dir="ltr">We have in the past done updates to JBT / JBDS
which *force* users to move up to a SR1 or SR2 minimum but we've
also done LOTS of releases where it was optional.
<div><br>
</div>
<div>So, yes, you need PM (Alexey) and QE (Len) to agree to this
change. I suspect Max will disagree to it.</div>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Wed, Dec 9, 2015 at 10:04 AM,
Mickael Istria <span dir="ltr"><<a href="mailto:mistria@redhat.com" target="_blank">mistria@redhat.com</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
<div>On 12/09/2015 03:56 PM, André Dietisheim wrote:<br>
</div>
<blockquote type="cite"> I added org.eclipse.swt 3.104.1
as required plugins to openshift.ui and express.ui,
shouldnt this trigger updated swt to get installed along
JBT?<br>
<a href="https://github.com/jbosstools/jbosstools-openshift/pull/838" target="_blank">https://github.com/jbosstools/jbosstools-openshift/pull/838</a><br>
</blockquote>
People who're using Mars.0 and installing this OpenShift
version will see a remediation page that will force them
to update their whole IDE to Mars.1 (because SWT version
is hardcoded in Platform, and using newer SWT implies
using newer Platform).<br>
I don't know if this is something we want to enforce or
not. I'm personally OK with dictating users to use the
newer/better version, but you'll need other people to
agree on that before forcing such a change.<span><br>
<br>
<div>-- <br>
Mickael Istria<br>
Eclipse developer at <a href="http://www.jboss.org/tools" target="_blank">JBoss,
by Red Hat</a><br>
<a href="http://mickaelistria.wordpress.com" target="_blank">My blog</a> - <a href="http://twitter.com/mickaelistria" target="_blank">My Tweets</a></div>
</span></div>
<br>
_______________________________________________<br>
jbosstools-dev mailing list<br>
<a href="mailto:jbosstools-dev@lists.jboss.org" target="_blank">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/mailman/listinfo/jbosstools-dev</a><br>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</div>
-- <br>
<div>
<div dir="ltr">
<div>
<div dir="ltr">Nick Boldt :: JBoss by Red Hat<br>
Productization Lead :: JBoss Tools & Dev Studio<br>
<a href="http://nick.divbyzero.com" target="_blank">http://nick.divbyzero.com</a><br>
</div>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
<pre>_______________________________________________
jbosstools-dev mailing list
<a href="mailto:jbosstools-dev@lists.jboss.org" target="_blank">jbosstools-dev@lists.jboss.org</a>
<a href="https://lists.jboss.org/mailman/listinfo/jbosstools-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jbosstools-dev</a></pre>
</blockquote>
<br>
</div>
<br>
<div style="font-family:Arial,Helvetica,sans-serif"><p style="margin-bottom:0.08in"><span style="font-family:Arial,serif;background-color:rgb(255,255,255)"><font color="#808080" size="1">CONFIDENTIALITY
NOTICE: This email and files attached to it are confidential. If you
are not the intended recipient you are hereby notified that using,
copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have
received this email in error please notify the sender and delete this
email.</font></span></p></div>_______________________________________________<br>
jbosstools-dev mailing list<br>
<a href="mailto:jbosstools-dev@lists.jboss.org" target="_blank">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/mailman/listinfo/jbosstools-dev</a></blockquote></div>
<br>
<div style="font-family:Arial,Helvetica,sans-serif"><p style="margin-bottom:0.08in"><span style="font-family:Arial,serif;background-color:rgb(255,255,255)"><font color="#808080" size="1">CONFIDENTIALITY
NOTICE: This email and files attached to it are confidential. If you
are not the intended recipient you are hereby notified that using,
copying, distributing or taking any action in reliance on the contents of this information is strictly prohibited. If you have
received this email in error please notify the sender and delete this
email.</font></span></p></div>