I'm seeing the same issue with:
java version 1.6.0_06
Java(TM) SE Runtime Environment (build 1.6.0_06-b02)
Java HotSpot(TM) Server VM (build 10.0-b22, mixed mode)
Maven version: 2.0.9
Java version: 1.6.0_06
OS name: linux version: 2.6.18-8.el5 arch: i386 Family: unix
Redhat Enterprise 5.x
Folks,
Apologies.
This looks like a Windows vs Linux problem associated with case sensitivity of filenames on Linux
not present on Windows.
Basically, the CBP file written to disk by the ODE processing is helloworld.cbp but a search is
made for a file HelloWorld.cbp. On Windows, this is no
apache headers in xmls and xsds without causing test case failures
--
Key: TUSCANY-2011
URL: https://issues.apache.org/jira/browse/TUSCANY-2011
Project: Tuscany
Issue Type
and xsds without causing test case failures
--
Key: TUSCANY-2011
URL: https://issues.apache.org/jira/browse/TUSCANY-2011
Project: Tuscany
Issue Type: Bug
include apache headers in xmls and xsds without causing test case failures
--
Key: TUSCANY-2011
URL: https://issues.apache.org/jira/browse/TUSCANY-2011
Project: Tuscany
@ws.apache.org
Sent: Thursday, July 27, 2006 9:39 AM
Subject: Re: Test case failures
Raymond was helping me with this yesterday. He noticed that if you run
the build from the respective subdirectory, the test succeeds. It seems
to only fail when the build is run from /java.
ant elder wrote:
I see
@ws.apache.org
Sent: Monday, July 24, 2006 10:57 PM
Subject: Re: Test case failures
Hi Raymond,
I am using: IBM 32-bit SDK and Runtime Environment for Windows,
Java
2 Technology Edition, Version 5.0
I tried your patch but the result is a new failure
1.5.0
Java(TM) 2 Runtime Environment, Standard Edition (build
pwi32dev-20060511 (SR2))
Thanks,
Raymond
- Original Message - From: Kevin Williams
[EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Monday, July 24, 2006 10:57 PM
Subject: Re: Test case failures
Hi
Sorry, the artifactId should be xercesImpl.
Can you try that?
Thanks,
Raymond
- Original Message -
From: Kevin Williams [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Monday, July 24, 2006 10:57 PM
Subject: Re: Test case failures
Hi Raymond,
I am using: IBM 32-bit SDK
pwi32dev-20060511
(SR2))
Thanks,
Raymond
- Original Message -
From: Kevin Williams [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Monday, July 24, 2006 10:57 PM
Subject: Re: Test case failures
Hi Raymond,
I am using: IBM 32-bit SDK and Runtime Environment for Windows, Java 2
PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Monday, July 24, 2006 10:57 PM
Subject: Re: Test case failures
Hi Raymond,
I am using: IBM 32-bit SDK and Runtime Environment for Windows, Java
2 Technology Edition, Version 5.0
I tried your patch but the result is a new failure
: Kevin Williams [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Monday, July 24, 2006 10:57 PM
Subject: Re: Test case failures
Hi Raymond,
I am using: IBM 32-bit SDK and Runtime Environment for Windows, Java
2 Technology Edition, Version 5.0
I tried your patch but the result is a new
/DocumentBuilderFactory.html#newInstance(),
the call should be successful.
Can you try SUN JDK as well?
Thanks,
Raymond
- Original Message -
From: Kevin Williams [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Tuesday, July 25, 2006 1:17 PM
Subject: Re: Test case failures
Hi Raymond,
I get the same
: Monday, July 24, 2006 10:57 PM
Subject: Re: Test case failures
Hi Raymond,
I am using: IBM 32-bit SDK and Runtime Environment for Windows, Java
2 Technology Edition, Version 5.0
I tried your patch but the result is a new failure
Hello,
Seeing the below error on java main trunk. Building on XP
Sun java full version 1.5.0_07-b03
rev 425055 on java
Maven version: 2.0.4
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Tuscany Build Tools
[INFO] SDO API
[INFO] SCA API
[INFO] Commonj
[INFO] OSOA
On Jul 24, 2006, at 7:30 AM, Rick wrote:
testSchedule
(org.apache.tuscany.core.services.work.jsr237.workmanager.ThreadPoolWo
rkManagerTestCase) Time elapsed: 0 sec ERROR!
java.lang.AssertionError:
Expectation failure on verify:
run(): expected: 1, actual: 0
at
Yea it is. I just checked in a fix. Please let me know if it works on
your machine, Rick.
Jim
On Jul 24, 2006, at 7:48 AM, Jeremy Boynes wrote:
On Jul 24, 2006, at 7:30 AM, Rick wrote:
testSchedule
(org.apache.tuscany.core.services.work.jsr237.workmanager.ThreadPoolW
orkManagerTestCase)
-
From: Jim Marino [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Monday, July 24, 2006 11:00 AM
Subject: Re: Java core test case failures?
Yea it is. I just checked in a fix. Please let me know if it works on
your machine, Rick.
Jim
On Jul 24, 2006, at 7:48 AM, Jeremy Boynes wrote
)
- Original Message - From: Jim Marino
[EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Monday, July 24, 2006 11:00 AM
Subject: Re: Java core test case failures?
Yea it is. I just checked in a fix. Please let me know if it works
on your machine, Rick.
Jim
On Jul 24, 2006, at 7:48 AM
: Re: Java core test case failures?
Yea it is. I just checked in a fix. Please let me know if it works
on your machine, Rick.
Jim
On Jul 24, 2006, at 7:48 AM, Jeremy Boynes wrote:
On Jul 24, 2006, at 7:30 AM, Rick wrote:
testSchedule
(org.apache.tuscany.core.services.work.jsr237
or tomorrow morning.
Ta
Meeraj
-Original Message-
From: Jim Marino [mailto:[EMAIL PROTECTED]
Sent: 24 July 2006 16:21
To: tuscany-dev@ws.apache.org
Subject: Re: Java core test case failures?
O.K. the easiest thing I think to do is what Jeremy mentioned and stub
out the Executor since
]
To: tuscany-dev@ws.apache.org
Sent: Monday, July 24, 2006 11:00 AM
Subject: Re: Java core test case failures?
Yea it is. I just checked in a fix. Please let me know if it
works on your machine, Rick.
Jim
On Jul 24, 2006, at 7:48 AM, Jeremy Boynes wrote:
On Jul 24, 2006, at 7:30 AM, Rick
16:21
To: tuscany-dev@ws.apache.org
Subject: Re: Java core test case failures?
O.K. the easiest thing I think to do is what Jeremy mentioned and stub
out the Executor since this is going to cause issues on different
machines. I've commented out the test cases for now and I'll go
back in
later
)
- Original Message - From: Jim Marino
[EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Monday, July 24, 2006 11:00 AM
Subject: Re: Java core test case failures?
Yea it is. I just checked in a fix. Please let me know if it works
on your machine, Rick.
Jim
On Jul 24, 2006, at 7:48 AM
After having trouble getting svn update to succeed I reloaded the entire
java tree. The first build attempt succeeded, I am almost certain :-),
but subsequent attempts fail with this error:
[surefire] Running org.apache.tuscany.databinding.impl.MediatorImplTestCase
[surefire] Tests run: 2,
: Monday, July 24, 2006 8:39 PM
Subject: Test case failures
After having trouble getting svn update to succeed I reloaded the entire
java tree. The first build attempt succeeded, I am almost certain :-),
but subsequent attempts fail with this error:
[surefire] Running
Subject: Test case failures
After having trouble getting svn update to succeed I reloaded the
entire java tree. The first build attempt succeeded, I am almost
certain :-), but subsequent attempts fail with this error:
[surefire] Running
org.apache.tuscany.databinding.impl.MediatorImplTestCase
Hi,
I ran into some test case failures with the trunk code in both Eclipse and
Maven (reported by my continumm build) related to the usage of java
assertions.
For example, in test case
org.apache.tuscany.spi.extension.ReferenceTestCase, we have the following
test:
public void testPrepare
, assertions
should not alter normal program execution.
I think I buy what the author says.
Thanks,
Raymond
- Original Message -
From: Yang ZHONG [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Thursday, July 20, 2006 3:11 PM
Subject: Re: Java assertion related test case failures
I
@ws.apache.org
Sent: Thursday, July 20, 2006 3:11 PM
Subject: Re: Java assertion related test case failures
I hope our code are not designated to run in some specifically
configured
JVM.
Since JVMs may turn assertion on or off, I'm not sure
AssertionError should
be an expected behavior
to
be launched with -ea. Making sense?
Thanks,
Raymond
- Original Message -
From: Jeremy Boynes [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Thursday, July 20, 2006 4:00 PM
Subject: Re: Java assertion related test case failures
We covered assertions a little in the exception
assertion related test case failures
I hope our code are not designated to run in some specifically
configured
JVM.
Since JVMs may turn assertion on or off, I'm not sure
AssertionError should
be an expected behavior in general.
Dedicated exceptions and errors are much better protocol, e.g
If you like my previous proposal, here's the patch I tried.
Thanks,
Raymond
- Original Message -
From: Raymond Feng [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Thursday, July 20, 2006 4:14 PM
Subject: Re: Java assertion related test case failures
If the purpose of the test
: Jeremy Boynes [EMAIL PROTECTED]
To: tuscany-dev@ws.apache.org
Sent: Thursday, July 20, 2006 4:37 PM
Subject: Re: Java assertion related test case failures
On Jul 20, 2006, at 4:14 PM, Raymond Feng wrote:
If the purpose of the test case is to verify the assert, I suggest
that we use
-dev@ws.apache.org
Sent: Thursday, July 20, 2006 4:37 PM
Subject: Re: Java assertion related test case failures
On Jul 20, 2006, at 4:14 PM, Raymond Feng wrote:
If the purpose of the test case is to verify the assert, I
suggest that we use ClassLoader.setClassAssertionStatus
(targetClassName
35 matches
Mail list logo
