Yay! :). This is good. Thanks for sharing this information.
On 9/24/2009 3:57 PM, Stefan Bodewig wrote:
On 2009-09-24, Francis GALIEGUE wrote:
But ideally, I'd like to use these properties all the time, with
boolean values. Say, for example, if I have nomail set to 1 or true,
then no mail
Hello Francis
Thanks a lot, I have already resolved this by other friend, your approach is
practically the same
Thanks!
-Manuel
Francis Galiegue-4 wrote:
>
> On Mon, Sep 21, 2009 at 02:34, dr_pompeii wrote:
>>
>> Hello supareno
>>
>> Thanks for the reply, but no woek :-(
>>
>
> Try this:
>
2009/9/22 Arne v.Irmer :
> Hi,
> with the command line program "zip" I can create a zip-File with annotated
> folders inside. I try to generate such a zip-File with the
> org.apache.tools.zip classes coming with ant.jar.
>
> Here is my small example program:
>
> package org.example.zip;
>
> impor
On Thu, Sep 24, 2009 at 16:41, danson wrote:
> Both antcontrib[1] and antelope[2] provide if/else constructs. Either
> of these would work for your situation.
>
> Dale
>
> [1] http://ant-contrib.sourceforge.net
> [2] http://antelope.tigris.org
>
>
I know this, I use ant-contrib extensively, but
Both antcontrib[1] and antelope[2] provide if/else constructs. Either
of these would work for your situation.
Dale
[1] http://ant-contrib.sourceforge.net
[2] http://antelope.tigris.org
On Thu, Sep 24, 2009 at 7:37 AM, Matt Benson wrote:
>
>
> --- On Thu, 9/24/09, Stefan Bodewig wrote:
>
>> F
--- On Thu, 9/24/09, Stefan Bodewig wrote:
> From: Stefan Bodewig
> Subject: Re: Feature request: ifbool/unlessbool
> To: user@ant.apache.org
> Date: Thursday, September 24, 2009, 5:27 AM
> On 2009-09-24, Francis GALIEGUE
>
> wrote:
>
> > But ideally, I'd like to use these properties all the
unless will pass if the property is either not set at all (current Ant
behavior) or is set and PropertyHelper expands it to Boolean.FALSE.
This sounds like an excellent solution!
Cheers,
Ernst
-
To unsubscribe, e-mail: user-
On 2009-09-24, Francis GALIEGUE wrote:
> But ideally, I'd like to use these properties all the time, with
> boolean values. Say, for example, if I have nomail set to 1 or true,
> then no mail is sent; if it's 0 or false, then the mail is sent. And
> the target would then read:
>
Ant 1.8.0[1] a
+1 to this feature request.
I am curious to know. why if and unless attributes in 'target' work the
way they do, i.e only check existence of the property and not its value.
Currently ant-contrib's if tag has to be used to accomplish this sort of
control over build execution.
-Prashant
On 9
Hi,
analysing the code solves the problem.
First all folders that will be added to a zip must end with a slash!
Second a ZipEntry must be marked explicit as a folder by setting the 4th bit of
the ExternalAttributes.
This will be done by setting the UnixMode of a ZipEntry.
Here a complete example
Hello list,
I have quite a huge build system based on ant and I govern some of its
behaviour using properties, or the lack of it thereof.
But ideally, I'd like to use these properties all the time, with
boolean values. Say, for example, if I have nomail set to 1 or true,
then no mail is sent; if
11 matches
Mail list logo
