| Caching of build path jars [message #252780] |
Thu, 17 April 2008 19:51  |
Eclipse User |
|
|
|
Hi all,
I'm trying to figure out what dependencies I need for JBoss messaging
without using the jbossall-client.jar. I'm doing this by adding all the
jboss client jars to my classpath, then removing them one at a time and
running my test cases. I'm getting some strange behavior, here is what
I'm seeing.
1. Remove trove.jar and run program. Execution successful
2. Remove xmlsec.jar and run program. Execution fails due to
ClassNotFoundException. The missing class was in trove.jar.
3. Add trove .jar and run the program. Execution successful.
I'm seeing this quite a bit, its happened 3 times so far. I'm not
deleting the jars, just removing them from the build path. Does the build
path not refresh correctly when a jar is removed? I've even tried Project
-> Clean, but this doesn't seem to fix the issue. Is this a bug, or am I
missing a step?
thanks,
Todd
Eclipse Version: 3.3.1.v20070814
Java Version: 1.5.0_13-b05-237
Platform: OS X 10.5.1
|
|
|
| Re: Caching of build path jars [message #252813 is a reply to message #252780] |
Fri, 18 April 2008 18:26  |
| Eclipse User |
|
|
|
"Todd Nine" <todd.nine@gmail.com> wrote in message
news:509ce6edaf2315b7cea0cdd634a2fbf2$1@www.eclipse.org...
> Hi all,
> I'm trying to figure out what dependencies I need for JBoss messaging
> without using the jbossall-client.jar. I'm doing this by adding all the
> jboss client jars to my classpath, then removing them one at a time and
> running my test cases.
The *build* path is used for *building*, not running. When you run, the
runtime classpath is what matters. In this case since you refer to JBoss I
presume it's the server's runtime classpath that matters.
That runtime classpath is probably affected by what you do to the build
path, but it sounds like the linkage is not very tight.
|
|
|
Powered by
FUDForum. Page generated in 0.03092 seconds
Home