Return-Path: 
 <user-return-52115-apmail-ant-user-archive=ant.apache.org@ant.apache.org>
Delivered-To: apmail-ant-user-archive@www.apache.org
Received: (qmail 99930 invoked from network); 1 Sep 2005 13:57:05 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199)
  by minotaur.apache.org with SMTP; 1 Sep 2005 13:57:05 -0000
Received: (qmail 70891 invoked by uid 500); 1 Sep 2005 13:56:58 -0000
Delivered-To: apmail-ant-user-archive@ant.apache.org
Received: (qmail 70851 invoked by uid 500); 1 Sep 2005 13:56:58 -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 70838 invoked by uid 99); 1 Sep 2005 13:56:58 -0000
Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2005 06:56:58 -0700
X-ASF-Spam-Status: No, hits=0.5 required=10.0
	tests=HTML_20_30,HTML_MESSAGE,RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (asf.osuosl.org: domain of andrewgoktepe@gmail.com
 designates 64.233.184.196 as permitted sender)
Received: from [64.233.184.196] (HELO wproxy.gmail.com) (64.233.184.196)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 01 Sep 2005 06:57:11 -0700
Received: by wproxy.gmail.com with SMTP id i2so381502wra
        for <user@ant.apache.org>; Thu, 01 Sep 2005 06:56:54 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=YJCbVYPwCodXRUxNR+rxtrcfJx3E2/DJ5t0IZgwyeRwvp622i0gHZyeZU5kwhoKYIS2nRl4MN++ySJDQJrACpVVwZSiaMSrcOHbjS6suIXa8g1g3RkoQDd9fM+EFIuZVzbh4l3i7Z9FFwiFqA4Tpl/ZjiMWva+YX2Zpm2zb/qV8=
Received: by 10.54.21.70 with SMTP id 70mr1708109wru;
        Thu, 01 Sep 2005 06:56:54 -0700 (PDT)
Received: by 10.54.118.9 with HTTP; Thu, 1 Sep 2005 06:56:54 -0700 (PDT)
Message-ID: <98c2b60d05090106564d97cc1a@mail.gmail.com>
Date: Thu, 1 Sep 2005 08:56:54 -0500
From: Andrew Goktepe <andrewgoktepe@gmail.com>
To: Ant Users List <user@ant.apache.org>
Subject: Re: Jar task updated a jar without known reason
In-Reply-To: <4A686AEE0A43FA47AF3D93220238209101306410@mail.clf.com>
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_11871_28026694.1125583014438"
References: <4A686AEE0A43FA47AF3D93220238209101306410@mail.clf.com>
X-Virus-Checked: Checked by ClamAV on apache.org
X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N

------=_Part_11871_28026694.1125583014438
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

The jar task will do as its told without checking to see if there is alread=
y=20
an up-to-date file, just as with the jar command-line utility.
 Yes, without the update attribute set, the jar file will be re-created eac=
h=20
time.
 -Andrew

 On 9/1/05, Barak Yaish <byaish@cloverleafcomm.com> wrote:=20
>=20
> First of all, Thanks!
>=20
> But can you tell WHY Ant touched my jar?
>=20
> Regarding your second comment, if I'll omit the update flag, the jar will=
=20
> be recreated every time the task is executed?
>=20
> Thanks,
>=20
> Barak.
>=20
> -----Original Message-----
> From: Andrew Goktepe [mailto:andrewgoktepe@gmail.com]
> Sent: ?? 01 ?????? 2005 16:46?
> To: Ant Users List
> Subject: Re: Jar task updated a jar without known reason
>=20
> You can use the <uptodate> task to compare timestamps between a set of=20
> files
> and a target file. In your case, the set of files are your class files,=
=20
> and
> the target file is your jar file.
> <target name=3D"compile_cli">
> (your current contents of compile_cli here)
> <uptodate property=3D"skip.jar" targetfile=3D"${jars}/cli.jar">
> <srcfiles dir=3D"${cli_output}" includes=3D"project/manager/tools/CLI/**"=
/>
> </uptodate>
> </target>
> <target name=3D"jar_cli" unless=3D"skip.jar" depends=3D"compile_cli">
> <jar destfile=3D"${jars}/cli.jar"
> basedir=3D"${cli_output}"
> includes=3D"project/manager/tools/CLI/**"
> update=3D"true"
> />
> </target>
> Also, are you sure you want update=3D"true" on the jar task? This will ad=
d
> files to the previously-built jar rather than creating a new one. If you
> remove files from your source, the jar will still keep the outdated files=
.
> -Andrew
>=20
> On 9/1/05, Barak Yaish <byaish@cloverleafcomm.com> wrote:
> >
> > Hello,
> >
> > In my build file, javac and jar task are called in order to create a ja=
r
> > for my project.
> > First time these tasks were called, the source files got compiled and a
> > jar was created just fine. Without changing anything in the source=20
> files, I
> > ran again the tasks.
> > Nothing happened in javac task, as expected, but the jar task changed=
=20
> the
> > time stamp of the jar. The question is: why? A check I did rais that th=
e=20
> Ant
> > change the time stamp of the manifest file, even without changing its
> > content. For some reasons, it is very important to me that the time=20
> stamp of
> > the jar file wouldn't be changed unless a source file changed.
> > This is how the jar task is written in my build file:
> >
> > <target name=3D"jar_cli" depends=3D"compile_cli">
> > <jar destfile=3D"${jars}/cli.jar"
> > basedir=3D"${cli_output}"
> > includes=3D"project/manager/tools/CLI/**"
> > update=3D"true"
> > />
> > </target>
> >
> > Can someone explain me please how can I avoid such situation?
> >
> > Thanks,
> >
> > Barak.
> >
> >
>=20
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: user-unsubscribe@ant.apache.org
> For additional commands, e-mail: user-help@ant.apache.org
>=20
>

------=_Part_11871_28026694.1125583014438--