From: Jon Stevens [mailto:[EMAIL PROTECTED]]
>
> on 5/3/01 10:32 PM, "Geir Magnusson Jr." <[EMAIL PROTECTED]> wrote:
>
> > The Configuration class is now in jakarta-commons
> collections package,
> > and this patch has been added there.
> >
> > The commons version is where its going to live now - this
> way others can
> > use it w/o having to drag velocity into things, although you have to
> > drag the commons-collections jar around. Whatever :)
> >
> > I will remove the class from Velocity and update everthing
> to use the
> > new commons package.
> >
> > geir
>
> Has a released version of that .jar file been made so that we
> can have good
> dependency tracking on it?
>
> <http://jakarta.apache.org/turbine/deprecation.html>
You guys can do whatever you want in turbine :)
I wouldn't say that it's a *released* jar - it's a milestone jar. The CVS
was tagged last night with the specific purpose of getting a fixed reference
point for this, as jason wanted to start converting Turbine to use
ExtendedProperties in preparation for the 2.1 release of Turbine.
The classname changed from Configuration to ExtendedProperties (I guess back
to what it was originally :), and we will switch the Velocity internals to
use the ExtendedProperties.
Becuase the classname changed, it's easy to deprecate the Configuration and
leave it lying around in Velocity for a little while, but people should
start moving over to the Commons version as that is where enhancements and
fixes will go.
We should work out how we want to handle this : I think it's convenient if
we do the same trick with Commons-collections that we do with oro and the
apache logger - put the .class we want into our vel dist jar, at least until
the commons-collections has a real release. We can add a target that does
this, or doesn't, depending on how people feel.
geir
