On 2010-01-20, wrote:
> I have a very specific question about some ant code, I hope this is the
> correct place to post it.
It is.
> I have been using part of the ant project to unGzip and unBzip2 files as
> I wanted a Java way of doing this and I stumbled across the ant classes
> that implemen
ul
for deploying complex java projects to Glassfish etc and apart from this
strange behavior, resulting from files that have their lastModified
fields set incorrectly, that the Untar/GUnzip/BUnzip2 classes work very
well indeed and have been an excellent solution to my problem.
Regards
Hardcode the gunzip src value as /users/build/main/release/AIX.tgz
instead of using properties.
If that works, a property value likely has a tab at the end of its
definition.
That makes the process look for "file " instead of "file" and would
explain why ANT doesn'
ory since the commandline sees it, (but apparently ANT doesn't?)
and
do the remainder of the work I have to do... but then when I try to
repackage it in that location I presume it is going to cause errors
again...
Scot P. Floess-2 wrote:
That's wierd...
What a
d.xml:311: the
>>>> archive
>>>> doesn't
>>>> exist
>>>>
>>>> One workaround I was thinking was just to tar -zxvf the file in the
>>>> directory since the commandline sees it, (but apparently ANT doesn't?)
>>>> an
Floess-2 wrote:
That's wierd...
What about before the gunzip call do this:
I really appreciate the help!
Added the few lines you requested, it appears the GZ_EXISTS variable
isn't
set, so apparently the gzipped file isn't "available."
But
t;> do the remainder of the work I have to do... but then when I try to
>> repackage it in that location I presume it is going to cause errors
>> again...
>>
>>
>> Scot P. Floess-2 wrote:
>> >
>> >
>> > That's wierd...
>> >
&g
t apparently ANT doesn't?) and
> do the remainder of the work I have to do... but then when I try to
> repackage it in that location I presume it is going to cause errors
> again...
>
>
> Scot P. Floess-2 wrote:
> >
> >
> > That's wierd...
> >
>
gt;
>> Scot P. Floess-2 wrote:
>>
>>> OK...so permissions not a problem - next ;)
>>>
>>> Hmm...interesting...
>>>
>>> What about prior to the gunzip call do this
>>>
>>> >> ...
>>>
>>>
>>
esn't?) and
do the remainder of the work I have to do... but then when I try to
repackage it in that location I presume it is going to cause errors again...
Scot P. Floess-2 wrote:
>
>
> That's wierd...
>
> What about
"available."
>
> But I don't know why it's not available, it physically is and the
> permissions seem to be okay..
>
>
> Scot P. Floess-2 wrote:
>
>> OK...so permissions not a problem - next ;)
>>
That's wierd...
What about before the gunzip call do this:
I really appreciate the help!
Added the few lines you requested, it appears the GZ_EXISTS variable isn't
set, so apparently the gzipped file isn't "available."
But I don't k
P. Floess-2 wrote:
>
>
> OK...so permissions not a problem - next ;)
>
> Hmm...interesting...
>
> What about prior to the gunzip call do this
>
> ...
>
>
>
>
>
>
>
>
> On Thu, 22 Jan 2009, Faded-Maximus w
OK...so permissions not a problem - next ;)
Hmm...interesting...
What about prior to the gunzip call do this
On Thu, 22 Jan 2009, Faded-Maximus wrote:
doing ls -la on the gzip file, I have -rw-rw-r--
All the parent directors show the following permissions: drwxrwxr-x
line.
>>
>>
>> Scot P. Floess-2 wrote:
>>>
>>>
>>> OK - my silly question...
>>>
>>> From the command line can you manually gunzip it?
>>>
>>> On Thu, 22 Jan 2009, Faded-Maximus wrote:
>>>
>>>>
I am able to manually unzip it via the command line.
Scot P. Floess-2 wrote:
OK - my silly question...
From the command line can you manually gunzip it?
On Thu, 22 Jan 2009, Faded-Maximus wrote:
Thanks for the reply. Yes, it has read and write permissions, so it's not
a
permissions mist
It's not silly, sometimes things like that are indeed the problem. As for an
answer, yes I am able to manually unzip it via the command line.
Scot P. Floess-2 wrote:
>
>
> OK - my silly question...
>
> From the command line can you manually gunzip it?
>
> On Thu,
OK - my silly question...
From the command line can you manually gunzip it?
On Thu, 22 Jan 2009, Faded-Maximus wrote:
Thanks for the reply. Yes, it has read and write permissions, so it's not a
permissions mistake.
Dale Anson wrote:
Does you build user have permission to read the
>>
>>
>> This is where it's failing, with that error message. The weird thing is
>> the
>> archive does physically exist in that location:
>>
>> [release]$ pwd
>> /users/b
gt;
>
>
> This is where it's failing, with that error message. The weird thing is the
> archive does physically exist in that location:
>
> [release]$ pwd
> /users/build/main/release
> [release]$ ls
> AIX.tgz Linux.tgz
> [release]$
&
z
[release]$
Any ideas?
--
View this message in context:
http://www.nabble.com/Gunzip-error-tp21608282p21608282.html
Sent from the Ant - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: user-unsubscr...@ant.apac
On Fri, 27 Jun 2008, ext-simon steiner <[EMAIL PROTECTED]> wrote:
> I have two zips and many gzips, bunzip2 and untar seem ok also, only
> gunzip is a problem.
gunzip simply doesn't support expanding more than one resource per
task - and the manual says so. Neither does
Hi,
I have two zips and many gzips, bunzip2 and untar seem ok also, only
gunzip is a problem.
Thanks
-Original Message-
From: ext Matt Benson [mailto:[EMAIL PROTECTED]
Sent: 26 June 2008 22:07
To: Ant Users List
Subject: Re: gunzip
--- [EMAIL PROTECTED] wrote:
> Hi,
>
--- [EMAIL PROTECTED] wrote:
> Hi,
>
> This works:
>
>
>
>
>
>
>
> This doesn't, why not?
>
>
>
>
>
>
>
> I get "only single argument resource collections are
> supported as
> archives"
I would imagine it's because you happen to have 1 .zip
and > 1
Hi,
This works:
This doesn't, why not?
I get "only single argument resource collections are supported as
archives"
Thanks
25 matches
Mail list logo
