[jbosstools-dev] Beta2 update - almost there! (was Re: Approaching Code Freeze for Beta2 :: FINAL ORDERS, PLEASE!)

Jiri Peterka jpeterka at redhat.com
Mon Mar 26 04:31:17 EDT 2012


Hi,

JBoss Central is working for me on JBDS 5 beta2, H115, L64 (clean JBDS 
installation)  Installation from update is confirmed as working as well. 
Issue in a log was already reported for beta1 - 
https://issues.jboss.org/browse/JBIDE-11164. Len, please comment the 
JIRA if needed.

--
Jirka


On 03/23/2012 10:33 PM, Max Andersen wrote:
> And pease open bugs ASAP with fix version beta2 so those that are 
> around Can pick it up.
>
> Sent from a mobile device
>
> On 23/03/2012, at 22.29, Len DiMaggio <ldimaggi at redhat.com 
> <mailto:ldimaggi at redhat.com>> wrote:
>
>> I can't get Central to open - funny - there is no ERROR written to 
>> the log until I close eclipse. Max - is this working for you?
>>
>>
>> --Len
>>
>>
>>
>>
>> ------------------------------------------------------------------------
>>
>>     *From: *"Max Andersen" <manderse at redhat.com
>>     <mailto:manderse at redhat.com>>
>>     *To: *"Nick Boldt" <nboldt at redhat.com <mailto:nboldt at redhat.com>>
>>     *Cc: *"jbds-pm-list" <jbds-pm-list at redhat.com
>>     <mailto:jbds-pm-list at redhat.com>>, jbosstools-dev at lists.jboss.org
>>     <mailto:jbosstools-dev at lists.jboss.org>,
>>     external-exadel-list at redhat.com
>>     <mailto:external-exadel-list at redhat.com>
>>     *Sent: *Friday, March 23, 2012 5:27:06 PM
>>     *Subject: *Re: [jbosstools-dev] Beta2 update - almost there! (was
>>     Re:        Approaching Code Freeze for Beta2 :: FINAL ORDERS,
>>     PLEASE!)
>>
>>     I've just got info that the forge runtime fixes contains a bug.
>>     Everything else can be verified on this beta2 build. I hope to
>>     get more info soon to hear how severe the bug is.
>>
>>     Sent from a mobile device
>>
>>     On 23/03/2012, at 19.23, Nick Boldt <nboldt at redhat.com
>>     <mailto:nboldt at redhat.com>> wrote:
>>
>>     > JBT 3.3.0.Beta2 is out (see other email w/ links).
>>     >
>>     > JBDS 5.0.0.Beta2 is pending. We're #7 in the Jenkins queue for
>>     the last
>>     > build job in our stack, which produces the JBDS top-level product
>>     > feature (the one that allows the JBDS product to be updated).
>>     >
>>     >
>>     http://hudson.qa.jboss.com/hudson/job/devstudio-5.0_stable_branch.product/
>>
>>     >> =115
>>     >
>>     > As you of course know, this means the Beta1 branch is now
>>     CLOSED for any
>>     > new commits. Please don't push anything in there w/o attaching
>>     a patch
>>     > to a JIRA AND getting PM approval.
>>     >
>>     > Have a good weekend,
>>     >
>>     > Nick
>>     >
>>     > On 03/22/2012 01:06 PM, Nick Boldt wrote:
>>     >> Note that predictably, I announce "we might be able to do it
>>     sooner" and
>>     >> an hour later I've taken two slaves offline due to OOM and "no
>>     locks
>>     >> available" problems.
>>     >>
>>     >> https://engineering.redhat.com/rt/Ticket/Display.html?id=147071
>>     >> https://engineering.redhat.com/rt/Ticket/Display.html?id=147072
>>     >>
>>     >> On the plus side, Openshift is already done, so now we just
>>     need Maven,
>>     >> Forge, and VPE.
>>     >>
>>     >> On 03/22/2012 11:54 AM, Max Rydahl Andersen wrote:
>>     >>>
>>     >>> VPE and Forge will be fixed.
>>     >>>
>>     >>> WS/JAX-RS and Hibernate is being looked at but I do not think
>>     they
>>     >>> will be relevant for beta2 at this time.
>>     >>>
>>     >>> /max
>>     >>>
>>     >>> On Mar 22, 2012, at 4:50 PM, Nick Boldt wrote:
>>     >>>
>>     >>>> I see 6 open issues assigned to a Beta2 target.
>>     >>>>
>>     >>>> Are all these going to be fixed& committed today or
>>     tomorrow? If not,
>>     >>>> can the owners move them off to Beta3 target? Components
>>     include WS,
>>     >>>> Hibernate, VPE& Forge.
>>     >>>>
>>     >>>>
>>     https://issues.jboss.org/secure/IssueNavigator!executeAdvanced.jspa?jqlQuery=project+in+%28JBIDE%2C+JBDS%2C+TOOLSDOC%29+AND+fixVersion+in+%28%275.0.0.Beta2%27%2C+%273.3.0.Beta2%27%29+and+Status+not+in+%28Resolved%2CClosed%29&runQuery=true&clear=true
>>     <https://issues.jboss.org/secure/IssueNavigator%21executeAdvanced.jspa?jqlQuery=project+in+%28JBIDE%2C+JBDS%2C+TOOLSDOC%29+AND+fixVersion+in+%28%275.0.0.Beta2%27%2C+%273.3.0.Beta2%27%29+and+Status+not+in+%28Resolved%2CClosed%29&runQuery=true&clear=true>
>>     >>>>
>>     >>>>
>>     >>>>
>>     >>>> - or -
>>     >>>>
>>     >>>>
>>     https://issues.jboss.org/secure/IssueNavigator.jspa?mode=show&createNew=true
>>     <https://issues.jboss.org/secure/IssueNavigator.jspa?mode=show&createNew=true>
>>     >>>>
>>     >>>> --> then paste in this:
>>     >>>>
>>     >>>> project in (JBIDE, JBDS, TOOLSDOC) AND fixVersion in
>>     ('5.0.0.Beta2',
>>     >>>> '3.3.0.Beta2') and Status not in (Resolved,Closed)
>>     >>>>
>>     >>>>
>>     >>>> On 03/22/2012 11:36 AM, Nick Boldt wrote:
>>     >>>>> Based on recent commits in SVN, I see two builds left to
>>     run for Beta2:
>>     >>>>>
>>     >>>>> * OpenShift, SVN r39770, build #66 in progress (waiting for
>>     a slave)
>>     >>>>> * Maven, SVN r39676, build #81 in progress (waiting for a
>>     slave)
>>     >>>>>
>>     >>>>> Other respins are done, including: AS, Examples, VPE,
>>     Hibernate,
>>     >>>>> Central, and Runtime.
>>     >>>>>
>>     >>>>> After that, we need to run the 3 aggregate jobs for JBT and
>>     JBDS.
>>     >>>>>
>>     >>>>> --
>>     >>>>>
>>     >>>>> Does anyone else have anything pending for commit to the
>>     Beta1 branch
>>     >>>>> for inclusion in the Beta2 bits? If not, I may be able to
>>     get the build
>>     >>>>> out to QE sooner than previously planned.
>>     >>>>>
>>     >>>>
>>     >>>> --
>>     >>>> 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
>>     <mailto: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
>>     <mailto:jbosstools-dev at lists.jboss.org>
>>     > https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>>
>>
>>
>>
>> -- 
>>
>> Len DiMaggio (ldimaggi at redhat.com <mailto: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
>>
>> <RHxJBpngthumb.png> <http://www.redhat.com>
>>
>> <beta2.log>
>> _______________________________________________
>> jbosstools-dev mailing list
>> jbosstools-dev at lists.jboss.org <mailto:jbosstools-dev at lists.jboss.org>
>> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
>
>
> _______________________________________________
> jbosstools-dev mailing list
> jbosstools-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev


-- 
Jiri Peterka
JBoss Developer Studio QE
Red Hat Czech s.r.o., Purkynova 99, 612 45 Brno, Czech Republic
IRC: jpeterka #jboss-qa, #devstudio-qa
email: jpeterka at redhat.com

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbosstools-dev/attachments/20120326/ac289729/attachment.html 


More information about the jbosstools-dev mailing list