No. The "so" comes from reading the native plugin's jelly script's
native:install goal:
...
<ant:property name="libdir__"
value="${maven.repo.local}/${pom.artifactDirectory}/so"/>
<ant:mkdir dir="${libdir__}"/>
<ant:copy file="${maven.build.dir}/native/lib${pom.artifactId}-
${pom.currentVersion}.so" tofile="${libdir__}/lib${pom.artifactId}-
${pom.currentVersion}.so" overwrite="true"/>
...
It puts the shared library in the ${artifactId}/so directory which lead me
to believe that Maven do something clever like put the library "so"
directory on the java.library.path. I wonder why it's so instead of
something consistent with your <type>s naming scheme, e.g. sos, or libs or
the like? Didn't mean to distract the dev list, keep up the good work. I'll
just move along to where the users skulk about....
Corey
-----Original Message-----
From: matthew.hawthorne [mailto:[EMAIL PROTECTED]
Sent: Wednesday, March 03, 2004 5:01 PM
To: Maven Developers List
Subject: Re: Projects with Native Code...
Klaasmeyer, Corey M wrote:
> I'm using Maven for a couple projects with native components. Does the
maven
> local repository handle native shared libraries? For example, if I
download
> a project with a shared library in the "<repo>/<artifactId>/so" directory,
> does maven add the library to the path, so that the JVM can load it?
This question is probably a better fit on the users list.
As far as I know, Maven doesn't do anything with native libaries.
I've never seen a <repo>/<artifactId>/so directory -- is this something
that you created manually?
If so, then the only way Maven would put it in the path is if you did it
manually in your maven.xml -- "so" directories aren't a part of Maven's
standard structure.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
