Am 10.08.2012 14:12, schrieb Tom Weissinger:
Oliver,
Thanks for the information.
Is the expectation that commons-configuration will undergo the same sort of
change, where all the package names change to have "configuration2" like
what was done with "lang3"?
Yes, both the package names and the
Oliver,
Thanks for the information.
Is the expectation that commons-configuration will undergo the same sort of
change, where all the package names change to have "configuration2" like
what was done with "lang3"?
Tom
On Wed, Aug 8, 2012 at 3:38 PM, Oliver Heger
wrote:
> Hi Tom,
>
> Am 07.08.20
Hi Tom,
Am 07.08.2012 22:21, schrieb Tom Weissinger:
Hi,
What is the timeline for commons-configuration to be compatible with
commons-lang 3.1? We want to be able to use some of the new features of
commons-lang (like generic support) but commons-configuration still uses
the old commons-lang.
Hi,
What is the timeline for commons-configuration to be compatible with
commons-lang 3.1? We want to be able to use some of the new features of
commons-lang (like generic support) but commons-configuration still uses
the old commons-lang.
The end result is, if we use the latest versions of both
