September 2011 - jbosstools-dev - Jboss List Archives

by jboss-user-bounces＠lists.jboss.org

The results of your email command are provided below. Attached is your original message. - Results: Ignoring non-text/plain MIME parts - Done.

13 years, 2 months

1
0
0 / 0

N&N review

by Max Rydahl Andersen

Hi, http://fisheye.jboss.org/browse/~raw,r=trunk/JBossTools/trunk/documentati... (and they are actually already live since needed to verify upload.sh were working properly: http://docs.jboss.org/tools/whatsnew/) I'm not fully through yet reviewing content but did wire the most pages up so they should at least be linked properly together. As always if you find errors let me know or simply just fix them. thanks, /max http://about.me/maxandersen

13 years, 2 months

1
0
0 / 0

the "infamous" "does not have JSF code completion and validation enabled completed" dialog

by Max Rydahl Andersen

Hey, I'm still getting it on new xhtml files in non-wtp projects. Didn't we remove this dialog or at least reword it since for many projects JSF is *not* relevant ? /max http://about.me/maxandersen

13 years, 2 months

4
9
0 / 0

tracking jobs-in-progress in Hudson / making sure your changes get built and aggregated into JBT/JBDS

by Nick Boldt

So, you're all familiar by now with the views we use to track jobs for JBT/JBDS builds, right? http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Stable_Br... (3.2/4.1 branch) http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_3.3.indigo (3.3/5.0 current milestone branch) http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/ (3.3/5.0 trunk) -- Just recently I discovered there's a widget for "Latest Builds" which helps you see what's currently running. It's now the second widget on the above pages under "Unstable Builds", and shows the ten most recent builds. Anything blinking is in progress, which makes it really easy to see if jobs spinning along during the freeze/respin cycle and for me to know when everyone's done and it's quiet enough to pull builds from nightly & staging into the development folders for use by QE. THAT SAID... If you commit something you *NEED* pushed into a respin, please please please _ensure your change appears in a build_. Most jobs are on a 4-6hr SVN check cycle, and if you miss the window, your change won't get built for several hours. Every job's builds show what changes are in that build, and why the build happened (SVN change or upstream job push, usually). If during that quiet period I see no changes grinding in Hudson I may pull off a build assuming we're all done but your change _may be missed_. (This happened w/ for a couple components last week.) If you need assistance on how to find your component's job, how to kick a respin, how jobs are interconnected, where to find build output, or anything related to the process of "commit change to SVN" --> "change is in JBDS", DO NOT HESITATE to ask for help (or even just for the Hudson login password, if you don't have that anymore). -- As a reminder, I maintain three "Cascade" pages which show the linkage between Hudson jobs and built bits, one per stream: http://download.jboss.org/jbosstools/builds/cascade/ (3.2/4.1) http://download.jboss.org/jbosstools/builds/cascade/3.3.indigo.html (3.3/5.0 current milestone) http://download.jboss.org/jbosstools/builds/cascade/trunk.html (3.3/5.0 trunk) Cheers, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

13 years, 2 months

2
2
0 / 0

Code Freeze is over for 3.2.2 / 4.1.1 maintenance branch :: EOM

by Nick Boldt

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

13 years, 2 months

1
0
0 / 0

JBoss Tools 3.2.2.M1 & JBDS 4.1.1.M1 avail for QE smoke testing

by Nick Boldt

These are not the final bits for the M1 release (yet). Notification will be sent when these are finalized and released. These are for internal / QE use only. JBT: http://download.jboss.org/jbosstools/updates/JBossTools-3.2.2.M1/ http://download.jboss.org/jbosstools/builds/development/3.2.2.M1/ JBDS: http://www.qa.jboss.com/binaries/RHDS/updates/development/4.1.1.M1_core/ http://www.qa.jboss.com/binaries/RHDS/updates/development/4.1.1.M1_extras/ http://www.qa.jboss.com/binaries/RHDS/builds/development/4.1.1.M1/ -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

13 years, 2 months

1
0
0 / 0

JBT 3.2.2.M1 / JBDS 4.1.1.M1 :: CODE FREEZE starts today!

by Nick Boldt

Meant to send this out earlier, but today (Sept 2) was meant to be the code freeze for for JBDS 4.1.1.M1 / JBT 3.2.2.M1 so we can get a build to QE by Sept 6 for simple smoke testing (as they're already busy w/ QEing JBT3.3/JBDS 5 M3). As such, unless you have anything urgent to commit to that branch, consider the 4.x / 3.2.x stream frozen until further notice. Of course critical/blocker issues can still be committed but please get confirmation from Max or Denis, and ensure you have a patch attached to a jira for review. Cheers, -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

13 years, 2 months

2
2
0 / 0

JBoss Remote Java Application in N&N

by Snjezana Peco

Max, Rob, Attached is the New and Noteworthy for the JBoss Remote Java Application 3.3.0.M3. I am not sure if it needs to be n&n for JBoss AS or we need to create a new n&n component. Snjeza

13 years, 2 months

3
2
0 / 0

JBoss Tools 3.3.0.M3 available for QE testing

by Nick Boldt

Builds: http://download.jboss.org/jbosstools/builds/development/3.3.0.M3/ http://download.jboss.org/jbosstools/builds/development/3.3.0.M3-soa-tool... Updates: http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.M3/ http://download.jboss.org/jbosstools/updates/JBossTools-3.3.0.M3.soa-tool... -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

13 years, 2 months

1
0
0 / 0

Jira changes

by Max Rydahl Andersen

Hi, I had a long overdue list of jira changes identified at our face-2-face a few months back. I've now gone through these and the end result is as follows: core & jst merged with common ======================== problematic to have them separate since everyone mixed them up thus core component have been deleted, all existing issues moved to common that now is named common/jst/core Hibernate lead changed to Dima Geraskov ================================= Dima does all the work anyway and faster if he gets assigned/notified immediately on new issues than waiting for me to reassign. integration component deprecated =========================== integration never means anything on its own, thus renamed to "z - Legacy - integration" and added "integration" label for any still open issues since can't bulkedit resolved issues. Use "integration" label going forward if relevant. JBossAS renamed to JBossAS/Servers ============================== JBossAS is not only JBoss AS anymore. libmanagement deprecated ====================== always relevant for a specific component thus use tag instead. now named "z - Legacy - libmanagement" Plan deprecated ============= only used for 6 issues and not since 2008, now named "z - Legacy - Plan" runtimes renamed to runtime detection ============================== reporters got confused with server and other specific runtimes thus renamed to clarify. xforms marked as legacy ==================== component created for kukeltje 2+ years ago - never seen adoption/features materialized. I've pinged kukeltje about this change to let him know and see if he have any objections. You can see the end result here: https://issues.jboss.org/browse/JBIDE?selectedTab=com.atlassian.jira.plug... Makes things a big more clean ;) Thanks, /max http://about.me/maxandersen

13 years, 2 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev September 2011