[configuration] Java 8 types

classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

[configuration] Java 8 types

garydgregory
Hi All:

I say it is time to update Commons Configuration to Java 8 and support the
types in java.time.

Thoughts?

Gary
Reply | Threaded
Open this post in threaded view
|

Re: [configuration] Java 8 types

jochen-2
+1


On Wed, Mar 28, 2018 at 9:06 PM, Gary Gregory <[hidden email]> wrote:
> Hi All:
>
> I say it is time to update Commons Configuration to Java 8 and support the
> types in java.time.
>
> Thoughts?
>
> Gary

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [configuration] Java 8 types

garydgregory
Done.

Gary

On Wed, Mar 28, 2018 at 2:21 PM, Jochen Wiedmann <[hidden email]>
wrote:

> +1
>
>
> On Wed, Mar 28, 2018 at 9:06 PM, Gary Gregory <[hidden email]>
> wrote:
> > Hi All:
> >
> > I say it is time to update Commons Configuration to Java 8 and support
> the
> > types in java.time.
> >
> > Thoughts?
> >
> > Gary
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>
Reply | Threaded
Open this post in threaded view
|

Re: [configuration] Java 8 types

Oliver Heger-3


Am 29.03.2018 um 15:54 schrieb Gary Gregory:

> Done.
>
> Gary
>
> On Wed, Mar 28, 2018 at 2:21 PM, Jochen Wiedmann <[hidden email]>
> wrote:
>
>> +1
>>
>>
>> On Wed, Mar 28, 2018 at 9:06 PM, Gary Gregory <[hidden email]>
>> wrote:
>>> Hi All:
>>>
>>> I say it is time to update Commons Configuration to Java 8 and support
>> the
>>> types in java.time.
>>>
>>> Thoughts?

Supporting these new types is certainly desirable.

As the conversion mechanism is designed to be extensible, maybe this can
be achieved without increasing the minimum Java requirement for the core
library: We could add a module (making [configuration] to a multi-module
project) that just contains a converter for new Java 8 types. This
module would then obviously require Java 8.

The API for installing this converter probably would need some tweaking
to make the extension of the conversion mechanism more convenient. But
this should be doable. The user guide [1] describes this mechanism and
how to add custom converters.

While I am not strictly against switching to Java 8, I fear that there
are still users who have to stick to version 1.7, for instance on Android.

Oliver

[1]
http://commons.apache.org/proper/commons-configuration/userguide/howto_basicfeatures.html#Data_type_conversions

>>>
>>> Gary
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [hidden email]
>> For additional commands, e-mail: [hidden email]
>>
>>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [configuration] Java 8 types

garydgregory
Hi,

We are talking dead Java 7 here, Android or not, Java 10 just came out. It
looks like Android supports some Java 8 at least:
https://developer.android.com/studio/write/java8-support.html

If someone has a burning desire to maintain a Java 7 branch, go for it. I
do think that in 2018, we need to move off Java 7 for main Java
development...

Gary

On Thu, Mar 29, 2018 at 12:05 PM, Oliver Heger <[hidden email]
> wrote:

>
>
> Am 29.03.2018 um 15:54 schrieb Gary Gregory:
> > Done.
> >
> > Gary
> >
> > On Wed, Mar 28, 2018 at 2:21 PM, Jochen Wiedmann <
> [hidden email]>
> > wrote:
> >
> >> +1
> >>
> >>
> >> On Wed, Mar 28, 2018 at 9:06 PM, Gary Gregory <[hidden email]>
> >> wrote:
> >>> Hi All:
> >>>
> >>> I say it is time to update Commons Configuration to Java 8 and support
> >> the
> >>> types in java.time.
> >>>
> >>> Thoughts?
>
> Supporting these new types is certainly desirable.
>
> As the conversion mechanism is designed to be extensible, maybe this can
> be achieved without increasing the minimum Java requirement for the core
> library: We could add a module (making [configuration] to a multi-module
> project) that just contains a converter for new Java 8 types. This
> module would then obviously require Java 8.
>
> The API for installing this converter probably would need some tweaking
> to make the extension of the conversion mechanism more convenient. But
> this should be doable. The user guide [1] describes this mechanism and
> how to add custom converters.
>
> While I am not strictly against switching to Java 8, I fear that there
> are still users who have to stick to version 1.7, for instance on Android.
>
> Oliver
>
> [1]
> http://commons.apache.org/proper/commons-configuration/
> userguide/howto_basicfeatures.html#Data_type_conversions
>
> >>>
> >>> Gary
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: [hidden email]
> >> For additional commands, e-mail: [hidden email]
> >>
> >>
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>