Bill,
my idea is that now PropertyFileInputHandler is not
very intuitive to use and the unprepared user might
encounter the same errors as I encountered. What we
have now is:
1) If we use prompts with spaces, we should remember
to escape the spaces, the way Stefan showed which is
at least tedious
om: Ivan Ivanov [mailto:[EMAIL PROTECTED]
Sent: Thursday, October 28, 2004 3:32 AM
To: Ant Users List
Subject: Re: Propostion for improving PropertyFileInputHandler
Something more,
nothing prevents us from this situation:
So we have same prompts and there is no way distinguish them as keys
Something more,
nothing prevents us from this situation:
So we have same prompts and there is no way
distinguish them as keys in properties file (which are
should be unique) and property names give us more
"uniqueness" as properties are immutable.
In short, using prompt as a key, open
Hi Stefan,
--- Stefan Bodewig <[EMAIL PROTECTED]> wrote:
>
> No, you create it as
>
> #inputp.properties
> Enter\ Your\ Name=Rambius Parkisanius
>
> At least for JDK > 1.1.
I didn't knew that. However, I think I will use
-propertyfile option, because in my custom task (i am
writng ant task fo
On Wed, 27 Oct 2004, Ivan Ivanov <[EMAIL PROTECTED]> wrote:
> So we create the following properties file
>
> #inputp.properties
> Enter Your Name=Rambius Parkisanius
No, you create it as
#inputp.properties
Enter\ Your\ Name=Rambius Parkisanius
At least for JDK > 1.1.
Cheers
Stefan
Hello Matt,
thank you for your answer.
--- Matt Benson <[EMAIL PROTECTED]> wrote:
> --- RADEMAKERS Tanguy <[EMAIL PROTECTED]>
> wrote:
>
> > Hey Matt,
> >
> > Thanks - i didn't know that. So now I'm a bit
and I have completely forgotten about -propertyfile
option and it makes PropertyFileInputH
--- RADEMAKERS Tanguy <[EMAIL PROTECTED]>
wrote:
> Hey Matt,
>
> Thanks - i didn't know that. So now I'm a bit
> confused: wouldn't this obviate the need for
> PropertyFileInputHandler?
IMHO probably so. Definitely makes changing
PropertyFileInputHandler to use Ant property as key a
non-issue (
st
>Subject: RE: Propostion for improving PropertyFileInputHandler
>
>--- RADEMAKERS Tanguy <[EMAIL PROTECTED]>
>wrote:
>> I agree that the property name makes a better key
>> than the message
>> string. I routinely wrap my tasks in their
>> own targets, us
--- RADEMAKERS Tanguy <[EMAIL PROTECTED]>
wrote:
> I agree that the property name makes a better key
> than the message
> string. I routinely wrap my tasks in their
> own targets, using
> "unless" to allow those devs who want to to put
> things in a properties
> file instead:
Well, now that you m
]
>Subject: Propostion for improving PropertyFileInputHandler
>
>Dear Colleagues,
>
>Consider the following ant xml file:
>
>
>
>Test Script for
>PropertyFileInputHandler
>
>
>addproperty="pfh.name"/>
>pfh.name is ${pfh.n
Dear Colleagues,
Consider the following ant xml file:
Test Script for
PropertyFileInputHandler
pfh.name is ${pfh.name}
If used with DefaultInputHanlder, it works like a
charm. Now let's try to start it with
PropertyFileInputHandler and make it read the input
fr
11 matches
Mail list logo
