Rickard �berg wrote:
>
> Hi!
>
> Vadim Tkachenko wrote:
> > Let me guess: you are able to successfully set the classpath when you
> > call
> > the build.bat, and then you don't have to worry about it when you run
> > the
> > run.bat, right?
>
> I'm not sure I understand. What is the question?
>
> build.bat sets up the classpath it needs, and run.bat only uses one jar
> (the rest is added dynamically to classpath).
>
> > Now, what if I rebooted the box in between?
>
> Not sure I understand the problem...
Well, to the best of my understanding the problem as it is now is that
run.jar contains the classpath clause pointing to ../lib/jmxri.jar, but
it is not there, as a matter of fact, it is nowhere in the
${srcdir}/build directory tree. I'll try to find and fix the cause, but
if you get to it faster, that'd be cool ;)
I suspect you didn't see this problem before just because the build.bat
sets the classpath in such a way that later you always have jmxri.jar in
your path.
> > And again, the run.sh is missing ;)
>
> Yup. Care to fix? ;-)
Sure ;) As soon as I get to it.
> > And I guess right now the structure is a little bit scewed up because of
> > the directory structure changes, so I'll take it easy ;)
>
> Why is it screwed up? I thought I finally got it covered...
Most probably, on Windows side it's OK. I'll take care of the rest.
> Rickard
--vt
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
