| -> Library Plugin for Digester and mockobjects [message #146508] |
Mon, 01 March 2004 07:16  |
Eclipse User |
|
|
|
Hi there,
I 've added a library plugin project and added all the required libraries
to it and referred to it from project A .
Since I got compile-errors (Project A) I 've added the libraries to the
classpath (thinking eclipse can not simply recognize it during PDE
programming sessions). So I was able to create test cases and to avoid
Plugin-Test runs. But after getting through most of the work and the
current iteration came to an end, I wanted to run the complete test suite.
Well and now it turns out that the library plugin does not work. I played
around with the plugin.xml and build.properties and exported the
plugin to see what it looks like and everything looks like it was expected,
but project A does not find any of the classes (throwing NoClassDefErrors
at me all the time).
So the question is, where is the bad guy?
The tags for the mock api looks like this:
<runtime>
[...]
<library name="mockobjects-core-0.09.jar">
<export name="*"/>
</library>
<library name="mockobjects-jdk1.4-0.09.jar">
<export name="*"/>
</library>
<library name="mockobjects-alt-jdk1.4-0.09.jar">
<export name="*"/>
</library>
</runtime>
The jars are all placed in the plugins main directory.
The build.properties look like:
bin.includes = plugin.xml,\
commons-beanutils.jar,\
commons-collections-3.0.jar,\
commons-digester-1.5.jar,\
commons-logging-api.jar,\
commons-logging.jar,\
log4j-1.2.8.jar,\
mockobjects-alt-jdk1.4-0.09.jar,\
mockobjects-core-0.09.jar,\
mockobjects-jdk1.4-0.09.jar
Can someone help me? It keeps me away from the lucky-land! :(
Thanks,
Martin (Kersten)
|
|
|
|
|
|
|
|
|
| Re: -> Library Plugin for Digester and mockobjects [message #147029 is a reply to message #146713] |
Tue, 02 March 2004 13:09  |
| Eclipse User |
|
|
|
Originally posted by: smesh.openrules.com
Hi Martin,
> Are there any resources about learning what a classpath container is
> and how it works?
Sorry, I read about this mostly from the source code. (bad practice:)
> I think I know why things are going crazy right now. There are two
> libraries involved. First the org.junit and the com.mockobjects
> (contributing the mock libraries). But running the testcases of a project
> depending on both results to org.junit classloader can not find any classes
> of com.mockobjects since the classloader looks at the dependency tree
> of org.junit. and also on the plugin depending on org.junit.
>
> Adding the mocklibraries to the project (not using a library plugin) works
> great. Wired. So my question is what is a classpath container (I only
> three or four sentences out of the context help and also some sentences
> from Developers guide to eclipse (book).
AFIAK, junit and plugin classloader are heavy-classloader-usage-guys.
It seems, they bite each other in your case.
Sam Mesh - http://openrules.com
Life is very short, and there's no time,
For coding and testing, my friend.
|
|
|
Powered by
FUDForum. Page generated in 0.07236 seconds
Home