So in this class, the build action (according to Max) is occasionally
failing. The problem is the unit test page doesn't provide me enough
information. My build action actually returns a MultiStatus object...
but I'm not sure how to get the details of this status object to be
presented somewhere in the build / test suite failure section.
Currently I receive the MultiStatus object, make a CoreException out of
it, then make a RuntimeException out of that and throw it up to the
testing framework... but as you can see, all I get is the stacktrace of
the Runtime / Core exceptions and I don't get the status details inside
the Core exception.
Anyone have any ideas how I can modify this test case to allow the
details of the CoreException's status object to be seen somewhere in the
test failure page?
To help me gauge how much work is left in
https://jira.jboss.org/jira/browse/JBIDE-3557, I have modified all the
projects' .settings (in my local workspace) to enable NON-NLS
(unexternalized string) warnings, and counted the number of warnings for
Here's a spreadsheet if anyone's interested:
I would ask for help to count these warnings automatically as part of
the Hudson build, but it's probably not worth the effort for a temporary
issue. (Tracking for all sorts of warnings might be though...)
However, I do think it would be worthwhile to enable NON-NLS *errors* in
the Hudson build, progressively, as each module is cleaned up. This
would help to ensure the module stays clean. Does this sound
Also, it would be a big help if everyone can keep an eye out for NON-NLS
warnings when changing code (or writing new code). This will save me
having to go back to modules I've already finished, because
unexternalized strings have crept in. Thanks!
 It would be easy to enable NON-NLS errors in the projects' .settings
for everyone, but we probably don't want to force everyone to
internationalise their code before running a local unit test.
Senior Software Engineer
Engineering - Internationalisation
I just posted
http://in.relation.to/Bloggers/JBossTools31MilestoneReleased - Thanks to
everyone working on helping getting M1 ready and out of the door.
We released this later than expected (2 weeks late) mostly because of
adjusting to Eclipse 3.5 and since we were trying to reach zero failures
test run. Unfortunately we did not make it to zero - but we got pretty
darn close (1 failure because of Java 5 and Java 6 differences) , and
thus I did
not want to hold back M1 just for this single error.
Operation Green Build will thus continue and I hope you are all watching
the build mails to be sure we are not regressing and if an failure occurs in
an area you can help out in please have it as your first priority to fix
test failures and keep the test suite growing with relevant tests.
We should reach the magic Zero tests failed as soon as possible so we
can start relying on the feedback it gives.
Thanks again and you can now all consider trunk fully open (it was never
really frozen :) for new features and tests!
Sometimes we need icons or some graphic elements for JBDS
I just need to know who is responsible for this work.
E.g. I need icons for Palette (https://jira.jboss.org/jira/browse/JBIDE-4308)
May I ask Alexey Dmitriev for this, and will this work paid him?
Or it will be someone else?
I've been working on the N&N and i'm still missing input from Denny
about ESB and Dart about Smooks.
Especially the jira's related to Smooks are very short on any detail.
Could you please complete the new and noteworthy before Friday evening ?
I also did not receive anything from Rob and Snjezana, but their jira's
were descriptive enough to make the job easy for me to do.
Thanks to Alexey and Maxim for the Seam, JSF and visual page editor news
I have committed the current Whats new and noteworthy for the M1 release
(being announced on monday).
let me know if I forgot something (feel free to add it /fix it directly