From issues-return-144052-archive-asf-public=cust-asf.ponee.io@maven.apache.org Mon Jan 14 00:44:04 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 65EE8180674 for ; Mon, 14 Jan 2019 00:44:04 +0100 (CET) Received: (qmail 32701 invoked by uid 500); 13 Jan 2019 23:44:03 -0000 Mailing-List: contact issues-help@maven.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@maven.apache.org Delivered-To: mailing list issues@maven.apache.org Received: (qmail 32690 invoked by uid 99); 13 Jan 2019 23:44:03 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 13 Jan 2019 23:44:03 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id E5D73C03A6 for ; Sun, 13 Jan 2019 23:44:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.501 X-Spam-Level: X-Spam-Status: No, score=-109.501 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id l3qG-5faSz4G for ; Sun, 13 Jan 2019 23:44:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id 912BB5F404 for ; Sun, 13 Jan 2019 23:44:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id CE792E265A for ; Sun, 13 Jan 2019 23:44:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 561CB2559E for ; Sun, 13 Jan 2019 23:44:00 +0000 (UTC) Date: Sun, 13 Jan 2019 23:44:00 +0000 (UTC) From: "Sylwester Lachiewicz (JIRA)" To: issues@maven.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (MNG-5448) Putting dll/so-type dependencies on java.library.path by default MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/MNG-5448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16741685#comment-16741685 ] Sylwester Lachiewicz commented on MNG-5448: ------------------------------------------- This issue has been auto closed because it has been inactive for a long period of time. If you think this issue still applies, retest your problem with the most recent version of Maven and the affected component, reopen and post your results. > Putting dll/so-type dependencies on java.library.path by default > ---------------------------------------------------------------- > > Key: MNG-5448 > URL: https://issues.apache.org/jira/browse/MNG-5448 > Project: Maven > Issue Type: Bug > Reporter: Markus Karg > Priority: Major > > Many people are using Maven to build products that are using native dependencies (e. g. using JNI directly or indirectly). These people have to declare in some way this dependency, so Maven will download the DLL/SO to [target]. But what they also need is to tell Java that the target folder has to be scanned for the DLL/SO, hence they need to set java.library path. > There are several solutions but all of them lack one thing: They are no default but always do "tricks". This is a problem, because: > * m2e needs to tell Eclipse where to find DLLs. > * There might be other tools that want to read or write the POM. > * How should different tools understand that DLL dependencies are to be put on java.library.path if there is no STANDARD way to find this information in the POM? > The only "real" solution would be that Maven 3.1 clearly defines the one and only unique way! > In my opinion the way clearly means: > * Clearly define that any dll and exe dependencies MUST be put to [target/native] and that [target/native] MUST be part of java.library.path! > That way, it will become most simple to use any DLL/SO as a dependency, either Maven-built or not. And it will be absolutely clear to m2e and any other tools that such dependencies must be told to Eclipse and other environments as to be put on the java.library.path! > I do not say that it must exactly work THIS way, but what I really like to say is that Maven MUST provide ONE and EXACTLY ONE clear and unambiguous way to tell ANY POM-reading tool that a dependency is a DLL/SO and MUST be found on java.library.path in turn. > This is NOT up to the POM author, as it is pretty clear that ANY DLL/SO that is a dependency only serves the single and simple purpose of BEING on java.library.path -- otherwise one would not have made it a dependency! > I mean, ANY JAR dependency is put on the CLASSPATH already, so it makes pretty much sense to do the same with DLL/SO dependency and java.library.path! -- This message was sent by Atlassian JIRA (v7.6.3#76005)