Fantastic, thanks for your efforts Chris, that was in fact the
problem, I removed all trace of those files, and it works just fine!!!
Now I just need to figure out why my system was still displaying
these symptons despite updates being done...
once again thanks for your help,
Ross.
On 15
Wild speculation: but perhaps this is just a classpath issue. Perhaps the
on the fly compiler used by Jetty (and Tomcat in the case of the URL i
sent earlier) tries to build a complete list of resources available from
every item in the classpath before compiling JSPs, and in your case these
dylib
Hi all,
yes I suspect that may be the problem, I will go through some web
guides on Java and Mac, see if anythingcomes up..
thanks,
Ross.
On 15 Aug 2006, at 13:44, Erik Hatcher wrote:
Just as a data point, my team (3 of us) develop on OS X using Solr
with no problems. Two of us are on M
Just as a data point, my team (3 of us) develop on OS X using Solr
with no problems. Two of us are on MacBook Pro's and one poor soul
is on a PowerBook. I know that doesn't help, and I do recall
stumbling into this particular issue or one very much like it a long
while ago (not Solr relat
A .dylib file isn't a zip or a jar at all, it's a native OS X shared
library. I have absolutely NO idea why Solr is trying to open it. Are
you deploying just the stock version, or did you add some of your own
code to it?
-MB
On Aug 15, 2006, at 2:06 AM, Ross McDonald wrote:
Thanks for
: oh dear.. maybe this is corrupt?
:
: A 'jar tvf' generates no output, once again indicating that the file
: is not a valid jar,
maybe ... i'm not convinced that file is suppose to be a zip/jar (i don't
really get "dylib" files) ... just that java seems to think it should be.
here's an interest
Thanks for the quick response guys,
I am using jdk 1.5, and am ensuring use of this jdk by typing the
full path.
As regards doing an 'unzip -l' on the file it indeed generates an
error..
/usr/local/lib rossputin$ unzip -l libsvnjavahl-1.0.0.0.dylib
Archive: libsvnjavahl-1.0.0.0.dylib
: The older version of Jetty that we are using requires the JDK version,
: not the JRE version of 'java' so it can compile JSPs via javac. Maybe
: that's be the problem? Try typing the full path to the java
: executable to verify.
Perhaps ... but this seems like an awfully strnage exception to
The older version of Jetty that we are using requires the JDK version,
not the JRE version of 'java' so it can compile JSPs via javac. Maybe
that's be the problem? Try typing the full path to the java
executable to verify.
-Yonik
On 8/14/06, Ross McDonald <[EMAIL PROTECTED]> wrote:
Hi all,
I
