In case you get this twice, please excuse
me, but I don't know why there is this
delay in delivery - trying to put a rush
order on it so that Erik does't go neck
deep in coding ;-)

> From: "Erik Hatcher" <[EMAIL PROTECTED]>
>
>
> > ----- Original Message -----
> > From: "Stefan Bodewig" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Wednesday, February 20, 2002 7:10 AM
> > Subject: Re: <property file=... problem
> >
> >
> > > On 20 Feb 2002, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> > > > On Wed, 20 Feb 2002, Erik Hatcher
> > > > <[EMAIL PROTECTED]> wrote:
> > > >
> > > >> I would only enable the prefix option on loading a properties file
> > > >> (or resource).  Seem reasonable?
> > > >
> > > > yes.
> > >
> > > but with a BuildException if somebody tries to use prefix with name,
> > > location or environment.
> >
> >
> >
> > But of course!  :)
> >
> > Well, location and name aren't mutually exclusive.  But I get the idea
> (and
> > that was my plan anyway, restrict it to only be valid for
file/resource).
> >
> >
>
> Sorry for jumping in late on this.  Erik,
> I hope you haven't coded this out already -
> would you consider this suggestion?
>
> <LoadProperty file="blah">
>     <filterreaderset>
>         <filter
classname="org.apache.tools.ant.filters.TransformProperty">
>             <param name="keyprefix" value="somePrefix"/>
>             <param name="keysuffix" value="someSuffix"/>
>         </filter>
>     </filterreaderset>
> </LoadProperty>
>
> Two reasons for this:
> 1.  <property> is loaded enough already.
> 2.  using filterreaders will make it more customizable
> - tomorrow, somebody would consider suffixing the keys
> as what they want instead of prefixing them, etc.  This
> way we let the user choose what she wants to do...
>
> Thanks,
> Magesh
>
> *************************************************
> *  Committee: Individuals who can do nothing    *
> *  individually and sit to decide that nothing  *
> *  can be done together.                        *
> *************************************************
>
>


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to