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

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/e... 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&quot;&lt;nboldt(a)redhat.com&gt; >>> *To: *external-exadel-list(a)redhat.com, "jbds-pm-list" >>> <jbds-pm-list(a)redhat.com&gt;, jbosstools-dev(a)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.S... >>> >>> [2] >>> http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_3.3.in... >>> >>> >>> >>> -- >>> Nick Boldt :: JBoss by Red Hat >>> Productization Lead :: JBoss Tools& Dev Studio >>> http://nick.divbyzero.com >>> >>> >>> >>> >>> -- >>> >>> Len DiMaggio (ldimaggi(a)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(a)lists.jboss.org > https://lists.jboss.org/mailman/listinfo/jbosstools-dev