Re: Would Commons Lang on Java 8 be a problem for the Apache Maven project?

2016-10-03 Thread Benedikt Ritter 
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 could change that, but that is
> *currently* what we have currently stated. I suspect that a bump to Java 8
> by commons-lang would have a corresponding major version bump... would that
> also include a package name relocation (ala commons-lang3) to indicate
> breaking API changes?
>

Not necessarily. If we just add new API for example for dealing with
java.util.function.Function, we would consider this a compatible change and
not bump the major version number.

If we decide to do a major version number bump, we would change maven and
package coordinates.

But TBH, I don't see Commons Lang 4.0 any time soon, simply because we
don't have enough man power.


>
> Would the commons PMC object to us looking for maintenance releases on the
> old line (perhaps even with us committing the fixes to the maintenance line
> if necessary... IIUI commons is "open commit" so any Maven committer
> *should* have a commit bit on commons... we'd just need the commons PMC to
> assist getting releases out)?
>

Traditionally we just maintain two release lines. For Commons Lang we still
provide the 2.x release line but the main development line is 3.x. TBH
there has been no development/fixes in the 2.x line for ages. But
theoretically we could push out a new 2.x release if anything critical
shows up.
So we would usually not maintain, say 3.4.x and 3.4+, because we don't have
enough resources.

Yes Commons is open for all Apache Committers and we invite every Apache
Committer to come and collaborate at Apache Commons. So if any Maven
Committer wants to push out a Maintenance release of Component XY, we're
happy to help with that.
When it comes to releases, at the moment only the Commons PMC LDAP group
can deploy to our group ID. But if anybody shows serious interest in
pushing a release we simply grant the necessary karma.


>
> I suspect the answers to the above are all favourable... in which case I
> say "don't let us hold you back"
>

Okay, I still think it will take some time until we seriously consider
moving to Java 8 (we're currently Java 6), but it's good to get some
feedback early.

Thank you!
Benedikt


>
> On 25 September 2016 at 15:20, Robert Scholte 
> wrote:
>
> > 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 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 nice if the target is still 1.7
> >>>
> >>> if ( isJava8() )
> >>> { // do java8 stuff }
> >>> else
> >>> { do classic stuff } )
> >>>
> >>> if the java8 stuff uses reflection, you can build it with JDK7,
> otherwise
> >>> you must use JDK8
> >>>
> >>>
> >> We're thinking about adding APIs for dealing with e.g. Functions. So
> >> maven.compiler.source and maven.compiler.target would be 1.8. This would
> >> require downstream user to also compile with Java 8. If I understand
> >> correctly, this would be a problem for Maven, right?
> >>
> >
> > As long as we say that users can run Maven with Java7, then yes it would
> > block us from upgrading. Is that a problem? Maybe, as long as we don't
> hit
> > a bug commons-lang.
> >
> > Robert
> >
> >
> >
> >> Regards,
> >> Benedikt
> >>
> >>
> >>
> >>> Robert
> >>>
> >>> [1]
> >>>
> >>> https://maven.apache.org/shared/maven-shared-utils/xref/org/
> >>> apache/maven/shared/utils/io/FileUtils.html#L831
> >>>
> >>> On Sun, 25 Sep 2016 09:48:56 +0200, Benedikt Ritter <
> brit...@apache.org>
> >>> wrote:
> >>>
> >>> > 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
> >>> > Commons Lang would require Java 8.
> >>> >
> >>> > Thank you,
> >>> > Benedikt
> >>> >
> >>> > [1] http://markmail.org/message/ecxc4brpxufamuzu
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >>> For additional commands, e-mail: dev-h...@maven.apache.org
> >>>
> >>>
>

Re: Would Commons Lang on Java 8 be a problem for the Apache Maven project?

2016-09-26 Thread Stephen Connolly 
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:
>
> > 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 commons-lang would have a corresponding major version bump... would
> that
> > also include a package name relocation (ala commons-lang3) to indicate
> > breaking API changes?
> >
> > Would the commons PMC object to us looking for maintenance releases on
> the
> > old line (perhaps even with us committing the fixes to the maintenance
> line
> > if necessary... IIUI commons is "open commit" so any Maven committer
> > *should* have a commit bit on commons... we'd just need the commons PMC
> to
> > assist getting releases out)?
> >
> > I suspect the answers to the above are all favourable... in which case I
> > say "don't let us hold you back"
> >
> > On 25 September 2016 at 15:20, Robert Scholte  >
> > wrote:
> >
> > > On Sun, 25 Sep 2016 16:11:22 +0200, Benedikt Ritter <
> brit...@apache.org >
> > > 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 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 nice if the target is still 1.7
> > >>>
> > >>> if ( isJava8() )
> > >>> { // do java8 stuff }
> > >>> else
> > >>> { do classic stuff } )
> > >>>
> > >>> if the java8 stuff uses reflection, you can build it with JDK7,
> > otherwise
> > >>> you must use JDK8
> > >>>
> > >>>
> > >> We're thinking about adding APIs for dealing with e.g. Functions. So
> > >> maven.compiler.source and maven.compiler.target would be 1.8. This
> would
> > >> require downstream user to also compile with Java 8. If I understand
> > >> correctly, this would be a problem for Maven, right?
> > >>
> > >
> > > As long as we say that users can run Maven with Java7, then yes it
> would
> > > block us from upgrading. Is that a problem? Maybe, as long as we don't
> > hit
> > > a bug commons-lang.
> > >
> > > Robert
> > >
> > >
> > >
> > >> Regards,
> > >> Benedikt
> > >>
> > >>
> > >>
> > >>> Robert
> > >>>
> > >>> [1]
> > >>>
> > >>> https://maven.apache.org/shared/maven-shared-utils/xref/org/
> > >>> apache/maven/shared/utils/io/FileUtils.html#L831
> > >>>
> > >>> On Sun, 25 Sep 2016 09:48:56 +0200, Benedikt Ritter <
> > brit...@apache.org >
> > >>> wrote:
> > >>>
> > >>> > 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
> > >>> > Commons Lang would require Java 8.
> > >>> >
> > >>> > Thank you,
> > >>> > Benedikt
> > >>> >
> > >>> > [1] http://markmail.org/message/ecxc4brpxufamuzu
> > >>>
> > >>> 
> -
> > >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> 
> > >>> For additional commands, e-mail: dev-h...@maven.apache.org
> 
> > >>>
> > >>>
> > > -
> > > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> 
> > > For additional commands, e-mail: dev-h...@maven.apache.org
> 
> > >
> > >
> >
>


-- 
Sent from my phone

Re: Would Commons Lang on Java 8 be a problem for the Apache Maven project?

2016-09-26 Thread Stian Soiland-Reyes 
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 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 commons-lang would have a corresponding major version bump... would that
> also include a package name relocation (ala commons-lang3) to indicate
> breaking API changes?
>
> Would the commons PMC object to us looking for maintenance releases on the
> old line (perhaps even with us committing the fixes to the maintenance line
> if necessary... IIUI commons is "open commit" so any Maven committer
> *should* have a commit bit on commons... we'd just need the commons PMC to
> assist getting releases out)?
>
> I suspect the answers to the above are all favourable... in which case I
> say "don't let us hold you back"
>
> On 25 September 2016 at 15:20, Robert Scholte 
> wrote:
>
> > 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 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 nice if the target is still 1.7
> >>>
> >>> if ( isJava8() )
> >>> { // do java8 stuff }
> >>> else
> >>> { do classic stuff } )
> >>>
> >>> if the java8 stuff uses reflection, you can build it with JDK7,
> otherwise
> >>> you must use JDK8
> >>>
> >>>
> >> We're thinking about adding APIs for dealing with e.g. Functions. So
> >> maven.compiler.source and maven.compiler.target would be 1.8. This would
> >> require downstream user to also compile with Java 8. If I understand
> >> correctly, this would be a problem for Maven, right?
> >>
> >
> > As long as we say that users can run Maven with Java7, then yes it would
> > block us from upgrading. Is that a problem? Maybe, as long as we don't
> hit
> > a bug commons-lang.
> >
> > Robert
> >
> >
> >
> >> Regards,
> >> Benedikt
> >>
> >>
> >>
> >>> Robert
> >>>
> >>> [1]
> >>>
> >>> https://maven.apache.org/shared/maven-shared-utils/xref/org/
> >>> apache/maven/shared/utils/io/FileUtils.html#L831
> >>>
> >>> On Sun, 25 Sep 2016 09:48:56 +0200, Benedikt Ritter <
> brit...@apache.org>
> >>> wrote:
> >>>
> >>> > 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
> >>> > Commons Lang would require Java 8.
> >>> >
> >>> > Thank you,
> >>> > Benedikt
> >>> >
> >>> > [1] http://markmail.org/message/ecxc4brpxufamuzu
> >>>
> >>> -
> >>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> >>> For additional commands, e-mail: dev-h...@maven.apache.org
> >>>
> >>>
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> > For additional commands, e-mail: dev-h...@maven.apache.org
> >
> >
>

Re: Would Commons Lang on Java 8 be a problem for the Apache Maven project?

2016-09-26 Thread Tibor Digana 
We do not have to rush however I can optimistically imaging the some
colleagues like Kristian would enjoy their spare time on reworking Maven
sources to Java 8 :-)

On Mon, Sep 26, 2016 at 12:04 PM, stephenconnolly [via Maven] <
ml-node+s40175n5881611...@n5.nabble.com> wrote:

> 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 commons-lang would have a corresponding major version bump... would
> that
> also include a package name relocation (ala commons-lang3) to indicate
> breaking API changes?
>
> Would the commons PMC object to us looking for maintenance releases on the
> old line (perhaps even with us committing the fixes to the maintenance
> line
> if necessary... IIUI commons is "open commit" so any Maven committer
> *should* have a commit bit on commons... we'd just need the commons PMC to
> assist getting releases out)?
>
> I suspect the answers to the above are all favourable... in which case I
> say "don't let us hold you back"
>
> On 25 September 2016 at 15:20, Robert Scholte <[hidden email]
> > wrote:
>
> > On Sun, 25 Sep 2016 16:11:22 +0200, Benedikt Ritter <[hidden email]
> >
> > wrote:
> >
> > Hello Robert,
> >>
> >> just watched your JavaOne presentation. Very interesting :-)
> >>
> >
> > thanks!
> >
> >
> >> Robert Scholte <[hidden email]
> > 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-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 nice if the target is still 1.7
> >>>
> >>> if ( isJava8() )
> >>> { // do java8 stuff }
> >>> else
> >>> { do classic stuff } )
> >>>
> >>> if the java8 stuff uses reflection, you can build it with JDK7,
> otherwise
> >>> you must use JDK8
> >>>
> >>>
> >> We're thinking about adding APIs for dealing with e.g. Functions. So
> >> maven.compiler.source and maven.compiler.target would be 1.8. This
> would
> >> require downstream user to also compile with Java 8. If I understand
> >> correctly, this would be a problem for Maven, right?
> >>
> >
> > As long as we say that users can run Maven with Java7, then yes it would
> > block us from upgrading. Is that a problem? Maybe, as long as we don't
> hit
> > a bug commons-lang.
> >
> > Robert
> >
> >
> >
> >> Regards,
> >> Benedikt
> >>
> >>
> >>
> >>> Robert
> >>>
> >>> [1]
> >>>
> >>> https://maven.apache.org/shared/maven-shared-utils/xref/org/
> >>> apache/maven/shared/utils/io/FileUtils.html#L831
> >>>
> >>> On Sun, 25 Sep 2016 09:48:56 +0200, Benedikt Ritter <[hidden email]
> >
> >>> wrote:
> >>>
> >>> > 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
> >>> > Commons Lang would require Java 8.
> >>> >
> >>> > Thank you,
> >>> > Benedikt
> >>> >
> >>> > [1] http://markmail.org/message/ecxc4brpxufamuzu
> >>>
> >>> -
> >>> 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]
> 
> >
> >
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://maven.40175.n5.nabble.com/Would-Commons-Lang-on-
> Java-8-be-a-problem-for-the-Apache-Maven-project-tp5881450p5881611.html
> To start a new topic under Maven Developers, email
> ml-node+s40175n142166...@n5.nabble.com
> To unsubscribe from Maven Developers, click here
> 
> .
> NAML
>

Re: Would Commons Lang on Java 8 be a problem for the Apache Maven project?

2016-09-26 Thread Stephen Connolly 
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 commons-lang would have a corresponding major version bump... would that
also include a package name relocation (ala commons-lang3) to indicate
breaking API changes?

Would the commons PMC object to us looking for maintenance releases on the
old line (perhaps even with us committing the fixes to the maintenance line
if necessary... IIUI commons is "open commit" so any Maven committer
*should* have a commit bit on commons... we'd just need the commons PMC to
assist getting releases out)?

I suspect the answers to the above are all favourable... in which case I
say "don't let us hold you back"

On 25 September 2016 at 15:20, Robert Scholte  wrote:

> 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 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 nice if the target is still 1.7
>>>
>>> if ( isJava8() )
>>> { // do java8 stuff }
>>> else
>>> { do classic stuff } )
>>>
>>> if the java8 stuff uses reflection, you can build it with JDK7, otherwise
>>> you must use JDK8
>>>
>>>
>> We're thinking about adding APIs for dealing with e.g. Functions. So
>> maven.compiler.source and maven.compiler.target would be 1.8. This would
>> require downstream user to also compile with Java 8. If I understand
>> correctly, this would be a problem for Maven, right?
>>
>
> As long as we say that users can run Maven with Java7, then yes it would
> block us from upgrading. Is that a problem? Maybe, as long as we don't hit
> a bug commons-lang.
>
> Robert
>
>
>
>> Regards,
>> Benedikt
>>
>>
>>
>>> Robert
>>>
>>> [1]
>>>
>>> https://maven.apache.org/shared/maven-shared-utils/xref/org/
>>> apache/maven/shared/utils/io/FileUtils.html#L831
>>>
>>> On Sun, 25 Sep 2016 09:48:56 +0200, Benedikt Ritter 
>>> wrote:
>>>
>>> > 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
>>> > Commons Lang would require Java 8.
>>> >
>>> > Thank you,
>>> > Benedikt
>>> >
>>> > [1] http://markmail.org/message/ecxc4brpxufamuzu
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Would Commons Lang on Java 8 be a problem for the Apache Maven project?

2016-09-25 Thread Fred Cooke 
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 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 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 nice if the target is still 1.7
>>>
>>> if ( isJava8() )
>>> { // do java8 stuff }
>>> else
>>> { do classic stuff } )
>>>
>>> if the java8 stuff uses reflection, you can build it with JDK7, otherwise
>>> you must use JDK8
>>>
>>>
>> We're thinking about adding APIs for dealing with e.g. Functions. So
>> maven.compiler.source and maven.compiler.target would be 1.8. This would
>> require downstream user to also compile with Java 8. If I understand
>> correctly, this would be a problem for Maven, right?
>>
>
> As long as we say that users can run Maven with Java7, then yes it would
> block us from upgrading. Is that a problem? Maybe, as long as we don't hit
> a bug commons-lang.
>
> Robert
>
>
>
>> Regards,
>> Benedikt
>>
>>
>>
>>> Robert
>>>
>>> [1]
>>>
>>> https://maven.apache.org/shared/maven-shared-utils/xref/org/
>>> apache/maven/shared/utils/io/FileUtils.html#L831
>>>
>>> On Sun, 25 Sep 2016 09:48:56 +0200, Benedikt Ritter 
>>> wrote:
>>>
>>> > 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
>>> > Commons Lang would require Java 8.
>>> >
>>> > Thank you,
>>> > Benedikt
>>> >
>>> > [1] http://markmail.org/message/ecxc4brpxufamuzu
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>>> For additional commands, e-mail: dev-h...@maven.apache.org
>>>
>>>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Would Commons Lang on Java 8 be a problem for the Apache Maven project?

2016-09-25 Thread Robert Scholte 
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 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 nice if the target is still 1.7

if ( isJava8() )
{ // do java8 stuff }
else
{ do classic stuff } )

if the java8 stuff uses reflection, you can build it with JDK7,  
otherwise

you must use JDK8



We're thinking about adding APIs for dealing with e.g. Functions. So
maven.compiler.source and maven.compiler.target would be 1.8. This would
require downstream user to also compile with Java 8. If I understand
correctly, this would be a problem for Maven, right?


As long as we say that users can run Maven with Java7, then yes it would  
block us from upgrading. Is that a problem? Maybe, as long as we don't hit  
a bug commons-lang.


Robert



Regards,
Benedikt




Robert

[1]

https://maven.apache.org/shared/maven-shared-utils/xref/org/apache/maven/shared/utils/io/FileUtils.html#L831

On Sun, 25 Sep 2016 09:48:56 +0200, Benedikt Ritter 
wrote:

> 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
> Commons Lang would require Java 8.
>
> Thank you,
> Benedikt
>
> [1] http://markmail.org/message/ecxc4brpxufamuzu

-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Would Commons Lang on Java 8 be a problem for the Apache Maven project?

2016-09-25 Thread Benedikt Ritter 
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-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 nice if the target is still 1.7
>
> if ( isJava8() )
> { // do java8 stuff }
> else
> { do classic stuff } )
>
> if the java8 stuff uses reflection, you can build it with JDK7, otherwise
> you must use JDK8
>

We're thinking about adding APIs for dealing with e.g. Functions. So
maven.compiler.source and maven.compiler.target would be 1.8. This would
require downstream user to also compile with Java 8. If I understand
correctly, this would be a problem for Maven, right?

Regards,
Benedikt


>
> Robert
>
> [1]
>
> https://maven.apache.org/shared/maven-shared-utils/xref/org/apache/maven/shared/utils/io/FileUtils.html#L831
>
> On Sun, 25 Sep 2016 09:48:56 +0200, Benedikt Ritter 
> wrote:
>
> > 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
> > Commons Lang would require Java 8.
> >
> > Thank you,
> > Benedikt
> >
> > [1] http://markmail.org/message/ecxc4brpxufamuzu
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
> For additional commands, e-mail: dev-h...@maven.apache.org
>
>

Re: Would Commons Lang on Java 8 be a problem for the Apache Maven project?

2016-09-25 Thread Benedikt Ritter 
Hello Tibor,

Tibor Digana  schrieb am So., 25. Sep. 2016 um
10:27 Uhr:

> What a new API is needed from commons-lang:3.7 in Maven?
> Do we need to have something from the latest commons-lang and latest JDK ?
> Benedikt, can you provide us with API changes on the web so that we would
> better understand.
> I understand that commons might be needed in the integration test classes
> in Surefire project but Maven is compiles with Java 1.7. If we compiled
> Maven with Java 1.8 then we forced the users to change their CI jobs and
> infrastructure.
>

We don't have any concrete plans yet. We're just thinking about it. So I
can't give you any examples yet.

Regards,
Benedikt


>
> Cheers
> Tibor
>
>
>
> On Sun, Sep 25, 2016 at 9:49 AM, Benedikt Ritter [via Maven] <
> ml-node+s40175n5881450...@n5.nabble.com> wrote:
>
> > 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
> > Commons Lang would require Java 8.
> >
> > Thank you,
> > Benedikt
> >
> > [1] http://markmail.org/message/ecxc4brpxufamuzu
> >
> >
> > --
> > If you reply to this email, your message will be added to the discussion
> > below:
> > http://maven.40175.n5.nabble.com/Would-Commons-Lang-on-
> > Java-8-be-a-problem-for-the-Apache-Maven-project-tp5881450.html
> > To start a new topic under Maven Developers, email
> > ml-node+s40175n142166...@n5.nabble.com
> > To unsubscribe from Maven Developers, click here
> > <
> http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code=142166=dGlib3JkaWdhbmFAYXBhY2hlLm9yZ3wxNDIxNjZ8LTI4OTQ5MjEwMg==
> >
> > .
> > NAML
> > <
> http://maven.40175.n5.nabble.com/template/NamlServlet.jtp?macro=macro_viewer=instant_html%21nabble%3Aemail.naml=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml
> >
> >
>
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Would-Commons-Lang-on-Java-8-be-a-problem-for-the-Apache-Maven-project-tp5881450p5881451.html
> Sent from the Maven Developers mailing list archive at Nabble.com.

Re: Would Commons Lang on Java 8 be a problem for the Apache Maven project?

2016-09-25 Thread Robert Scholte 
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 nice if the target is still 1.7

if ( isJava8() )
{ // do java8 stuff }
else
{ do classic stuff } )

if the java8 stuff uses reflection, you can build it with JDK7, otherwise  
you must use JDK8


Robert

[1]  
https://maven.apache.org/shared/maven-shared-utils/xref/org/apache/maven/shared/utils/io/FileUtils.html#L831


On Sun, 25 Sep 2016 09:48:56 +0200, Benedikt Ritter   
wrote:



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

Commons Lang would require Java 8.

Thank you,
Benedikt

[1] http://markmail.org/message/ecxc4brpxufamuzu


-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org

Re: Would Commons Lang on Java 8 be a problem for the Apache Maven project?

2016-09-25 Thread Tibor Digana 
What a new API is needed from commons-lang:3.7 in Maven?
Do we need to have something from the latest commons-lang and latest JDK ?
Benedikt, can you provide us with API changes on the web so that we would
better understand.
I understand that commons might be needed in the integration test classes
in Surefire project but Maven is compiles with Java 1.7. If we compiled
Maven with Java 1.8 then we forced the users to change their CI jobs and
infrastructure.

Cheers
Tibor



On Sun, Sep 25, 2016 at 9:49 AM, Benedikt Ritter [via Maven] <
ml-node+s40175n5881450...@n5.nabble.com> wrote:

> 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
> Commons Lang would require Java 8.
>
> Thank you,
> Benedikt
>
> [1] http://markmail.org/message/ecxc4brpxufamuzu
>
>
> --
> If you reply to this email, your message will be added to the discussion
> below:
> http://maven.40175.n5.nabble.com/Would-Commons-Lang-on-
> Java-8-be-a-problem-for-the-Apache-Maven-project-tp5881450.html
> To start a new topic under Maven Developers, email
> ml-node+s40175n142166...@n5.nabble.com
> To unsubscribe from Maven Developers, click here
> 
> .
> NAML
> 
>




--
View this message in context: 
http://maven.40175.n5.nabble.com/Would-Commons-Lang-on-Java-8-be-a-problem-for-the-Apache-Maven-project-tp5881450p5881451.html
Sent from the Maven Developers mailing list archive at Nabble.com.

Would Commons Lang on Java 8 be a problem for the Apache Maven project?

2016-09-25 Thread Benedikt Ritter 
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
Commons Lang would require Java 8.

Thank you,
Benedikt

[1] http://markmail.org/message/ecxc4brpxufamuzu