Hi all,

I wrote a wrapper for the OverwriteProperties.java class from Jetspeed.  It
is posted as an attachment at this URL:

http://issues.apache.org/bugzilla/show_bug.cgi?id=16551

OverwritePropertiesTask takes a file that has some properties definied in
it.  It then will update properties in another property file, remove extra
ones according to matching rules, and insert new ones.

I wrote it to help my Jetspeed development, but then realized I want the
same cool ability for my Turbine apps.

Is this something that we could add to Turbine?  Should be a matter of
renaming packages and grabbing the OverwriteProperties.java class from
Jetspeed.

The code attached to the issue has full Junit test cases as well.

Eric Pugh

-----Original Message-----
From: Quinton McCombs [mailto:[EMAIL PROTECTED]]
Sent: Friday, January 31, 2003 11:49 AM
To: Turbine Developers List
Subject: RE: FW: [vote] Moving to servlet API 2.3


The session service requires 2.3.  We could simply leave it at 2.2 and
state that use of the session service will require a 2.3 compliant
container.

> -----Original Message-----
> From: John McNally [mailto:[EMAIL PROTECTED]] 
> Sent: Friday, January 31, 2003 10:37 AM
> To: Turbine Developers List
> Subject: Re: FW: [vote] Moving to servlet API 2.3
> 
> 
> What feature are you wanting to add that requires 2.3?
> john mcnally
> 
> On Thu, 2003-01-30 at 11:56, Quinton McCombs wrote:
> > 
> > 
> > > -----Original Message-----
> > > From: Quinton McCombs
> > > Sent: Friday, January 17, 2003 9:19 AM
> > > To: Turbine Developers List
> > > Subject: [vote] Moving to servlet API 2.3
> > > 
> > > 
> > > I have conducted a poll on the turbine-user list asking if
> > > moving to the 2.3 API will pose a problem for moving to T2.3.
> > >  
> > > Only one person has a problem with it.
> > > http://nagoya.apache.org/eyebrowse/ReadMsg?listId=101
> > > 
> <http://nagoya.apache.org/eyebrowse/ReadMsg?listId=101&msgNo=1
3634>
> > &msgNo=13634
> >  
> > So, what say the committers?
> > 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]



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


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

Reply via email to