[
https://issues.apache.org/jira/browse/MNG-6115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15895729#comment-15895729
]
Hervé Boutemy commented on MNG-6115:
------------------------------------
I didn't look previously, but yes the libs come from
{{META-INF/native/<arch>/libjansi.<type>}} in {{jansi-1.13.jar}}
you're right, we should probably extract them from the jar in our distribution
if we want to avoid temporary extracts: this idea about {{lib/ext}} and users
to put files in it just won't work
the only question I have now is: how to select the file at runtime?
I'll have a look at jansi source code to see if there is a better integration
trick than {{library.jansi.path}} that would find automatically the value of
{{<arch>}}
> Add Jansi native library search path to our start scripts
> ---------------------------------------------------------
>
> Key: MNG-6115
> URL: https://issues.apache.org/jira/browse/MNG-6115
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build, Command Line
> Reporter: Michael Osipov
> Assignee: Hervé Boutemy
> Fix For: 3.5.0-alpha-2
>
>
> By default Jansi extracts the native, shared library to temp which results in
> unnecessary file I/O and a huge amount of temp files when Maven is run very
> often. One can avoid that by adding
> {{-Dlibrary.jansi.path=$\{MAVEN_HOME\}/lib/ext}} to the start script. The
> user has to copy the {{libjansi.so}} or {{jansi.dll}} once and will avoid the
> overhead.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
