Return-Path: 
 <user-return-66089-apmail-ant-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-user-archive@www.apache.org
Received: (qmail 73391 invoked from network); 15 Oct 2008 18:48:11 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 15 Oct 2008 18:48:11 -0000
Received: (qmail 10874 invoked by uid 500); 15 Oct 2008 18:48:08 -0000
Delivered-To: apmail-ant-user-archive@ant.apache.org
Received: (qmail 10552 invoked by uid 500); 15 Oct 2008 18:48:07 -0000
Mailing-List: contact user-help@ant.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:user-unsubscribe@ant.apache.org>
List-Help: <mailto:user-help@ant.apache.org>
List-Post: <mailto:user@ant.apache.org>
List-Id: "Ant Users List" <user.ant.apache.org>
Reply-To: "Ant Users List" <user@ant.apache.org>
Delivered-To: mailing list user@ant.apache.org
Received: (qmail 10541 invoked by uid 99); 15 Oct 2008 18:48:07 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Oct 2008 11:48:07 -0700
X-ASF-Spam-Status: No, hits=-0.0 required=10.0
	tests=SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of ddevienne@gmail.com
 designates 209.85.132.242 as permitted sender)
Received: from [209.85.132.242] (HELO an-out-0708.google.com) (209.85.132.242)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 15 Oct 2008 18:47:01 +0000
Received: by an-out-0708.google.com with SMTP id b2so209417ana.25
        for <user@ant.apache.org>; Wed, 15 Oct 2008 11:47:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to
         :subject:in-reply-to:mime-version:content-type
         :content-transfer-encoding:content-disposition:references;
        bh=la2Tf7dFy2dHijR9SNGONYhjhT0kVphG2GFpVw6MEnU=;
        b=JStBp4BgXb5qJS50/wfXL0YTueS96+0sPmf6uG7GDBtmjUIVURSbKeLlxWSc9Os1U2
         C4jR8ERGalOUG391U4UP1L3+YrkRQr1y5aFIEiIPcv4gbG2bWWI1kwTD+EWQgDBpuh7v
         P0eDLodz77AEO/CVpR5doSQ1TmJhcx+7Ed9Ts=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version
         :content-type:content-transfer-encoding:content-disposition
         :references;
        b=XHU4RE5d4nmiGL/TLKWl3a35gDivpPGcl82GtYHtsEy2ywKJsgHXkCnFFiIObjFc+G
         f5auU99L7oECd+63PGeFTDU0V8FaZLZqXXqgupb3HwdzYGCnH8BnIUXkDRyqJtJ6EBUE
         9s9ag3E6wTAkCixeQm+2h0NhvUD81QtusCkB4=
Received: by 10.100.225.19 with SMTP id x19mr1379367ang.122.1224096448232;
        Wed, 15 Oct 2008 11:47:28 -0700 (PDT)
Received: by 10.100.197.12 with HTTP; Wed, 15 Oct 2008 11:47:28 -0700 (PDT)
Message-ID: <255d8d690810151147tb8c2388x5f395f7e64a5d19c@mail.gmail.com>
Date: Wed, 15 Oct 2008 13:47:28 -0500
From: "Dominique Devienne" <ddevienne@gmail.com>
To: "Ant Users List" <user@ant.apache.org>
Subject: Re: Strange behaviour of <manifestclasspath>
In-Reply-To: <20081014224637.8k6gor19ssoc8skw@webmail.cheapnet.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <20081014224637.8k6gor19ssoc8skw@webmail.cheapnet.it>
X-Virus-Checked: Checked by ClamAV on apache.org

On Tue, Oct 14, 2008 at 3:46 PM, andbin <abin73@cheapnet.it> wrote:
> <project name="Manifest classpath test">
>  <path id="initial.path">
>    <pathelement location="${basedir}/file1.jar"/>
>    <pathelement location="${basedir}/lib/file2.jar"/>
>    <pathelement location="${basedir}"/>
>  </path>

FYI: use either file="${basedir}/..." or location="...", but using
both, while OK, doesn't make much sense to me. The purpose of all
location attributes is to resolve a relative path from ${basedir}, so
to me it's redundant to say location="${basedir}/..". No big deal
though.

> C:\Test\MyProject\file1.jar;C:\Test\MyProject\lib\file2.jar;C:\Test\MyProject
>     [echo] manifest.classpath = file1.jar lib/file2.jar ../MyProject/
>
> The three relative paths generated by <manifestclasspath> are all
> technically correct. But the last is very little useful!!

More than "not-useful", it's wrong. The point of having relative paths
in the manifest is such that you can "transport" all the jars to
another dir and it continues working. Using ../Project/ works only in
a .../Project directory, so it's a bug.

I find it strange to put such a dir in the classpath, but that's
another story ;)

> According to me, the relative path should be generated as . or ./ since it's
> the most logical.

The spec says dirs must end in /, so only ./ is valid. I've never
tried such a combo though.

> BUILD FAILED
> java.lang.NullPointerException
>        at java.lang.String.startsWith(String.java:1422)
>        at java.lang.String.startsWith(String.java:1451)
>        at
> org.apache.tools.ant.taskdefs.ManifestClassPath.execute(ManifestClassPath.java:100)

As Stephan mentions, this is also clearly a bug. Escaped attention has
nobody typically puts jars or classes in the root directory ;-)

Although your paths are "usual", they have uncovered real bugs, albeit
minor ones few people will notice given a more traditional project
layout. --DD

---------------------------------------------------------------------
To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
For additional commands, e-mail: user-help@ant.apache.org