[geometry] Points and Vectors Proposal

Hi all, I'd like to propose an update to the Euclidean Point/Vector classes in the geometry project. We currently have a single CartesianXD class per dimension (eg, Cartesian2D) that implements both the Point and Vector interfaces. This is similar to the previous commons-math version where we

Re: Discuss [VOTE] Migrate Commons Weaver to Git

On 22 April 2018 at 17:58, Matt Sicker wrote: > We can easily convert the existing git repos over to gitbox. The only > changes we'll need to make here will be updating the SCM URLs (both in > pom.xml and the current site) to point to the proper subdomain. Existing > clones from

Re: [VOTE] Migrate existing Git repos to GitBox

An example project already using gitbox is whimsy: https://github.com/apache/whimsy On 22 April 2018 at 14:06, ajs6f wrote: > I have asked INFRA about this (for another project) and they confirmed > that GitBox runs the mirroring Github => Apache, so that PRs can be merged >

Re: [VOTE] Migrate existing Git repos to GitBox

I have asked INFRA about this (for another project) and they confirmed that GitBox runs the mirroring Github => Apache, so that PRs can be merged at Github. I did not ask about whether commits can also be pushed directly to Apache. ajs6f > On Apr 22, 2018, at 3:03 PM, Matt Sicker

Re: [VOTE] Migrate existing Git repos to GitBox

On 22 April 2018 at 13:34, Ralph Goers wrote: > For example, with GitBox can we now merge pull requests directly at > GitHub? That would be a nice benefit. Can we still commit to the ASF git > repo or only at GitHub? > >From my understanding, you can merge PRs

Re: [VOTE] Migrate existing Git repos to GitBox

On 2018-04-22, Matt Sicker wrote: > This is a vote to migrate existing Git repositories from the old git-wip-us > infrastructure to the new gitbox infrastructure. New Apache projects are > not allowed to use git-wip-us and are instead directed to use gitbox. As > such, it makes sense for us to

Re: [VOTE] Migrate existing Git repos to GitBox

+1 Although I really would like to see documentation somewhere on how the process differs. For example, with GitBox can we now merge pull requests directly at GitHub? That would be a nice benefit. Can we still commit to the ASF git repo or only at GitHub? Ralph > On Apr 22, 2018, at 10:07

Re: [VOTE] Migrate existing Git repos to GitBox

+1 Oliver Am 22.04.2018 um 19:07 schrieb Matt Sicker: > This is a vote to migrate existing Git repositories from the old git-wip-us > infrastructure to the new gitbox infrastructure. New Apache projects are > not allowed to use git-wip-us and are instead directed to use gitbox. As > such, it

Re: [VOTE] Migrate existing Git repos to GitBox

+1 > On Apr 22, 2018, at 1:21 PM, Gary Gregory wrote: > > +1 > > Gary > >> On Sun, Apr 22, 2018, 11:07 Matt Sicker wrote: >> >> This is a vote to migrate existing Git repositories from the old git-wip-us >> infrastructure to the new gitbox

Re: [VOTE] Migrate existing Git repos to GitBox

+1 Gary On Sun, Apr 22, 2018, 11:07 Matt Sicker wrote: > This is a vote to migrate existing Git repositories from the old git-wip-us > infrastructure to the new gitbox infrastructure. New Apache projects are > not allowed to use git-wip-us and are instead directed to use

Re: [VOTE] Migrate existing Git repos to GitBox

+1 Le 22 avr. 2018 19:10, "Pascal Schumacher" a écrit : > +1 > > Am 22.04.2018 um 19:07 schrieb Matt Sicker: > >> This is a vote to migrate existing Git repositories from the old >> git-wip-us >> infrastructure to the new gitbox infrastructure. New Apache projects are

Re: [VOTE] Migrate existing Git repos to GitBox

+1 Am 22.04.2018 um 19:07 schrieb Matt Sicker: This is a vote to migrate existing Git repositories from the old git-wip-us infrastructure to the new gitbox infrastructure. New Apache projects are not allowed to use git-wip-us and are instead directed to use gitbox. As such, it makes sense for

[VOTE] Migrate existing Git repos to GitBox

This is a vote to migrate existing Git repositories from the old git-wip-us infrastructure to the new gitbox infrastructure. New Apache projects are not allowed to use git-wip-us and are instead directed to use gitbox. As such, it makes sense for us to stay consistent with other projects. The

Re: Discuss [VOTE] Migrate Commons Weaver to Git

We can easily convert the existing git repos over to gitbox. The only changes we'll need to make here will be updating the SCM URLs (both in pom.xml and the current site) to point to the proper subdomain. Existing clones from git-wip-us.a.o or elsewhere can be updated by changing the remote url

Re: [lang] [LANG-1393] Add API SystemUtils.String getEnvironmentVariable(final String name, final String defaultValue).

Thank you for the review. Done: https://issues.apache.org/jira/browse/LANG-1394 Gary On Sun, Apr 22, 2018 at 7:06 AM, sebb wrote: > On 22 April 2018 at 13:44, Gary Gregory wrote: > > On Sun, Apr 22, 2018, 03:55 sebb wrote: > > > >>

Re: Discuss [VOTE] Migrate Commons Weaver to Git

On Sun, Apr 22, 2018 at 10:34 AM, Matt Benson wrote: > Shall we call a second vote to move all components to gitbox, then? > That would be fine with me. My understanding of such a VOTE is that we would not saddle ourselves with a ton of work ASAP but indicates our intent and

Re: [compress][io] Avoid InputStream#skip?

Hi All: We should at the very least document all of this carefully. My gut reaction is that an API called skip should call skip internally. Doing anything else clever as you point out has performance implications and might violate the principle of least surprise. We could consider creating a

Re: Discuss [VOTE] Migrate Commons Weaver to Git

Shall we call a second vote to move all components to gitbox, then? Matt On Sun, Apr 22, 2018 at 11:31 AM, Gary Gregory wrote: > On Sun, Apr 22, 2018 at 10:26 AM, Oliver Heger < > oliver.he...@oliver-heger.de > > wrote: > > > > > > > Am 21.04.2018 um 22:31 schrieb Matt

Re: Discuss [VOTE] Migrate Commons Weaver to Git

On Sun, Apr 22, 2018 at 10:26 AM, Oliver Heger wrote: > > > Am 21.04.2018 um 22:31 schrieb Matt Sicker: > > I opened an infra ticket [1] to find out our options here. My preferred > > option would be to migrate all of Commons over to gitbox for consistency. > >

Re: Discuss [VOTE] Migrate Commons Weaver to Git

Am 21.04.2018 um 22:31 schrieb Matt Sicker: > I opened an infra ticket [1] to find out our options here. My preferred > option would be to migrate all of Commons over to gitbox for consistency. Many thanks, Matt! I would be +1 for a mass conversion, too. I think, nobody has objections against

Re: [1/2] commons-compress git commit: COMPRESS-447 turn ArrayIndexOutOfBoundsExceptions into ZipExceptions

Simple and pragmatic: -) Gary On Sun, Apr 22, 2018, 09:45 wrote: > Repository: commons-compress > Updated Branches: > refs/heads/master 777853369 -> 166b186e8 > > > COMPRESS-447 turn ArrayIndexOutOfBoundsExceptions into ZipExceptions > > > Project:

[compress][io] Avoid InputStream#skip?

Hi all while looking into https://issues.apache.org/jira/browse/COMPRESS-449 I realized that calling skip on any InputStream probably means you are up to receiving an IOException because some stream in there decided to implement skip via seek and now faces a stream that doesn't support seek. And

Re: [lang] [LANG-1393] Add API SystemUtils.String getEnvironmentVariable(final String name, final String defaultValue).

On 22 April 2018 at 13:44, Gary Gregory wrote: > On Sun, Apr 22, 2018, 03:55 sebb wrote: > >> On 20 April 2018 at 15:55, wrote: >> > Repository: commons-lang >> > Updated Branches: >> > refs/heads/master 8e3ec1722 -> efba54d35 >>

Re: [lang] [LANG-1393] Add API SystemUtils.String getEnvironmentVariable(final String name, final String defaultValue).

On Sun, Apr 22, 2018, 03:55 sebb wrote: > On 20 April 2018 at 15:55, wrote: > > Repository: commons-lang > > Updated Branches: > > refs/heads/master 8e3ec1722 -> efba54d35 > > > > > > [LANG-1393] Add API SystemUtils.String getEnvironmentVariable(final >

Re: [lang] [LANG-1393] Add API SystemUtils.String getEnvironmentVariable(final String name, final String defaultValue).

On 20 April 2018 at 15:55, wrote: > Repository: commons-lang > Updated Branches: > refs/heads/master 8e3ec1722 -> efba54d35 > > > [LANG-1393] Add API SystemUtils.String getEnvironmentVariable(final > String name, final String defaultValue). > > Project:

[GitHub] commons-text issue #80: travis: add Java 10

Github user coveralls commented on the issue: https://github.com/apache/commons-text/pull/80 [](https://coveralls.io/builds/16636653) Coverage remained the same at 97.833% when pulling

[GitHub] commons-text issue #80: travis: add Java 10

Github user PascalSchumacher commented on the issue: https://github.com/apache/commons-text/pull/80 Not yet available on travis: `Sorry, but JDK 'oraclejdk10' is not known.` --- - To unsubscribe, e-mail:

[GitHub] commons-text pull request #80: travis: add Java 10

Github user PascalSchumacher closed the pull request at: https://github.com/apache/commons-text/pull/80 --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail:

[GitHub] commons-text pull request #80: travis: add Java 10

GitHub user PascalSchumacher opened a pull request: https://github.com/apache/commons-text/pull/80 travis: add Java 10 You can merge this pull request into a Git repository by running: $ git pull https://github.com/PascalSchumacher/commons-text travis_jdk10 Alternatively you