Hi
System.load:
- for the user we still need to make some assembly goal that grabs
all the shared
and jni like libs and puts them in a lib directory. A small setup
script can then set
the appropriate ld_library_path or the like.
- for maven the nar plugin includes an integration test goal, which
runs after packaging,
and runs as part of maven, so it knows how to set the java.library.path
to run the tests. The lava.library.path is set to the produced jni/
so file
and all its dependencies.
Naming:
The artifactID and version are picked up from the "standard" maven
properties
file in the jar file.
Regards
Mark
On Jun 19, 2006, at 8:18 AM, Richard van der Hoff wrote:
Mark Donszelmann wrote:
The NAR gets unpacked in the local repository under the directory
where the
jar file is stored, so underneath a parent directory with that
version number.
Ah ha, I see. In that case, how does your System.load() call know
where to find the library? I guess it has knowledge of group,
artifact, version built into the java jar?
And if you have libraries which are linked at the native level, how
does the os library loader know where to find the prerequisite
libraries?
Cheers,
Richard
--
Richard van der Hoff <[EMAIL PROTECTED]>
Telephony Gateways Project Manager
Tel: +44 (0) 845 666 7778
http://www.mxtelecom.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
