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 2017/03/04 23:49:46 UTC

[jira] [Updated] (MNG-6115) Add Jansi native library search path to our start scripts to avoid extraction to temp file on each run

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

Hervé Boutemy updated MNG-6115:
-------------------------------
    Summary: Add Jansi native library search path to our start scripts to avoid extraction to temp file on each run  (was: Add Jansi native library search path to our start scripts)

> Add Jansi native library search path to our start scripts to avoid extraction to temp file on each run
> ------------------------------------------------------------------------------------------------------
>
>                 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)