[
https://issues.apache.org/jira/browse/MNG-6115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15884757#comment-15884757
]
Michael Osipov edited comment on MNG-6115 at 2/26/17 2:02 PM:
--------------------------------------------------------------
OK, this is not build time, this is runtime. For the shell script, you need to
make a difference at least between {{.so}} and {{.dylib}}. Looks good to me.
Distributions can add the shared library to {{/usr/lib}} or {{/usr/local/lib}}
and patch the shell script.
was (Author: michael-o):
OK, this is not build time, this is runtime. For the shell script, you need to
make a difference at least between {{.so}} and {.dylib}}. Looks good to me.
Distributions can add the shared library to {{/usr/lib}} or {{/usr/local/lib}}
and patch the shell script.
> 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-candidate
>
>
> 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)
