Hi,
sorry for the late reply... :-)
Stephen Connolly schrieb am Mo., 26. Sep.
2016 um 12:03 Uhr:
> Well another question is how much longer will we support Java 7 anyway...
> what we have said in the past is the next release line after JDK9 is
> released will only support Java 8+... now we coul
Sounds reasonable. I think you have your answer
On Monday 26 September 2016, Stian Soiland-Reyes wrote:
> If you don't mind helping with back porting, then we can help push
> maintenance releases out :)
>
> On 26 Sep 2016 11:03 a.m., "Stephen Connolly" <
> stephen.alan.conno...@gmail.com > wrote
If you don't mind helping with back porting, then we can help push
maintenance releases out :)
On 26 Sep 2016 11:03 a.m., "Stephen Connolly" <
stephen.alan.conno...@gmail.com> wrote:
> Well another question is how much longer will we support Java 7 anyway...
> what we have said in the past is the
m for
> >>> you
> >>> > if
> >>> > Commons Lang would require Java 8.
> >>> >
> >>> > Thank you,
> >>> > Benedikt
> >>> >
> >>> > [1] http://markmail.org/message/ecxc4brpxufamuzu
&g
Well another question is how much longer will we support Java 7 anyway...
what we have said in the past is the next release line after JDK9 is
released will only support Java 8+... now we could change that, but that is
*currently* what we have currently stated. I suspect that a bump to Java 8
by co
Commons lang could commit to providing patch releases/bug fixes in a
maintenance series of the existing line
for that purpose. Then it'd be totally fine to do whatever they liked in
the new version with major incremented.
On Mon, Sep 26, 2016 at 3:20 AM, Robert Scholte
wrote:
> On Sun, 25 Sep 20
On Sun, 25 Sep 2016 16:11:22 +0200, Benedikt Ritter
wrote:
Hello Robert,
just watched your JavaOne presentation. Very interesting :-)
thanks!
Robert Scholte schrieb am So., 25. Sep. 2016 um
13:48 Uhr:
It depends. If you are changing existing methods to only work with
Java8,
that wou
Hello Robert,
just watched your JavaOne presentation. Very interesting :-)
Robert Scholte schrieb am So., 25. Sep. 2016 um
13:48 Uhr:
> It depends. If you are changing existing methods to only work with Java8,
> that would be a problem (read: we cannot upgrade). If you have both Java8
> and pre
TI4OTQ5MjEwMg==
> >
> > .
> > NAML
> > <
> http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamesp
It depends. If you are changing existing methods to only work with Java8,
that would be a problem (read: we cannot upgrade). If you have both Java8
and pre-Java8 implementations, either by reflection or proper encapsulated
code it'll work for us.
We do it ourselves too[1]
for us it would be
nt_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>
>
--
View th
Hi,
at the Apache Commons Project we're currently discussing where we can host
utility classes for working with the features introduced in Java 8. One
proposal add this to Commons Lang [1]. Since Apache Maven makes use of
Commons Lang, I would like to know whether it would be a problem for you if
12 matches
Mail list logo
