Re: Applicability of PolyhedronsSet for high polygon counts

I really appreciate the quick response. Even though I believe this API has the functionality I need, I'm not really sure I can easily tune the performance. I need to check out a few other APIs to determine if they will be a better fit, and if I can't find anything that fits, I'll probably see

Re: [ALL] Git repository for a sandbox component?

GitHub mirrors both the svn and git repos for ASF projects, so you get the advantages either way. Merging pull requests from GitHub is easier via git, but they do provide .patch files as well which work just as well in svn. On 5 November 2016 at 13:54, Eric Barnhill

Re: commons-io git repository write access

Nothing if you are an Apache committer already, you have karma automatically. Gary On Nov 5, 2016 2:43 PM, "Pascal Schumacher" wrote: > Hello everybody, > > if nobody objects I would like to help maintaining commons-io. > > What would I have to do in order to get

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

There is no need to maintain BC since 2.0 is not out. Changing package names and Maven coordinates must also happen hand in hand. Changing one means changing the other. Gary On Nov 5, 2016 1:37 PM, "Thomas Vandahl" wrote: > Hi Oliver, > > On 05.11.16 21:18, Oliver Heger wrote:

Re: [ALL] Git repository for a sandbox component?

On Sat, 5 Nov 2016 19:54:02 +0100, Eric Barnhill wrote: Speaking for myself either is fine. I find svn commands easier to deal with than git, but github is easy to use as a site. I find the above a little contradictory but since you are going to manage this, it's up to you. ;-) Gilles

[GitHub] commons-io pull request #26: README.md: update maven coordinates to version ...

GitHub user PascalSchumacher opened a pull request: https://github.com/apache/commons-io/pull/26 README.md: update maven coordinates to version 2.5 You can merge this pull request into a Git repository by running: $ git pull https://github.com/PascalSchumacher/commons-io

commons-io git repository write access

Hello everybody, if nobody objects I would like to help maintaining commons-io. What would I have to do in order to get write access to the git repository? -Pascal - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org

[GitHub] commons-io pull request #25: IO-514: Remove org.apache.commons.io.Java7Suppo...

GitHub user PascalSchumacher opened a pull request: https://github.com/apache/commons-io/pull/25 IO-514: Remove org.apache.commons.io.Java7Support You can merge this pull request into a Git repository by running: $ git pull https://github.com/PascalSchumacher/commons-io

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

Hi Oliver, On 05.11.16 21:18, Oliver Heger wrote: > It seems that there are many breaking changes between this release and > beta1; for instance, the clirr report for the core component lists > numerous errors. Is it not against Commons policy to publish > incompatible artifacts with the same

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

It seems that there are many breaking changes between this release and beta1; for instance, the clirr report for the core component lists numerous errors. Is it not against Commons policy to publish incompatible artifacts with the same maven and package coordinates to Maven central? Oliver Am

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

Good to know, TY. Hopefully someone will take the time to review over the weekend. Gary On Sat, Nov 5, 2016 at 12:37 PM, Thomas Vandahl wrote: > On 05.11.16 20:24, Gary Gregory wrote: > > Time to tally? > > I would like to. However, AFAIK, we are one PMC vote short. > > Bye,

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

On 05.11.16 20:24, Gary Gregory wrote: > Time to tally? I would like to. However, AFAIK, we are one PMC vote short. Bye, Thomas. - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail:

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

Time to tally? Gary On Sat, Nov 5, 2016 at 4:38 AM, Thomas Vandahl wrote: > On 01.11.16 09:24, Thomas Vandahl wrote: > > [X] +1 Release these artifacts > > [ ] +0 OK, but... > > [ ] -0 OK, but really should fix... > > [ ] -1 I oppose this release because... > > My

Re: [ALL] Git repository for a sandbox component?

Speaking for myself either is fine. I find svn commands easier to deal with than git, but github is easy to use as a site. Eric On Sat, Nov 5, 2016 at 4:43 PM, Gilles wrote: > On Sat, 5 Nov 2016 09:53:01 -0500, Matt Sicker wrote: > >> Is this a vote of some sort

Re: commons-filter sandbox is operational

Hi Eric, the error came from not having a site subtree. I've added one. That needs to change so that it fits into the numbering scheme of the library. I guess it will be a sub-topic in the filter.xml? Either way "mvn site" works now to get it going. /Bernd On 02/11/16 09:09, Eric Barnhill

Re: Applicability of PolyhedronsSet for high polygon counts

Hello. On Fri, 4 Nov 2016 23:57:48 -0500, Wes Gilster wrote: I've been using the commons math geometry libraries for some simple 2d intersection functions, but I'm now interested in expanding it's use to include some manipulation of 3d models with polygon counts that will easily reach 200,000

Re: [ALL] Git repository for a sandbox component?

On Sat, 5 Nov 2016 09:53:01 -0500, Matt Sicker wrote: Is this a vote of some sort to convert from svn? Not really (at least if your question is whether I ask to convert the whole sandbox, or all sandbox components). I thought that a sandbox component had to use the same repository as all

Re: [ALL] Git repository for a sandbox component? (Was: commons-filter sandbox is operational)

Is this a vote of some sort to convert from svn? So far we've all been pretty on board with migrating Commons projects to git. On 4 November 2016 at 16:27, Gilles wrote: > Hello. > > I noticed that the "Text" component uses "git". > It would be simpler to also use

Re: [VOTE] Release Apache Commons JCS 2.0-beta-2 based on RC2

On 01.11.16 09:24, Thomas Vandahl wrote: > [X] +1 Release these artifacts > [ ] +0 OK, but... > [ ] -0 OK, but really should fix... > [ ] -1 I oppose this release because... My vote. Bye, Thomas - To unsubscribe,