Update : Looked at Java Preferences in Utilities section:It stipulates : Java Applications, Web Start applications and command line tools use 'this order' to determine the most appropriate version to use..The panel has the 64 bit version listed above the 32 bit one. So I'd assume 64 bit was being chosen.
--- On Thu, 30/9/10, Jeremy Flowers <[email protected]> wrote: From: Jeremy Flowers <[email protected]> Subject: Re: Archiva Mac OS X console status warning (JNI stuff) To: [email protected] Date: Thursday, 30 September, 2010, 11:36 Not sure how to tell... java -version yields:java version "1.6.0_20"Java(TM) SE Runtime Environment (build 1.6.0_20-b02-279-10M3065)Java HotSpot(TM) 64-Bit Server VM (build 16.3-b01-279, mixed mode) I think it's down to this:Wrapper (Version 3.2.3) http://wrapper.tanukisoftware.org I saw some similar posts 1) on Stack Overflow unrelated to Archivahttp://stackoverflow.com/questions/1309879/java-service-wrapper-3-2-3-on-mac-os-x-64-bit 2) IntelliJhttp://youtrack.jetbrains.net/issue/TW-8212 --- On Thu, 30/9/10, Deng Ching <[email protected]> wrote: From: Deng Ching <[email protected]> Subject: Re: Archiva Mac OS X console status warning (JNI stuff) To: [email protected] Date: Thursday, 30 September, 2010, 11:28 Are you running it on 32-bit or 64-bit? It could be similar to this: http://www.mail-archive.com/[email protected]/msg01192.html Thanks, Deng On Thu, Sep 30, 2010 at 6:13 PM, Jeremy Flowers <[email protected]> wrote: > WARNING - Unable to load the Wrapper's native library because none of the > following files: > libwrapper-macosx-x86-64.jnilib > libwrapper-macosx-universal-64.jnilib > libwrapper.jnilib > could be located on the following java.library.path: > /opt/apache-archiva-1.3.1/lib > Please see the documentation for the wrapper.java.library.path > configuration property. > System signals will not be handled correctly. > > Googling didn't yield a result. > Suggestion: > Wouldn't it make more sense to have URL to section of documentation in > message? > Question: > Can someone show me where this is located in the documentation? > > Cheers. > > >
