Return-Path: 
 <ant-user-return-28050-qmlist-jakarta-archive-ant-user=jakarta.apache.org@jakarta.apache.org>
Delivered-To: apmail-jakarta-ant-user-archive@apache.org
Received: (qmail 39405 invoked from network); 6 Jan 2003 23:22:05 -0000
Received: from exchange.sun.com (192.18.33.10)
  by daedalus.apache.org with SMTP; 6 Jan 2003 23:22:05 -0000
Received: (qmail 12371 invoked by uid 97); 6 Jan 2003 23:23:19 -0000
Delivered-To: qmlist-jakarta-archive-ant-user@jakarta.apache.org
Received: (qmail 12361 invoked by uid 97); 6 Jan 2003 23:23:18 -0000
Mailing-List: contact ant-user-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:ant-user-unsubscribe@jakarta.apache.org>
List-Subscribe: <mailto:ant-user-subscribe@jakarta.apache.org>
List-Help: <mailto:ant-user-help@jakarta.apache.org>
List-Post: <mailto:ant-user@jakarta.apache.org>
List-Id: "Ant Users List" <ant-user.jakarta.apache.org>
Reply-To: "Ant Users List" <ant-user@jakarta.apache.org>
Delivered-To: mailing list ant-user@jakarta.apache.org
Received: (qmail 21496 invoked by uid 98); 6 Jan 2003 17:14:29 -0000
X-Antivirus: nagoya (v4218 created Aug 14 2002)
Message-ID: <3E19B922.FDEE185B@Motorola.com>
Date: Mon, 06 Jan 2003 11:13:06 -0600
From: Sean Landis<Sean.Landis@Motorola.com>
X-Mailer: Mozilla 4.78 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: Ant Users List<ant-user@jakarta.apache.org>
Subject: Re: Different behavior 1.4.1 - 1.5.1 (adding files to existing jar
 files)
References: <3E15B0B2.CCCB234A@Motorola.com>
 <00e501c2b3fc$03f62a30$030200c0@DJ0X820J>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N
X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N

Thanks.
Sean

Antoine Levy-Lambert wrote:

> Dear Sean,
> there is awareness about this issue,
> see http://nagoya.apache.org/bugzilla/show_bug.cgi?id=10755
> in this web page Peter Hale suggested a workaround of touching the jar file,
> setting its date in the past.
> You should try this.
> I have tried to suggest fixes of the code actually this morning, but you
> should probably try to use the workaround first, and wait until the bug is
> officially fixed by one of the ant commiters.
>
> Antoine
>
> >>I was able to workaround the problem by adding a <touch> task between the
> <jar>
> >>and <zip> tasks using a date that I know is in the past.
>
>     <target name="jar" depends="compile" description="Create client jar
> file">
>         <jar destfile="${jar.file.name}.jar" includes="**"
> basedir="${dest.dir}" manifest="ant/dashclient-nosign.mf" update="true" />
>         <touch file="${jar.file.name}.jar" datetime="06/28/2000 2:02 pm"/>
>         <zip destfile="${jar.file.name}.jar" update="true" >
>             <zipfileset src="shared/Cnnxn/CnnxnUtils.jar" excludes="META-
> INF/MANIFEST.MF" />
>         </zip>
>     </target>
>
> >> Peter Hale phale@cnnxn.com
>
> ----- Original Message -----
> From: "Sean Landis" <Sean.Landis@Motorola.com>
> To: "Ant User List (E-mail)" <ant-user@jakarta.apache.org>;
> <Sean.Landis@Motorola.com>
> Sent: Friday, January 03, 2003 4:48 PM
> Subject: Different behavior 1.4.1 - 1.5.1
>
> > We noticed an important difference in behavior between 1.4.1  and 1.5.1
> > regarding the jar built-in. The difference is demonstrated in the
> > following
> > build file fragment:
> >
> >   <jar jarfile="${service-dl.jars}/controller-surrogate.jar"
> >          basedir="${build}"  includesfile="tmp"/>
> >   <jar jarfile="${service-dl.jars}/controller-surrogate.jar"
> >         manifest="${manifests}/controller-surrogate.mf"
> >          update="true"
> >          basedir="${service-dl.jars}"
> >          includes="service-surrogate.jar"/>
> >
> > In 1.4.1, the first jar command would create the jar and the second
> > would
> > update the jar file. In 1.5.1, the first would create, but the second
> > would
> > be skipped. With -debug, a message is printed that states the second
> > command was skipped because the jar file was up to date.
> >
> > This seems to be a bug in 1.5.1 since the 'update="true"' ought to
> > force update regardless of the state of the jar file.
> >
> > Is this a bug to be fixed?
> >
> > If not, is there a correct way to do what we want?
> >
> > If so, is there a work-around technique to get what we want?
> >
> > Thanks,
> > Sean
> >
> >
> > --
> > To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
> > For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>
> >
>
> --
> To unsubscribe, e-mail:   <mailto:ant-user-unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:ant-user-help@jakarta.apache.org>


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