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 to avoid extraction to temp file on each run
Date Sun, 05 Mar 2017 11:49:33 GMT

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

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

[~stephen.alan.connolly@gmail.com], please test this on macOS. I think that the code won't
work for you because binaries are univeral on macOS. The code ignores that fact.

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

Mime
View raw message