Claude Brisson schrieb:
There may be several classpaths implied, for instance the one used to
run the testsuite and the one used to launch junit from within the
testsuite.
Matthias, have you any insight on the use of some such inner classpath?
Unfortunally, the implementation of the testsuite framework is pretty
old and hacky, but it has a very simple main method that includes:
if (text) {
junit.textui.TestRunner.main(testCaseName);
} else {
junit.swingui.TestRunner.main(testCaseName);
}
So I looked into the old (3.8) junit code bzw. documentation and found
the problem: I had to set the set the "non-loading" switch, see
http://junit.sourceforge.net/junit3.8.1/index.html
So now everything works fine, thanks for your help!
Regards,
matthias
Claude
Le lundi 05 novembre 2007 à 20:32 -0800, Will Glass-Husain a écrit :
Sounds to me very much like a classloader problem. We've seen this type of
error with Velocity 1.4 or if there are multiple velocity jars loaded by
different class loaders.
WILL
On 11/5/07, Matthias Epheser <[EMAIL PROTECTED]> wrote:
Nathan Bubna schrieb:
Just for reference, what version of Velocity are you using?
it is velocity-1.5
On 11/5/07, Matthias Epheser <[EMAIL PROTECTED]> wrote:
Claude Brisson schrieb:
Have you checked that there isn't any older version of Velocity
somewhere in the classpath that junit swing gui is using?
What happens for instance if you put your velocity jar first in the
classpath?
yep, there is definitely only one velocity.jar present. In fact, as
mentioned, it is exectly the same classpath as it is using the textui.
The main class is just started without an optional "-text" argument.
I am using the old ant build to avoid maven-specific dependeny issues.
So only the jars in my "lib" directory are used.
That's why I'm so confused. Tried it with velocity.jar as first
classpath item too.
hth
matthias
Claude
Le lundi 05 novembre 2007 à 16:12 +0100, Matthias Epheser a écrit :
Hi list,
I'm currently implementing a velocity integration into the source
generation process of the castor framework (www.castor.org). So I
generate java POJOs out a xml schema.
The castor framework includes a testsuite that uses an embedded junit
runner. I encouter a very strange classpath issue here:
- running the testsuite in textmode (using junit.textui.TestRunner),
everything works fine as expected
- running the testsuite in swing mode (using
junit.swingui.TestRunner), I get the following exception during
Velocity
init:
[error] The specified class for ResourceManager
(org.apache.velocity.runtime.resource.ResourceManagerImpl) does not
implement org.apache.velocity.runtime.resource.ResourceManager;
Velocity
is not initialized correctly.
java.lang.Exception: The specified class for ResourceManager
(org.apache.velocity.runtime.resource.ResourceManagerImpl) does not
implement org.apache.velocity.runtime.resource.ResourceManager;
Velocity
is not initialized correctly.
at
org.apache.velocity.runtime.RuntimeInstance.initializeResourceManager
(RuntimeInstance.java:589)
at
org.apache.velocity.runtime.RuntimeInstance.init(RuntimeInstance.java
:241)
at
org.apache.velocity.runtime.RuntimeSingleton.init(
RuntimeSingleton.java:113)
at org.apache.velocity.app.Velocity.init(Velocity.java:83)
The only difference between both executions is the TestRunner class,
everything else (classpath, used jars etc.) is exactly the same..
Has someone stepped over a similar problem?
Regards
matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
