[GitHub] sebkur opened a new pull request #1: Fix link to Javadocs

sebkur opened a new pull request #1: Fix link to Javadocs URL: https://github.com/apache/commons-build-plugin/pull/1 I noticed, in multiple projects, that in the README.md file, the link to the Javadocs is broken. I think this PR properly fixes this issue. Examples: https://github.co

[RESULT][VOTE][RC2] Commons collections 4.3 (take 2)

Hello All, I'm closing the VOTE, 72 hours are over The VOTE was successful, it receives 3 binding +1 Rob Tompkins, Gary Gregory, Gilles Sadowski On Fri, 1 Feb 2019 at 20:49, Gilles Sadowski wrote: > > Hi. > > Le jeu. 31 janv. 2019 à 12:23, Maxim Solodovnik a > écrit : > > > > This is a [VOTE]

[GitHub] sebkur commented on issue #1: Fix link to Javadocs

sebkur commented on issue #1: Fix link to Javadocs URL: https://github.com/apache/commons-build-plugin/pull/1#issuecomment-460297548 Exactly, they are in the 'apidocs' folder, however if you look at the README.md, for example here: https://github.com/apache/commons-bcel it points to 'java

[GitHub] garydgregory merged pull request #1: Fix link to Javadocs

garydgregory merged pull request #1: Fix link to Javadocs URL: https://github.com/apache/commons-build-plugin/pull/1 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub an

[GitHub] garydgregory commented on issue #1: Fix link to Javadocs

garydgregory commented on issue #1: Fix link to Javadocs URL: https://github.com/apache/commons-build-plugin/pull/1#issuecomment-460298733 Thank you@sebkur!, This is an automated message from the Apache Git Service. To respo

[GitHub] garydgregory edited a comment on issue #1: Fix link to Javadocs

garydgregory edited a comment on issue #1: Fix link to Javadocs URL: https://github.com/apache/commons-build-plugin/pull/1#issuecomment-460298733 Thank you @sebkur ! This is an automated message from the Apache Git Service. T

[GitHub] chtompki commented on issue #1: Fix link to Javadocs

chtompki commented on issue #1: Fix link to Javadocs URL: https://github.com/apache/commons-build-plugin/pull/1#issuecomment-460299962 Yes indeed, many thanks. This is an automated message from the Apache Git Service. To resp

Re: [VOTE] Release Apache Commons VFS 2.3 based on RC2

+1 signatures, rat, (minor nits) checkstyle issues, (minor nits) findbugs issues. I had a build issue with java11 that looks insurmountable for this release. Specifically: Tests in error: AbstractFtpsProviderTestCase$FtpProviderTestSuite>AbstractTestSuite.run:137->setUp:153->AbstractTestS

Re: [VOTE] Release Apache Commons VFS 2.3 based on RC2

Thanks Rob. I had the same Java 11 issues but forgot to mention it in the original email, sorry about that. I would like a subsequent release to deal with any issues building on Java 11. May I please have more PMC VOTEs? Gary On Mon, Feb 4, 2019 at 11:00 AM Rob Tompkins wrote: > +1 > > signatu

[GitHub] sebkur commented on issue #1: Fix link to Javadocs

sebkur commented on issue #1: Fix link to Javadocs URL: https://github.com/apache/commons-build-plugin/pull/1#issuecomment-460343209 Can't figure out how to regenerate the README.md though. I try this: mvn commons-build:readme-md But it fails: [ERROR] No plugin

[GitHub] garydgregory commented on issue #1: Fix link to Javadocs

garydgregory commented on issue #1: Fix link to Javadocs URL: https://github.com/apache/commons-build-plugin/pull/1#issuecomment-460345294 You have to build and install it first: 'mvn clean install'. This is an automated mess

Re: [VOTE] Release Apache Commons VFS 2.3 based on RC2

+1 looks good Am 04.02.2019 um 17:00 schrieb Rob Tompkins: +1 signatures, rat, (minor nits) checkstyle issues, (minor nits) findbugs issues. I had a build issue with java11 that looks insurmountable for this release. Specifically: Tests in error: AbstractFtpsProviderTestCase$FtpProvider

[VOTE][RESULT] Release Apache Commons VFS 2.3 based on RC2

This VOTE passes with the following +1s: - Otto Fowler (non-binding) - Woonsan Ko (non-binding) - Gary Gregory (binding) - Rob Tompkins (binding) - Pascal Schumacher (binding) No other VOTEs were cast. Thank you all! Gary On Fri, Feb 1, 2019 at 12:36 PM Gary Gregory wrote: > We have fixed qui

[ANNOUNCE] All proper svn development repos in gitbox

Hello all, We just finished up putting all of the following repositories from proper svn in to gitbox (many thanks to Chris Lambertus): bcel/ beanutils/ bsf/ chain/ codec/ commons-parent/ commons-skin/ commons-configuration/ daemon/ digester/ email/ exec/ functor/ jci/ jcs/ jelly/

Re: [ANNOUNCE] All proper svn development repos in gitbox

Thanks Rob! Do all repos use master as the default branch? Are all trunk branches gone? Gary On Mon, Feb 4, 2019 at 1:58 PM Rob Tompkins wrote: > Hello all, > > We just finished up putting all of the following repositories from proper > svn in to gitbox (many thanks to Chris Lambertus): > > bce

Re: [ANNOUNCE] All proper svn development repos in gitbox

The still exist, but we can delete them in the github UI even -Rob > On Feb 4, 2019, at 2:00 PM, Gary Gregory wrote: > > Thanks Rob! Do all repos use master as the default branch? Are all trunk > branches gone? > > Gary > > On Mon, Feb 4, 2019 at 1:58 PM Rob Tompkins wrote: > >> Hello all,

[VFS] Tests fail on Java 11

Now that 2.3 is done, I'd like some help to get the build running on Java 11, which currently fails in the tests: https://travis-ci.org/apache/commons-vfs/jobs/488728611 The failures might all be related to the antique version of Apache Mina and JackRabbit we are using. Does anyone have the know