February 2012 - jbosstools-dev - Jboss List Archives

by Max Rydahl Andersen

Hi guys, It's that time again - sharpen your pencils and get your achievements scribbled into the whats new and noteworthy! I've cloned last time round into https://issues.jboss.org/browse/JBIDE-11011 (and if you don't like CLONE CLONE CLONE then edit the title and it will be gone next time :) As always: :start if (N&N) { write it into the relevant section in trunk/documentation/whatsnew/* } else { Add N&N labels for those you forgot; if(still !N&N) reject; } goto start Thank you!

11 years, 1 month

1
0
0 / 0

Adding Plugins to m2e Discovery Mechanism

by Rob Cernich

Hey folks, Does anybody know how I go about getting the SwitchYard tools to show up in m2e's discovery list? Thanks in advance, Rob

11 years, 1 month

6
15
0 / 0

Red Deer?

by Len DiMaggio

Hey everyone, We (JBDS QE) have started thinking about how to improve/refactor the SWTBot extensions - some of the issues that we want to improve on are test stability and ease of debugging. We're still at a very early stage on this - not much will happen until after the 5.0 GA - but will need everyone's input and contributions to this in the future. The current (very drafty) drafts of ideas and plans are here: https://docspace.corp.redhat.com/community/bu/middleware/jboss-qe/jboss_d... Our mascot is here: https://docspace.corp.redhat.com/servlet/JiveServlet/previewBody/89896-10... Stay tuned!, Len -- 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

11 years, 1 month

4
4
0 / 0

JBoss Tools & Dev Studio are branched for Beta1

by Nick Boldt

Branches created: http://svn.jboss.org/repos/jbosstools/branches/jbosstools-3.3.0.Beta1/ http://svn.jboss.org/repos/devstudio/branches/devstudio-5.0.0.Beta1/ Note that we are code frozen for Beta1, which means only urgent fixes should be done in the branch, associated w/ a JIRA. Trunk remains open for new development work; however, we should be more or less "feature complete" at this time, so focus on missing functionality (rather than adding new functionality), polishing, documentation, and ease of use improvements. Where applicable, please remember to commit changes in BOTH trunk and the new branch. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years, 1 month

2
1
0 / 0

Beta1 build status: 19 builds are red!

by Nick Boldt

Currently experiencing cascade failures insofar as components that depend on other components are failing because their upstream are failing. All red jobs: http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_3.3.indig... --- Here's the problem stack - looks like some refactoring last week (moving stuff from Central to Examples) might have caused some havoc to components that depend on these shared classes. common: test failure https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo... WS: compile failure https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo... Runtime: compile failure https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo... Examples: SVN checkout failures for vmg19-rhel5-x86; slave disconnected, reported to ci-issues@, and we're respinning. https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo... Portlet: compile failure https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo... Maven: compile failure due to project examples https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo... Central: compile failure https://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.compo... (Also failing in trunk: http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.component--cen...) JBT Aggregate: missing o.j.t.maven.jpa feature due to upstream maven component failure ESB, SOA Tooling: blocked by upstream. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years, 1 month

2
2
0 / 0

jbosstools-3.3_stable_branch.aggregate - Build # 64 - Failure!

by jboss-qa-internal＠redhat.com

jbosstools-3.3_stable_branch.aggregate - Build # 64 - Failure: Check console output at http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_stable_branch.aggreg... to view the results.

11 years, 1 month

1
10
0 / 0

Target Platform Update this week: new m2e-wtp 0.15.1 and m2e-jdt-compiler 1.0.0 to be included

by Nick Boldt

Current target platform [1] and reqs mirror [2] include m2e wtp feature 0.14 [3]: [1] http://download.jboss.org/jbosstools/updates/target-platform_3.3.indigo.S... [2] http://download.jboss.org/jbosstools/updates/indigo/SR1-M/ [3] http://download.jboss.org/jbosstools/updates/requirements/m2eclipse/20111... I've been asked [4] to update this, so I'm announcing the change will happen tomorrow. If the request to add m2e-jdt-compiler [5] gets approved in the next 24hrs, I'll add that at the same time too. [4] https://issues.jboss.org/browse/JBIDE-10659 [5] https://issues.jboss.org/browse/JBIDE-10834 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years, 1 month

3
6
0 / 0

Current crop of failing builds / Beta1 branch still postponed until later today

by Nick Boldt

Branching for Beta1 is currently blocked by a number of problems that I'd love to see fixed in trunk before I branch, but will most likely have to be fixed in BOTH trunk and branch afterwards. I've opened a few issues (links below). Component owners, please fix your issues or assign them to the correct people. == Publishing Issues == * JBDS Aggregate: publishing issues upstream. Awaiting respin. * Bottests Aggregate: publishing issues upstream. Awaiting respin. * JBT SOA Aggregate: problem resolving runtime.esb.detector. Hopefully a respin will fix. == Slave Issues == * AS: slave taken offline and reported to ci-issues@. 20 min job stalled after >2hrs https://engineering.redhat.com/rt/Ticket/Display.html?id=142775 == SWT Test Failures == CDI: https://issues.jboss.org/browse/JBIDE-10951 JBPM: https://issues.jboss.org/browse/JBIDE-10954 VPE: https://issues.jboss.org/browse/JBIDE-10957 == JUnit Test Failures == Common: https://issues.jboss.org/browse/JBIDE-10952 (1 failure) ESB: https://issues.jboss.org/browse/JBIDE-10953 (4 failures) JSF: https://issues.jboss.org/browse/JBIDE-10955 (2 failures) Seam: https://issues.jboss.org/browse/JBIDE-10956 (8 failures) == Compilation Errors == Continuous Build is failing due to Central, yet the Central job may be OK. I'm respinning both but Central is currently blocked up upstream. I had to change the swimlanes so that Central now depends on Maven (which might be why it was failing to compile, too). == Sourceforge Mirror Failure == Requirements Bootstrap is failing due to a faulty mirror, and I realized is using an old version of Seam 2.2.1.CR1 when Final is available. https://issues.jboss.org/browse/JBIDE-10950 -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years, 1 month

1
0
0 / 0

Code Freeze for Beta1 will be in about 5hrs

by Nick Boldt

As I'm finding a number of issues w/ builds today, including interlinkages ("swimlanes") that aren't correctly configured and all sorts of downstream build delays due to upstream builds churning, I will be branching for Beta1 closer to EOD here than the previous "before noon" plan stated yesterday. If you have a problem w/ the freeze being pushed back about 5hrs (eg., after 4pm GMT-5) let me know. I still intend to get something built and QEable over the weekend. -- Nick Boldt :: JBoss by Red Hat Productization Lead :: JBoss Tools & Dev Studio http://nick.divbyzero.com

11 years, 1 month

1
0
0 / 0

Using Jacoco coverage report as Usage report

by Mickael Istria

Hi all, Since generating Jacoco coverage files is as easy as setting up a -java.agent JVM arg, and does not affect performance, we could think about using Jacoco in daily usage of JBoss Tools/Dev Studio to get some "technical" usage reports. By gathering a sufficient amount of coverage report files from enough different users, we'll clearly see which pieces of code are not used, and which ones are the most used. See https://issues.jboss.org/browse/JBDS-2017 to debate this idea. And for our internal development usage and improved quality: https://issues.jboss.org/browse/JBIDE-10537 -- Mickael Istria Eclipse developer at JBoss, by RedHat <http://www.jboss.org/tools> My blog <http://mickaelistria.wordpress.com> - My Tweets <http://twitter.com/mickaelistria>

11 years, 1 month

1
0
0 / 0

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-dev February 2012