maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Osipov (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MNG-6115) Add Jansi native library search path to our start scripts
Date Mon, 02 Jan 2017 20:19:58 GMT

    [ https://issues.apache.org/jira/browse/MNG-6115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15793434#comment-15793434
] 

Michael Osipov commented on MNG-6115:
-------------------------------------

[~hboutemy], can I handle this over to you to be squashed with MNG-3507 during master cleanup?
This feels right to do so. We can discuss wether this should be in {{${maven.home\}/lib}}
or {{${maven.home\}/lib/ext}}.

> 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)

Mime
View raw message