[jbosstools-dev] JBT/JBDS Target Platform for Beta1 -- time to update?

Mon Jan 30 11:00:31 EST 2012

There are two compelling reasons to keep building against the latest 
Eclipse.org bits:

a) provide feedback to upstream so they'll fix their bugs

If we lock in on 3.7.0 and never move up, we don't ever validate 3.7.x 
bugs are fixed, nor can we take advantage of the fixes. The recent bump 
that Rob S asked for to grab a newer WTP 3.3.2 maintenance build is a 
prime example of that.

b) ensure that when SR2 is released, and becomes the standard version 
of Eclipse 3.7 available on which people will install JBT, that our 
stuff WILL RUN THERE.

It's great to obsess over old version compatibility because yes, there 
will be people out there who are using 3.7.0 (or earlier?), but based 
on past experience - and our download numbers! - the bulk of people 
using JBT will be using it once it goes FINAL, not some early 
milestone. And therefore we need to worry about 3.7.2 moreso than 3.7.0.

But that said, if a given feature or plugin will happily run on a 3.7.x 
instead of 3.7.2, then its manifest should correctly set the wider 
range to allow that.

Nick

On Sat 28 Jan 2012 03:29:40 AM EST, Max Rydahl Andersen wrote:
> I think what Denis is saying is that many more than the plugins that relate to JBIDE-9853 is bumped.
>
> That's the problem.
>
> i.e. none of our plugins have problems running on SR0 on almost any platform just because SWT 86_64 has a runtime issue when starting up.
>
> /max
>
> On Jan 28, 2012, at 24:54, Nick Boldt wrote:
>
>> That's because there are bug fixes in SR1 on which we depend.
>>
>> For example, https://issues.jboss.org/browse/JBIDE-9853
>>
>> On 01/27/2012 02:22 PM, Denis Golovin wrote:
>>> On 01/27/2012 01:13 AM, Max Rydahl Andersen wrote:
>>>> +1
>>>>
>>>> But I would like to make clear this does *not* mean our code should
>>>> have hard plugin dependencies on
>>>> SR2.
>>>>
>>>> Still much better if our code install and runs from SR0 and upwards.
>>> Which is not the case right now. Simple test below fails on as component
>>>
>>> 1. Download
>>> http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo/e370-wtp330.target.zip
>>>
>>> 2. cd to svn workspace with trunk version
>>> 3. mvn clean install -Dmaven.test.skip -Dmaven.repo.local=.repository1/
>>> -Djbosstools-target-site=jar:file///path-to-tp/e370-wtp330.target.zip\!/
>>>
>>> Denis
>>>
>>>>
>>>> /max
>>>>
>>>> On Jan 26, 2012, at 21:19, Nick Boldt wrote:
>>>>
>>>>> OK, but bear in mind I'll still have to do it again after the SR2
>>>>> bits are actually in the can.
>>>>>
>>>>> Pencilling this in for Monday, barring other +1/-1 comments.
>>>>>
>>>>> On 01/26/2012 02:22 PM, Len DiMaggio wrote:
>>>>>> I'd vote for doing this early - in other words next week. It sounds
>>>>>> like
>>>>>> it's unlikely that there will be a major issue, but if there is a
>>>>>> problem it's better to find it sooner.
>>>>>>
>>>>>>
>>>>>> --Len
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> ------------------------------------------------------------------------
>>>>>>
>>>>>>
>>>>>> *From: *"Nick Boldt"<nboldt at redhat.com>
>>>>>> *To: *external-exadel-list at redhat.com, "jbds-pm-list"
>>>>>> <jbds-pm-list at redhat.com>, jbosstools-dev at lists.jboss.org
>>>>>> *Sent: *Thursday, January 26, 2012 10:20:39 AM
>>>>>> *Subject: *JBT/JBDS Target Platform for Beta1 -- time to update?
>>>>>>
>>>>>> About a month ago, I created a new Target Platform [1], [2] for use
>>>>>> with
>>>>>> our trunk builds so we'd be using the latest from Eclipse.org as they
>>>>>> move toward SR2.
>>>>>>
>>>>>> On Jan 20, the first release candidate (RC1) for Eclipse Indigo SR2 was
>>>>>> dropped. There are 3 more planned on Feb 3, 10 and 17, with GA on Feb
>>>>>> 24. Chances are there will be little to no changes between now and
>>>>>> their GA.
>>>>>>
>>>>>> Would next week be a good time to bump up the TPs to newer content? Or
>>>>>> should we wait until closer to the Feb 16 code freeze? Bear in mind
>>>>>> we'll want to update AGAIN before we drop Beta1 so that the bits public
>>>>>> on eclipse.org will match exactly those against which we built.
>>>>>>
>>>>>> Note too that changing the TP DURING a QE cycle will guarantee a respin
>>>>>> is needed.
>>>>>>
>>>>>> [1]
>>>>>> http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.SR1-M/
>>>>>>
>>>>>> [2]
>>>>>> http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_3.3.indigo.SR1-M/
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>> Nick Boldt :: JBoss by Red Hat
>>>>>> Productization Lead :: JBoss Tools&  Dev Studio
>>>>>> http://nick.divbyzero.com
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> --
>>>>>>
>>>>>> Len DiMaggio (ldimaggi at redhat.com)
>>>>>> JBoss by Red Hat
>>>>>> 314 Littleton Road
>>>>>> Westford, MA 01886 USA
>>>>>> tel: 978.392.3179
>>>>>> cell: 781.472.9912
>>>>>> http://www.redhat.com
>>>>>> http://community.jboss.org/people/ldimaggio
>>>>>>
>>>>>> <http://www.redhat.com>
>>>>>>
>>>>> --
>>>>> Nick Boldt :: JBoss by Red Hat
>>>>> Productization Lead :: JBoss Tools&  Dev Studio
>>>>> http://nick.divbyzero.com
>>>>>
>>>> /max
>>>> http://about.me/maxandersen
>>>>
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> 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
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>
> /max
> http://about.me/maxandersen
>
>
>

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