Return-Path: 
 <issues-return-85497-apmail-maven-issues-archive=maven.apache.org@maven.apache.org>
X-Original-To: apmail-maven-issues-archive@minotaur.apache.org
Delivered-To: apmail-maven-issues-archive@minotaur.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 11D519C3E
	for <apmail-maven-issues-archive@minotaur.apache.org>;
 Sun,  2 Jun 2013 14:39:32 +0000 (UTC)
Received: (qmail 69488 invoked by uid 500); 2 Jun 2013 14:39:31 -0000
Delivered-To: apmail-maven-issues-archive@maven.apache.org
Received: (qmail 69272 invoked by uid 500); 2 Jun 2013 14:39:31 -0000
Mailing-List: contact issues-help@maven.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@maven.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@maven.apache.org>
List-Post: <mailto:issues@maven.apache.org>
List-Id: <issues.maven.apache.org>
Reply-To: dev@maven.apache.org
Delivered-To: mailing list issues@maven.apache.org
Received: (qmail 69128 invoked by uid 99); 2 Jun 2013 14:39:30 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Jun 2013 14:39:30 +0000
X-ASF-Spam-Status: No, hits=-0.0 required=5.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: local policy)
Received: from [63.246.24.159] (HELO codehaus01.managed.contegix.com)
 (63.246.24.159)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 02 Jun 2013 14:39:24 +0000
Received: from codehaus01 (localhost.localdomain [127.0.0.1])
	by codehaus01.managed.contegix.com (Postfix) with ESMTP id 45B73B073F
	for <issues@maven.apache.org>; Sun,  2 Jun 2013 09:39:03 -0500 (CDT)
Date: Sun, 2 Jun 2013 09:39:03 -0500 (CDT)
From: "Robert Scholte (JIRA)" <jira@codehaus.org>
To: issues@maven.apache.org
Message-ID: 
 <JIRA.112195.1278702530741.143.1370183943281@codehaus01.managed.contegix.com>
In-Reply-To: <JIRA.112195.1278702530741@codehaus01.managed.contegix.com>
References: <JIRA.112195.1278702530741@codehaus01.managed.contegix.com>
Subject: [jira] (MNG-4723) scope="system" errors are difficult to diagnose
 because the error message is wrong
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 22cf62d5d84cf5bea94eb3b65e0ebd09
X-Virus-Checked: Checked by ClamAV on apache.org


     [ https://jira.codehaus.org/browse/MNG-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte updated MNG-4723:
--------------------------------

    Description: 
The following pom contents:
{code:xml}
  <dependencies>
    <dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>3.8.1</version>
      <scope>system</scope>
      <systemPath>c:/x/y/x</systemPath>
    </dependency>
  </dependencies>
{code}
generates the output:

{noformat}
[INFO] Failed to resolve artifact.

Missing:
----------
1) junit:junit:jar:3.8.1

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=junit -DartifactId=junit -Dversion=3.8.1 -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there:
      mvn deploy:deploy-file -DgroupId=junit -DartifactId=junit -Dversion=3.8.1 -Dpackaging=jar -Dfile=/path/to/file -Du
rl=[url] -DrepositoryId=[id]

  Path to dependency:
        1) org.home.mvnsample:mvnsample:jar:1.0-ALPHA2
        2) junit:junit:jar:3.8.1

----------
1 required artifact is missing.

for artifact:
  org.home.mvnsample:mvnsample:jar:1.0-ALPHA2

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)
{noformat}


This implies that the {{junit.jar}} is being sought in Maven Central, whereas in fact it is supposed to be in a local directory.

It would be a lot easier to debug errors in the systemPath if the error message showed where Maven was actually looking for it.


  was:
The following pom contents:

  <dependencies>
    <dependency>
      <groupId>junit</groupId>
      <artifactId>junit</artifactId>
      <version>3.8.1</version>
      <scope>system</scope>
      <systemPath>c:/x/y/x</systemPath>
    </dependency>
  </dependencies>

generates the output:

=================================================
[INFO] Failed to resolve artifact.

Missing:
----------
1) junit:junit:jar:3.8.1

  Try downloading the file manually from the project website.

  Then, install it using the command:
      mvn install:install-file -DgroupId=junit -DartifactId=junit -Dversion=3.8.1 -Dpackaging=jar -Dfile=/path/to/file

  Alternatively, if you host your own repository you can deploy the file there:
      mvn deploy:deploy-file -DgroupId=junit -DartifactId=junit -Dversion=3.8.1 -Dpackaging=jar -Dfile=/path/to/file -Du
rl=[url] -DrepositoryId=[id]

  Path to dependency:
        1) org.home.mvnsample:mvnsample:jar:1.0-ALPHA2
        2) junit:junit:jar:3.8.1

----------
1 required artifact is missing.

for artifact:
  org.home.mvnsample:mvnsample:jar:1.0-ALPHA2

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)
=================================================


This implies that the junit.jar is being sought in Maven Central, whereas in fact it is supposed to be in a local directory.

It would be a lot easier to debug errors in the systemPath if the error message showed where Maven was actually looking for it.


    
> scope="system" errors are difficult to diagnose because the error message is wrong
> ----------------------------------------------------------------------------------
>
>                 Key: MNG-4723
>                 URL: https://jira.codehaus.org/browse/MNG-4723
>             Project: Maven 2 & 3
>          Issue Type: Bug
>          Components: POM
>    Affects Versions: 2.2.1
>         Environment: Apache Maven 2.2.1 (r801777; 2009-08-06 20:16:01+0100)
> Java version: 1.6.0_20
> Java home: C:\jdk1.6.0_20\jre
> Default locale: en_GB, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>            Reporter: SebbASF
>             Fix For: Issues to be reviewed for 3.x
>
>
> The following pom contents:
> {code:xml}
>   <dependencies>
>     <dependency>
>       <groupId>junit</groupId>
>       <artifactId>junit</artifactId>
>       <version>3.8.1</version>
>       <scope>system</scope>
>       <systemPath>c:/x/y/x</systemPath>
>     </dependency>
>   </dependencies>
> {code}
> generates the output:
> {noformat}
> [INFO] Failed to resolve artifact.
> Missing:
> ----------
> 1) junit:junit:jar:3.8.1
>   Try downloading the file manually from the project website.
>   Then, install it using the command:
>       mvn install:install-file -DgroupId=junit -DartifactId=junit -Dversion=3.8.1 -Dpackaging=jar -Dfile=/path/to/file
>   Alternatively, if you host your own repository you can deploy the file there:
>       mvn deploy:deploy-file -DgroupId=junit -DartifactId=junit -Dversion=3.8.1 -Dpackaging=jar -Dfile=/path/to/file -Du
> rl=[url] -DrepositoryId=[id]
>   Path to dependency:
>         1) org.home.mvnsample:mvnsample:jar:1.0-ALPHA2
>         2) junit:junit:jar:3.8.1
> ----------
> 1 required artifact is missing.
> for artifact:
>   org.home.mvnsample:mvnsample:jar:1.0-ALPHA2
> from the specified remote repositories:
>   central (http://repo1.maven.org/maven2)
> {noformat}
> This implies that the {{junit.jar}} is being sought in Maven Central, whereas in fact it is supposed to be in a local directory.
> It would be a lot easier to debug errors in the systemPath if the error message showed where Maven was actually looking for it.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira