Re: [all] github

2020-07-27 Thread Stefan Bodewig 
On 2020-07-26, Melloware wrote:

> I know there seems to to be a holy war about the use of GitHub going
> on here

This has never been my intention. Far from it. And if you believ I've
tried to start any kind of war you must have misread my original mail
completely. I'm really sorry about thaty.

I appreciate the benefits github brings but realize it also causes
problems that I don't know how to solve. I would have liked to talk
about what we can do to build communities around components again rather
than whether creating PRs is better than not doing that.

Maybe I should have written an essay and not bother the list. All that
hapened is that I've caused another stirrup about topics I didn't even
intend to touch.

I'll rest my case as this is not going to become productive.

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: Build failed in Jenkins: commons-io-windows #527

2020-07-27 Thread Gary Gregory 
Matt,

Any thoughts?

Gary

On Mon, Jul 27, 2020 at 7:42 AM Apache Jenkins Server <
jenk...@builds.apache.org> wrote:

> See  >
>
> Changes:
>
>
> --
> [...truncated 40.01 MB...]
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
> Source)
> at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)
> at java.lang.Thread.run(Unknown Source)
> java.nio.file.AccessDeniedException: <
> https://builds.apache.org/job/commons-io-windows/ws/target\test-classes\test-file-x-windows-950.bin
> >
> at sun.nio.fs.WindowsException.translateToIOException(Unknown
> Source)
> at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
> at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
> at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)
> at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown
> Source)
> at java.nio.file.Files.deleteIfExists(Unknown Source)
> at
> jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)
> at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)
> at
> jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)
> at
> jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)
> at
> jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215)
> at
> jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)
> at
> jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215)
> at
> jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)
> at
> jenkins.util.io.PathRemover.forceRemoveDirectoryContents(PathRemover.java:87)
> at hudson.Util.deleteContentsRecursive(Util.java:259)
> at hudson.Util.deleteContentsRecursive(Util.java:248)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:699)
> at
> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
> at
> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
> at hudson.remoting.UserRequest.perform(UserRequest.java:212)
> at hudson.remoting.UserRequest.perform(UserRequest.java:54)
> at hudson.remoting.Request$2.run(Request.java:369)
> at
> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
> at java.util.concurrent.FutureTask.run(Unknown Source)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown
> Source)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
> Source)
> at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)
> at java.lang.Thread.run(Unknown Source)
> java.nio.file.AccessDeniedException: <
> https://builds.apache.org/job/commons-io-windows/ws/target\test-classes\test-file-x-windows-950.bin
> >
> at sun.nio.fs.WindowsException.translateToIOException(Unknown
> Source)
> at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
> at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown Source)
> at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)
> at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown
> Source)
> at java.nio.file.Files.deleteIfExists(Unknown Source)
> at
> jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)
> at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)
> at
> jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)
> at
> jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)
> at
> jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215)
> at
> jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)
> at
> jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215)
> at
> jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)
> at
> jenkins.util.io.PathRemover.forceRemoveDirectoryContents(PathRemover.java:87)
> at hudson.Util.deleteContentsRecursive(Util.java:259)
> at hudson.Util.deleteContentsRecursive(Util.java:248)
> at
> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:699)
> at
> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
> at
> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
> at hudson.remoting.UserRequest.perform(UserRequest.java:212)
> at hudson.remoting.UserRequest.perform(Use

[SITE] Apache Buildbot fails to publish as it uses HTTP instead of HTTPS

2020-07-27 Thread Gary Gregory 
How can we fix our site buildbot to use HTTPS?

Apache Buildbot fails to publish as it uses HTTP instead of HTTPS:

https://ci.apache.org/builders/commons-site-staging/builds/333/steps/compile/logs/stdio


TY!
Gary

Re: [SITE] Apache Buildbot fails to publish as it uses HTTP instead of HTTPS

2020-07-27 Thread Gary Gregory 
On Mon, Jul 27, 2020 at 8:09 AM Gary Gregory  wrote:

> How can we fix our site buildbot to use HTTPS?
>
> Apache Buildbot fails to publish as it uses HTTP instead of HTTPS:
>
>
> https://ci.apache.org/builders/commons-site-staging/builds/333/steps/compile/logs/stdio
>
>
>
Hm maybe the buildbox machine has an old settings.xml with HTTP in it
instead of HTTPS...?

Gary

> TY!
> Gary
>

Re: Build failed in Jenkins: commons-io-windows #527

2020-07-27 Thread Matt Sicker 
Looks like a test is leaving behind a file that can’t be deleted. One
potential workaround might be to run mvn clean afterwards if you’re
clearing the workspace every time like that.

On Mon, Jul 27, 2020 at 07:02 Gary Gregory  wrote:

> Matt,
>
> Any thoughts?
>
> Gary
>
> On Mon, Jul 27, 2020 at 7:42 AM Apache Jenkins Server <
> jenk...@builds.apache.org> wrote:
>
>> See <
>> https://builds.apache.org/job/commons-io-windows/527/display/redirect>
>>
>> Changes:
>>
>>
>> --
>> [...truncated 40.01 MB...]
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
>> Source)
>> at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)
>> at java.lang.Thread.run(Unknown Source)
>> java.nio.file.AccessDeniedException: <
>> https://builds.apache.org/job/commons-io-windows/ws/target\test-classes\test-file-x-windows-950.bin
>> >
>> at sun.nio.fs.WindowsException.translateToIOException(Unknown
>> Source)
>> at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown
>> Source)
>> at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown
>> Source)
>> at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)
>> at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown
>> Source)
>> at java.nio.file.Files.deleteIfExists(Unknown Source)
>> at
>> jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:237)
>> at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)
>> at
>> jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)
>> at
>> jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)
>> at
>> jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215)
>> at
>> jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)
>> at
>> jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215)
>> at
>> jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)
>> at
>> jenkins.util.io.PathRemover.forceRemoveDirectoryContents(PathRemover.java:87)
>> at hudson.Util.deleteContentsRecursive(Util.java:259)
>> at hudson.Util.deleteContentsRecursive(Util.java:248)
>> at
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:699)
>> at
>> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:153)
>> at
>> org.jenkinsci.plugins.gitclient.RemoteGitImpl$CommandInvocationHandler$1.call(RemoteGitImpl.java:146)
>> at hudson.remoting.UserRequest.perform(UserRequest.java:212)
>> at hudson.remoting.UserRequest.perform(UserRequest.java:54)
>> at hudson.remoting.Request$2.run(Request.java:369)
>> at
>> hudson.remoting.InterceptingExecutorService$1.call(InterceptingExecutorService.java:72)
>> at java.util.concurrent.FutureTask.run(Unknown Source)
>> at java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown
>> Source)
>> at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown
>> Source)
>> at hudson.remoting.Engine$1.lambda$newThread$0(Engine.java:93)
>> at java.lang.Thread.run(Unknown Source)
>> java.nio.file.AccessDeniedException: <
>> https://builds.apache.org/job/commons-io-windows/ws/target\test-classes\test-file-x-windows-950.bin
>> >
>> at sun.nio.fs.WindowsException.translateToIOException(Unknown
>> Source)
>> at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown
>> Source)
>> at sun.nio.fs.WindowsException.rethrowAsIOException(Unknown
>> Source)
>> at sun.nio.fs.WindowsFileSystemProvider.implDelete(Unknown Source)
>> at sun.nio.fs.AbstractFileSystemProvider.deleteIfExists(Unknown
>> Source)
>> at java.nio.file.Files.deleteIfExists(Unknown Source)
>> at
>> jenkins.util.io.PathRemover.removeOrMakeRemovableThenRemove(PathRemover.java:241)
>> at jenkins.util.io.PathRemover.tryRemoveFile(PathRemover.java:205)
>> at
>> jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:216)
>> at
>> jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)
>> at
>> jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215)
>> at
>> jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)
>> at
>> jenkins.util.io.PathRemover.tryRemoveRecursive(PathRemover.java:215)
>> at
>> jenkins.util.io.PathRemover.tryRemoveDirectoryContents(PathRemover.java:226)
>> at
>> jenkins.util.io.PathRemover.forceRemoveDirectoryContents(PathRemover.java:87)
>> at hudson.Util.deleteContentsRecursive(Util.java:259)
>> at hudson.Util.deleteContentsRecursive(Util.java:248)
>> at
>> org.jenkinsci.plugins.gitclient.CliGitAPIImpl$2.execute(CliGitAPIImpl.java:699)
>>

[crypto] Releasing 1.1.0 with Mac64 support

2020-07-27 Thread Gary Gregory 
Hi All,

Thanks to Geoffrey Blake's help setting up a Docker Ubuntu Trusty (14.04)
environment, I am working toward creating an RC for 1.1.0, but in order to
get Mac64 support we are quite sure I need to build that binary on a Mac,
which I do not own or have simple access to.

Is there an acceptable workflow for me, the Release Manager, to procure
said binary from another person? Does that person need to be on the Commons
PMC, a Commons Committer, an Apache Commons, an Apache Member, or can it be
Anyone?

There is an obvious trust issue here since I would not be the one building
the Mac64 binary but would be delivering it through our dist area and Maven
Central.

Yes, I know that in theory, Apache only delivers source code and that our
binary distributions are only a convenience, so there might be nothing to
talk about, still, I want to make sure to check on expectations and
processes.

Gary

Re: [crypto] Releasing 1.1.0 with Mac64 support

2020-07-27 Thread Bindul Bhowmik 
Hi Gary,

(Please ignore if it has been discussed already)

On Mon, Jul 27, 2020 at 12:07 PM Gary Gregory  wrote:
>
> Hi All,
>
> Thanks to Geoffrey Blake's help setting up a Docker Ubuntu Trusty (14.04)
> environment, I am working toward creating an RC for 1.1.0, but in order to
> get Mac64 support we are quite sure I need to build that binary on a Mac,
> which I do not own or have simple access to.
>
> Is there an acceptable workflow for me, the Release Manager, to procure
> said binary from another person? Does that person need to be on the Commons
> PMC, a Commons Committer, an Apache Commons, an Apache Member, or can it be
> Anyone?
>
> There is an obvious trust issue here since I would not be the one building
> the Mac64 binary but would be delivering it through our dist area and Maven
> Central.

commons-crypto is built on OSX on travis. So, a thought on getting the
binaries out of that:
If you had a place for travis to upload the artifacts: you could fork
the repo, alter the .travis.yml to add a deployment step to upload the
built OSX binaries to your location. I think this gets you, the
release manager, a known good binary. You can add whatever 'on'
conditions for the deploy to only upload binaries from the tag, etc. I
am suggesting forking the repo, so the altered .travis.yml is not in
the release source tag and the secrets to upload the binary are only
in your github/travis org.

>
> Yes, I know that in theory, Apache only delivers source code and that our
> binary distributions are only a convenience, so there might be nothing to
> talk about, still, I want to make sure to check on expectations and
> processes.
>
> Gary

Bindul

-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

[VOTE] Release Apache Commons Pool 2.8.1 based on RC1

2020-07-27 Thread Gary Gregory 
We have fixed one bug and added a few enhancements since Apache Commons
Pool 2.8.0 was released, so I would like to release Apache Commons Pool
2.8.1.

Apache Commons Pool 2.8.1 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/pool/2.8.1-RC1 (svn
revision 40727)

The Git tag commons-pool-2.8.1-RC1 commit for this RC is
3fb7df661d521d57297d6aafa2d2d57356ae4adf which you can browse here:

https://gitbox.apache.org/repos/asf?p=commons-pool.git;a=commit;h=3fb7df661d521d57297d6aafa2d2d57356ae4adf
You may checkout this tag using:
git clone https://gitbox.apache.org/repos/asf/commons-pool.git --branch
commons-pool-2.8.1-RC1 commons-pool-2.8.1-RC1

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1509/org/apache/commons/commons-pool2/2.8.1/

These are the artifacts and their hashes:

#Release SHA-512s
#Mon Jul 27 21:09:02 EDT 2020
commons-pool2-2.8.1-bin.tar.gz=a2887c27af17691c06c23b6b44f63f71414f460f6bf8788ce15013c8dbd68989df5ca75fd87975c806b4e93d976bdd6d9af2ff824a8127416c2cc303f38a02a9
commons-pool2-2.8.1-bin.zip=3e8b7522572db4234c6ba7879d8920e7590f5c176eceb3bc1cf1dfddf84e13f0ee12e7e839831b54ecb1ed367d4c67936335adbc13460a8bfe6469765550
commons-pool2-2.8.1-javadoc.jar=7cfdc4f238fdd298dd690823c1d8a2e43629d75851152d369383a7007ebf559e0f231a1d05a027f9476d3dcd16502ee39c818f18176e8fd398d4300948098195
commons-pool2-2.8.1-sources.jar=1d679ec95dcd105eb8b619cbe0755693d15495a19b64609e9ccba7137a5307b2dc7b18276aa26d5af28d90465e925984257d26e7f40870456de26a6c6a84cb95
commons-pool2-2.8.1-src.tar.gz=4cece944ac8b4b1f76bcf78355b3262b043f1a00699da0334fff622a7e5042c5b51defc625c292f1fb228af43fd0608a4c6bdbd083c32d944d7d2c8e89dd106c
commons-pool2-2.8.1-src.zip=7351bb17f2144742f145cd936ab10c0e90ef1e568d88637e96a1dc03e60dfca2f9902036b0e58a8790600c03b03da2a62779d1cab5d50bec7f4a1621de2313de
commons-pool2-2.8.1-test-sources.jar=0c4c4d7d57bbc1bfa7b6bf6eacf2cbf980e0f88972af6c2fdbdf7f91afdf681c14bb5c58844490562214e898a66da3e022ada29a3fe52556f780c4b08e8ff42c
commons-pool2-2.8.1-tests.jar=84a939f018f1a9f0dc28f822144566883d685bfc75f05d072aeef3504cec51f4f92d92fd37fa41c5608505b5001fd04da15b1b81143abf4202d8922ff678ca0f

I have tested this with

mvn -V -Duser.name=%my_apache_id%
-Dcommons.release-plugin.version=%commons.release-plugin.version% -Prelease
-Ptest-deploy -P jacoco -P japicmp clean package site deploy

using:

Apache Maven 3.6.3 (cecedd343002696d0abb50b32b541b8a6ba2883f)
Maven home: C:\Java\apache-maven-3.6.3\bin\..
Java version: 1.8.0_251, vendor: Oracle Corporation, runtime: C:\Program
Files\Java\jdk1.8.0_251\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Details of changes since 2.8.0 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/pool/2.8.1-RC1/RELEASE-NOTES.txt

https://dist.apache.org/repos/dist/dev/commons/pool/2.8.1-RC1/site/changes-report.html

Site:

https://dist.apache.org/repos/dist/dev/commons/pool/2.8.1-RC1/site/index.html
(note some *relative* links are broken and the 2.8.1 directories are
not yet created - these will be OK once the site is deployed.)

JApiCmp Report (compared to 2.8.0):

https://dist.apache.org/repos/dist/dev/commons/pool/2.8.1-RC1/site/japicmp.html

RAT Report:

https://dist.apache.org/repos/dist/dev/commons/pool/2.8.1-RC1/site/rat-report.html

KEYS:
  https://www.apache.org/dist/commons/KEYS

Please review the release candidate and vote.
This vote will close no sooner that 72 hours from now.

  [ ] +1 Release these artifacts
  [ ] +0 OK, but...
  [ ] -0 OK, but really should fix...
  [ ] -1 I oppose this release because...

Thank you,

Gary Gregory,
Release Manager (using key 86fdc7e2a11262cb)

For following is intended as a helper and refresher for reviewers.

Validating a release candidate
==

These guidelines are NOT complete.

Requirements: Git, Java, Maven.

You can validate a release from a release candidate (RC) tag as follows.

1) Clone and checkout the RC tag

git clone https://gitbox.apache.org/repos/asf/commons-pool.git --branch
commons-pool-2.8.1-RC1 commons-pool-2.8.1-RC1
cd commons-pool-2.8.1-RC1

2) Check Apache licenses

This step is not required if the site includes a RAT report page which you
then must check.

mvn apache-rat:check

3) Check binary compatibility

Older components still use Apache Clirr:

This step is not required if the site includes a Clirr report page which
you then must check.

mvn clirr:check

Newer components use JApiCmp with the japicmp Maven Profile:

This step is not required if the site includes a JApiCmp report page which
you then must check.

mvn install -DskipTests -P japicmp japicmp:cmp

4) Build the package

mvn -V clean package

You can record the Maven and Java version produced by -V in your VOTE reply.
To gather OS information from a command line:
Windows: ver
Linux: uname -a

5) Build the site for a single module project

Note: S