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

[Benedikt Ritter <br...@apache.org>]

Hi,

sorry for the late reply... :-)

Stephen Connolly <st...@gmail.com> 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 <rf...@apache.org>
> wrote:
>
> > On Sun, 25 Sep 2016 16:11:22 +0200, Benedikt Ritter <br...@apache.org>
> > wrote:
> >
> > Hello Robert,
> >>
> >> just watched your JavaOne presentation. Very interesting :-)
> >>
> >
> > thanks!
> >
> >
> >> Robert Scholte <rf...@apache.org> 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 <
> britter@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-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >>>
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>