Uploaded image for project: 'Maven'
  1. Maven
  2. MNG-6115 Add Jansi native library search path to our start scripts to avoid extraction to temp file on each run
  3. MNG-6186

switch to improved HawtJNI

    XMLWordPrintableJSON

Details

    • Sub-task
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 3.5.0-beta-1
    • 3.5.2
    • Bootstrap & Build, Command Line
    • None

    Description

      calculating the directory where jansi native lib is available required a hack = copy/paste HawtJNI code https://git1-us-west.apache.org/repos/asf?p=maven.git;a=blobdiff;f=maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java;h=350fa61c5da633a04fa17c1ed7530096c4ad60ad;hp=b3367c177c91fae32831207ab4a568121da621f0;hb=181b0215aa1199e152db9d2c08b1a01436547805;hpb=809ba34055c70eab31876aad03c577e925fa2e6e

      This should become a HawtJNI feature (ie. library.jansi.path should point to lib/jansi-native and HawtJNI should find the right directory the same way it does it in classpath), then we'll be able to integrate it instead of hacking

      Attachments

        Issue Links

          Is contained by

          Bug - A problem which impairs or prevents the functions of the product. MNG-6205 Non-ascii chars in name element are displayed as question marks in Win CLI output (regression)

          • Major - Major loss of function.
          • Closed

          Activity

            People

              hboutemy Herve Boutemy
              hboutemy Herve Boutemy
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: