jbosscache-dev July 2007

jbosscache-dev@lists.jboss.org

8 participants
130 discussions

Start a nNew thread

jboss-cache-testsuite-140 build.14 Build Successful

by jboss-qa-internal＠redhat.com

18 years, 12 months

1
0
0 / 0

jboss-cache-testsuite-jdk16 Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

18 years, 12 months

1
0
0 / 0

javadocs for XmlHelper?

by Galder Zamarreno

Hi, XmlHelper methods don't have any Javadocs which means that unless you read through the implementation, you can't know whether they can return null or not, or whether they return empty strings...etc. I think we should write them so that the rest of the code does not over/under checks the values retrieved from XML. Example: String readStringContents() Looking at the implementation, I can see null will never be returned from the method call. I have to check for either empty or non empty Strings. Cheers,

18 years, 12 months

2
2
0 / 0

jboss-cache-testsuite Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

18 years, 12 months

1
0
0 / 0

Cutting JBC Cayenne 1.4.1.SP4

by Manik Surtani

Guys, The 1.4.0 branch is pretty stable [1] at the moment and we have some important fixes [2] there. Outstanding, waiting for closure are: JBCACHE-1048 (Brian, is this important for 1.4.1.SP4?) JBCACHE-1103 (Jimmy, any feedback on this, did you get feedback on this fix?) JBCACHE-1067 - I still haven't confirmed whether this is a bug in the first place; may defer this) Hopefully once we have these closed we can look at cutting this release. Cheers, Manik [1] http://cruisecontrol.jboss.com/cc/buildresults/jboss-cache- testsuite-140 [2] http://tinyurl.com/28ox9f -- Manik Surtani Lead, JBoss Cache JBoss, a division of Red Hat

18 years, 12 months

2
1
0 / 0

jboss-cache build.1110 Build Successful

by jboss-qa-internal＠redhat.com

18 years, 12 months

1
0
0 / 0

jboss-cache-testsuite-140 build.13 Build Fixed

by jboss-qa-internal＠redhat.com

19 years

1
0
0 / 0

poll: java tag for shortcut set up methods created only for UT purposes?

by Galder Zamarreno

Hi, Quite often when contributing in JBoss projects, I create extra protected methods (i.e. setters) to make my life a lot simpler when coding unit tests. People have different opinions (such as the messaging guys who believe every single UT should be coded to the public API), but I personally believe that you shouldn't be necessarily forced to set up a complete environment to run a specific UT. There're a lot of situations where it makes sense to do this, but others where not, and in the latter, having "shortcut" set up methods helps. Sometimes, this "shortcut" methods are already there but other times are not, hence my tendency to create these protected methods. Now, wouldn't it be nice if there's a Java tag that could be applied to this methods to indicate that: "this method is only here to make my unit-testing-coding-life easier and so, should only be called from unit tests, not from production code" I had a quick look around and could not find anything. Do people agree/disagree with creating such tag? Cheers, Galder

19 years

3
3
0 / 0

jboss-cache-testsuite-jdk16 Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

19 years

1
0
0 / 0

jboss-cache-testsuite Build Completed With Testsuite Errors

by jboss-qa-internal＠redhat.com

19 years

1
0
0 / 0

← Newer
1
...
5
6
7
8
9
10
11
12
13
Older →

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosscache-dev July 2007