[jbosstools-dev] Changes to jbosstools/devstudio 4.60.x target platforms to avoid remediation when installing?

[Nick Boldt]

Turns out the actual problem I was seeing was that of an install-time test.

So as discussed in https://issues.jboss.org/browse/JBIDE-23364 the
best solution here appears to be to simply build the jbosstools
aggregate sites using the MAX target platform so we avoid any
disparity of versions in the composite.

On Mon, Oct 17, 2016 at 1:25 PM, Alexey Kazakov <alkazako at redhat.com> wrote:
>
>
> On 10/16/2016 05:49 PM, Nick Boldt wrote:
>> I've encountered a couple remediation problems when installing the
>> latest jbosstools/devstudio AM2 bits.
> Installing into Neon.0 or Neon.1?
>
>>
>> If you've hit these problems too, and agree we should bump the
>> versions in the 4.60.2.AM1-SNAPSHOT target platform to include newer
>> bits (from Neon.1 instead of Neon.0), please +1 the JIRAs and I'll
>> update the target platforms so these changes are live as part of the
>> AM2 staging & subsequent release.
>
> We are using  4.60.x / Neon.0 TP for building only, correct? And we use
> 4.61.x / Neon.1 TP in update sites, devstudio installer, etc. So am not
> sure how Neon.0 TP can change anything in the installation process?
>
>>
>> * https://issues.jboss.org/browse/JBIDE-23364 Code Recommenders -> 2.4.3
>> * https://issues.jboss.org/browse/JBIDE-23365 egit & egit.mylyn -> 4.4.1
>> * https://issues.jboss.org/browse/JBIDE-23143 more remediation issues
>>
>>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev



-- 
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com