Hi All and FYI,
I created a Slack channel called #commons for the team the-asf.slack.com
Gary
Github user asfgit closed the pull request at:
https://github.com/apache/commons-text/pull/54
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature
Hi All,
I found some time recently to work on the suggestions and ideas that came
up while discussing this.
Specifically, I reworked two major points that were called out -
1. Removed usage of Reflection API.
Replaced reflection with MethodHandles introduced in Java 7 which provide
typed,
It seems so, although it sounds like there is a solution to do it with Java 7
and 8 as well.
http://events.linuxfoundation.org/sites/events/files/slides/Java9%20and%20the%20impact%20on%20Maven%20projects.pdf
It sounds like building on Java 9 renders the animal sniffer Maven plugin
obsolete.
Gary
On Jun 26, 2017 15:02, "Simon Spero" wrote:
> 1.5
> 1.5
> org.apache.commons.functor
>
> JDK 9 cannot generate or parse class files compiled with -target 1.5 [1].
>
> Per
I am OK with keeping the lazy vote since it is pretty frictionless, and
gives people the opportunity to officially raise their hand and show why
this is a problem for them. In practice though, moving everything to Git is
just a matter of time. I can imagine that we would just move components to
Java 9 can still run old bytecode, but they're removing compiler support
for outputting that bytecode apparently (either that or syntax support).
On 27 June 2017 at 18:45, Emmanuel Bourg wrote:
> Le 27/06/2017 à 00:02, Simon Spero a écrit :
>
> > JDK 9 cannot generate or
The only objection I've seen to switching on any project so far was other
projects using svn:external to sync up a commons project, but there are
workarounds for that (e.g., the GitHub svn mirror).
On 28 June 2017 at 03:45, Amey Jadiye wrote:
> unless there is strong
unless there is strong reason to stick with svn we should move on git(as
many other already moved). I agree that in few cases svn is preferred and
that may open huge discussion but atleast for Commons I don't see much
advantages to use svn. people who are using svn from long time usually
comes in
On 2017-06-28, Amey Jadiye wrote:
> I think just announcing with intention is enough as git is always better
> than svn and at some point everyone will wish to move on git.
There certainly are people who disagree with your (I'm not one of them) ;-)
Stefan
On 2017-06-28, Benedikt Ritter wrote:
> do we still need a vote for moving components to git? We have done
> this so often that I think we could change the process to a simply
> mail announcing intents to move a component.
Hmm, what if one of the active developers of the component then says
I think just announcing with intention is enough as git is always better
than svn and at some point everyone will wish to move on git.
so +1 to just announce it.
Regards,
Amey
On Wed, Jun 28, 2017, 12:51 PM Benedikt Ritter wrote:
> Hi,
>
> do we still need a vote for
Hi,
do we still need a vote for moving components to git? We have done this so
often that I think we could change the process to a simply mail announcing
intents to move a component.
Thoughts?
Benedikt
-
To unsubscribe,
Hi Carl,
> Am 28.06.2017 um 05:48 schrieb Carl Hall :
>
> Hi friends,
>
> I'd like to move commons-dbutils to git rather than continuing to deal with
> git-svn. Could someone point me in the right direction for requesting this
> or point me to the right person/group to
Dear Wiki user,
You have subscribed to a wiki page or wiki category on "Commons Wiki" for
change notification.
The "MovingToGit" page has been changed by BenediktRitter:
https://wiki.apache.org/commons/MovingToGit?action=diff=7=8
Comment:
Add requirement to start a vote before migration
15 matches
Mail list logo