You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2016/12/26 15:10:58 UTC

[jira] [Issue Comment Deleted] (MNG-6115) Add Jansi native library search path to our start scripts

     [ https://issues.apache.org/jira/browse/MNG-6115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Hervé Boutemy updated MNG-6115:
-------------------------------
    Comment: was deleted

(was: SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #11 (See [https://builds.apache.org/job/maven-3.x%20Jigsaw/11/])
[MNG-6115] Add Jansi native library search path to our start scripts (michaelo: rev 3d4cd94450e167953c40028eaf1c71ce7a7cafc7)
* (edit) apache-maven/src/bin/mvn.cmd
* (edit) apache-maven/src/bin/mvn
)

> 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
>    Affects Versions: 3.4.0
>            Reporter: Michael Osipov
>            Assignee: Michael Osipov
>             Fix For: 3.4.0
>
>
> 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}} 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.4#6332)