Another (more preferable for me) way could be set a specific locale and
compare to the message for this locale
Thanks,
Mikhail.
2006/5/13, Andrew Zhang [EMAIL PROTECTED]:
Hello,
If we really decide to test exception message, I think we could write test
case as follows:
public void test_f(){
On Saturday 13 May 2006 02:53 Elford, Chris L wrote:
I'll need to look at this a bit more closely. Some of the
CompiledMethodLoad data for secondary jit events look a bit strange. It
sounds like support is still early so this type of issue will likely be
resolved as the VM and JIT evolve?
(Apologies if your note was not directed to me...)
Magnusson, Geir wrote:
Is any license included?
Nope, no license file and no block comments in the source files (that I
checked).
If not, just add that
Not my prerogative to license Alexander's code :-)
I'll put pointers on the wiki that
Tim Ellison wrote:
(Apologies if your note was not directed to me...)
Magnusson, Geir wrote:
Is any license included?
Nope, no license file and no block comments in the source files (that I
checked).
If not, just add that
Not my prerogative to license Alexander's code :-)
I didn't
Hello, Mikhail
org.apache.harmony.luni.util.Msg has already handled locale issue.
So it's not neccessary to get locale inforamtion again in test case, and
then get i18n message.
For example, following code is from java.net.HttpURLConnection.java
method setRequestMethod:
if (connected)
I have recently built jchevm and tried to run eclipse with it. When
loading a error window appeared. It looks like a bug or unimplemented
functionality.
I have taken a look at list of loaded native libraries. It looks
classpath is used for system classes instead of harmony classlib. I
remember,
Hi Andrew,
Thanks for your comments and interesting feedback. The ideas in this spec
are certainly open to debate and input from everyone. As we well know,
modularity is a great goal which has many merits...testability, ease of
development, plug and play etc. However it is less easy to achieve
I agree with your analysis. +1 from me.
Regards,
Tim
Stepan Mishura wrote:
On 5/12/06, *Jimmy, Jing Lv* wrote:
SNIP
In this case, though replace StringIndexOutOfBoundsException with
ArrayIndexOutOfBoundsException is surely better, it seems it is
internal
Andrey Chernyshev wrote:
snip
(1) Do we need to keep the 'main' directory in every module? If we
need to have a distinction between tests and sources, may be just pull
tests one level up and have something like:
archive/
src/
native/
java/
tests/
