maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <>
Subject [jira] [Commented] (MNG-6115) Add Jansi native library search path to our start scripts
Date Sat, 04 Mar 2017 23:47:45 GMT


Hervé Boutemy commented on MNG-6115:

[~michael-o] "I would people expect to put the library to /usr/local/lib once": perhaps you
can tell that to FreeBSD advanced users, who are used to tweak everything. But you can't expect
such work from normal users, this "won't scale" as you say

I implemented the extraction of native libs in {{$maven.home/lib/jansi-native}} during distribution
build (with maven-dependency-plugin + assembly configuration) then {{library.jansi.path}}
calculation from Maven embedder's MavenCli in
Please review and confirm this is the way to go for now: I'll propose patches to HawtJNI to
support such scenario and avoid us to copy/paste some platform calculation algorithm

> Add Jansi native library search path to our start scripts
> ---------------------------------------------------------
>                 Key: MNG-6115
>                 URL:
>             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 {{}} or {{jansi.dll}} once and will avoid the overhead.

This message was sent by Atlassian JIRA

View raw message