Re: [release-plugin] commit failure con't

[Rob Tompkins]

> On Jun 13, 2018, at 7:22 PM, Gary Gregory  wrote:
> 
> Looking at http://svnbook.red-bean.com/en/1.8/svn.ref.svn.c.add.html, it
> seems we can just do a SCM add of the three folders (binaries, source,
> site) instead of each file in those folders.
> 
> Thoughts?

I’ll give that a shot first thing in the morning. And I’ll continue to stage to 
a “SNAPSHOT” for testing purposes, yeah?

-Rob

> 
> Gary
> 
>> On Wed, Jun 13, 2018 at 5:17 PM Gary Gregory  wrote:
>> 
>> Rob,
>> 
>> In our code, we have:
>> 
>> new ScmFileSet(distCheckoutDirectory, filesToCommit);
>> 
>> The Javadoc for ScmFileSet says that the filesToCommit list must be
>> _relative_ to the base dir in  distCheckoutDirectory. For example, in our
>> tests distCheckoutDirectory is:
>> 
>> target\testing-commons-release-plugin\scm
>> 
>> and the first file to commit in the list is:
>> 
>> 
>> target\testing-commons-release-plugin\scm\1.0-SNAPSHOT-RC1\binaries\commons-text-1.4-bin.tar.gz
>> 
>> Obviously one is not relative to the other, they are both relative to the
>> _same_ place.
>> 
>> Gary
>> 

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

Re: [DBCP] DelegatingConnection, hashCode(), and equals()

[Gary Gregory]

The RC is out. Please review it :-)

Gary

On Tue, Jun 12, 2018, 15:49 Gary Gregory  wrote:

> After fixing prepared statements in the cpdsadapter package, I found a
> cleaner solution that delegates all prepared and callable statement pooling
> to DBCP's cpdsadapter.
>
> Thank you for the feedback.
>
> I think I am ready to create an RC for DBCP 2.4.0.
>
> Gary
>
> On Thu, Jun 7, 2018 at 5:01 PM Gary Gregory 
> wrote:
>
>> Thanks for your feedback Mark.
>>
>> Looking deeper into DBCP for a cleaner solution, it seems we are missing
>> support for preparing callable statements
>> in org.apache.commons.dbcp2.cpdsadapter.ConnectionImpl
>> and org.apache.commons.dbcp2.cpdsadapter.PooledConnectionImpl. I see APIs
>> implemented for prepareStatement(*) but not prepareCall(*). That's a big
>> hole for our server. I'll look into filling it now...
>>
>> Gary
>>
>> On Thu, Jun 7, 2018 at 1:09 PM, Mark Thomas  wrote:
>>
>>> On 07/06/18 17:18, Matt Sicker wrote:
>>> > This sounds like an honest bug that should be fixed, backwards
>>> > compatibility be damned. I don't see how the old behavior is useful for
>>> > anything other than connection starvation or some other strange
>>> behavior.
>>>
>>> I have completely the opposite view.
>>>
>>> There is nothing in the DBCP API that suggests that a Connection object
>>> provided by the pool will ever be seen by the client again.
>>>
>>> The implementation below sounds like deliberate misuse of the pool.
>>> Clients are not meant to retain references to objects that have been
>>> returned to the pool. To do so is nearly always the cause of all sorts
>>> of problems. I would be very strongly against any change that encouraged
>>> that sort of misuse.
>>>
>>> What is the actual use case here? What is the purpose of retaining this
>>> Map? Maybe we can come up with a better solution and/or an API change
>>> that enables the requirement to be met without having to retain
>>> references to connections after they have been returned to the pool.
>>>
>>> Mark
>>>
>>>
>>> >
>>> > On 7 June 2018 at 10:44, Gary Gregory  wrote:
>>> >
>>> >> Hi All:
>>> >>
>>> >> I just ran into a case where different instances of subclasses
>>> >> of DelegatingConnection like PoolGuardConnectionWrapper and
>>> ConnectionImpl
>>> >> are used as keys in a Map (Map)
>>> >>
>>> >> The problem is that when you borrow a Connection out of a pool, you
>>> get a
>>> >> new PoolGuardConnectionWrapper, so that the Map in the eventual call
>>> site
>>> >> grows and grows because the intention is that the Map key should be
>>> the
>>> >> same when you borrow the same underlying Connection later.
>>> >>
>>> >> If DelegatingConnection implemented hashCode() and equals() to
>>> account for
>>> >> some or all of its instance variables, then one could use
>>> >> DelegatingConnection instances as keys in a Map with the behavior I
>>> expect,
>>> >> YMMV.
>>> >>
>>> >> The issue is that implementing hashCode() and equals() where we did
>>> not
>>> >> before could have unexpected side-effects for existing applications.
>>> >>
>>> >> Thoughts?
>>> >>
>>> >> Gary
>>> >>
>>> >
>>> >
>>> >
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>
>>>
>>

Re: [release-plugin] commit failure con't

[Gary Gregory]

Looking at http://svnbook.red-bean.com/en/1.8/svn.ref.svn.c.add.html, it
seems we can just do a SCM add of the three folders (binaries, source,
site) instead of each file in those folders.

Thoughts?

Gary

On Wed, Jun 13, 2018 at 5:17 PM Gary Gregory  wrote:

> Rob,
>
> In our code, we have:
>
> new ScmFileSet(distCheckoutDirectory, filesToCommit);
>
> The Javadoc for ScmFileSet says that the filesToCommit list must be
> _relative_ to the base dir in  distCheckoutDirectory. For example, in our
> tests distCheckoutDirectory is:
>
> target\testing-commons-release-plugin\scm
>
> and the first file to commit in the list is:
>
>
> target\testing-commons-release-plugin\scm\1.0-SNAPSHOT-RC1\binaries\commons-text-1.4-bin.tar.gz
>
> Obviously one is not relative to the other, they are both relative to the
> _same_ place.
>
> Gary
>

[release-plugin] commit failure con't

[Gary Gregory]

Rob,

In our code, we have:

new ScmFileSet(distCheckoutDirectory, filesToCommit);

The Javadoc for ScmFileSet says that the filesToCommit list must be
_relative_ to the base dir in  distCheckoutDirectory. For example, in our
tests distCheckoutDirectory is:

target\testing-commons-release-plugin\scm

and the first file to commit in the list is:

target\testing-commons-release-plugin\scm\1.0-SNAPSHOT-RC1\binaries\commons-text-1.4-bin.tar.gz

Obviously one is not relative to the other, they are both relative to the
_same_ place.

Gary

Re: [release-plugin][build-plugin] Java 8

[Pascal Schumacher]

+1

Am 13.06.2018 um 23:07 schrieb Gary Gregory:

I propose we make our release-plugin require Java 8. Newer dependencies
like the latest Checkstyle require Java 8.

Gary




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

Re: [release-plugin][build-plugin] Java 8

[Rob Tompkins]

> On Jun 13, 2018, at 5:07 PM, Gary Gregory  wrote:
> 
> I propose we make our release-plugin require Java 8. Newer dependencies
> like the latest Checkstyle require Java 8.

+1

> 
> Gary

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

Re: [apache/commons-release-plugin] Update Checkstyle 6.19 -> 8.10.1. OK: mvn clean site (13210c7)

[Rob Tompkins]

> On Jun 13, 2018, at 4:39 PM, Gary Gregory  wrote:
> 
> It we should just make the plugin require Java 8.
> 

Seems reasonable to me. 

> Gary
> 
> On Wed, Jun 13, 2018 at 1:27 PM Pascal Schumacher 
> wrote:
> 
>> But travis build fails with
>> 
>> [WARNING] Error injecting:
>> org.apache.maven.plugins.checkstyle.CheckstyleViolationCheckMojo
>> java.lang.UnsupportedClassVersionError:
>> com/puppycrawl/tools/checkstyle/api/AuditListener : Unsupported major.minor
>> version 52.0
>> 
>> because checkstyle 7+ requires java 8.
>> 
>> —
>> You are receiving this because you authored the thread.
>> Reply to this email directly, view it on GitHub
>> ,
>> or mute the thread
>> 
>> .
>> 

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

[release-plugin][build-plugin] Java 8

[Gary Gregory]

I propose we make our release-plugin require Java 8. Newer dependencies
like the latest Checkstyle require Java 8.

Gary

Re: [apache/commons-release-plugin] Update Checkstyle 6.19 -> 8.10.1. OK: mvn clean site (13210c7)

[Gary Gregory]

It we should just make the plugin require Java 8.

Gary

On Wed, Jun 13, 2018 at 1:27 PM Pascal Schumacher 
wrote:

> But travis build fails with
>
> [WARNING] Error injecting:
> org.apache.maven.plugins.checkstyle.CheckstyleViolationCheckMojo
> java.lang.UnsupportedClassVersionError:
> com/puppycrawl/tools/checkstyle/api/AuditListener : Unsupported major.minor
> version 52.0
>
> because checkstyle 7+ requires java 8.
>
> —
> You are receiving this because you authored the thread.
> Reply to this email directly, view it on GitHub
> ,
> or mute the thread
> 
> .
>

[VOTE] Release Apache Commons DBCP 2.4.0 based on RC1

[Gary Gregory]

We have fixed quite a few bugs and added some significant enhancements
since Apache Commons DBCP 2.3.0 was released, so I would like to release
Apache Commons DBCP 2.4.0.

Apache Commons DBCP 2.4.0 RC1 is available for review here:
https://dist.apache.org/repos/dist/dev/commons/dbcp/2.4.0-RC1 (svn
revision 27438)

The Git tag commons-dbcp-2.4.0-RC1 commit for this RC is
d7aa662fbbb99e536ae28c47d0c4e1d51e39d5b9 which you can browse here:

https://git-wip-us.apache.org/repos/asf?p=commons-dbcp.git;a=tag;h=refs/tags/commons-dbcp-2.4.0-RC1

Maven artifacts are here:

https://repository.apache.org/content/repositories/orgapachecommons-1333/org/apache/commons/commons-dbcp2/2.4.0/

These are the Maven artifacts and their hashes in Nexus:

#Release SHA-1s
#Wed Jun 13 13:32:41 MDT 2018
commons-dbcp2-2.4.0-bin-tar.gz.asc=064e744553fddd0c8c45aeb998429546c773eefc
commons-dbcp2-2.4.0-src-zip=fb3157fa431b3dd059c8bed81c93f93160daba75
commons-dbcp2-2.4.0-javadoc-jar.asc=a2fbc96c6b8553b13b4f2ed653d9aa5717e89842
commons-dbcp2-2.4.0-test-sources-java-source=a8cb680bd20e46b548413ab4f3159a1b6af370fc
commons-dbcp2-2.4.0-test-sources-jar.asc=e073bc4700757d6b6d66a84989ba9f72b85fa2d4
commons-dbcp2-2.4.0-bin-zip.asc=74d108cbbbc0099f87d1536f92b59b5eb1b3657c
commons-dbcp2-2.4.0-bin-zip=fda0585ae3d6cdb64091ffac630806cf1f781e7f
commons-dbcp2-2.4.0-sources-java-source=f3a963f855209e9b4a18ea642a3a01adb95d8946
commons-dbcp2-2.4.0-src-tar.gz=fef764329584d12053c20e50ed628822f22d2728
commons-dbcp2-2.4.0-javadoc-javadoc=46cfd110cc0002c5f37bc6965e0149ec208ef458
commons-dbcp2-2.4.0-bin-tar.gz=382feff1078882750981b91d810117fefe590047
commons-dbcp2-2.4.0-src-tar.gz.asc=00d53b490f2631b2b7515e673cd6063c58c9b4fc
commons-dbcp2-2.4.0-src-zip.asc=7aeaba88bf4a7459e8f20515ba6f26886a0f9702
commons-dbcp2-2.4.0-null-pom.asc=df3fbc3dc6460cba003b16f8eba13ed3ffd8beef
commons-dbcp2-2.4.0-tests-jar.asc=51051e26c5eb6c76e4dbf9523e9c9f22be548343
commons-dbcp2-2.4.0-sources-jar.asc=b3a3467cf022728806eb2db63ca0c1fa76f9a5f4
commons-dbcp2-2.4.0-tests-test-jar=8546d77cf33dbe35145fbcbd4890f29a673b6e97
commons-dbcp2-2.4.0-null-jar.asc=3352f1b1ab04452445709d19272449bc5238d735

#Release SHA-256s
#Wed Jun 13 13:32:41 MDT 2018
commons-dbcp2-2.4.0-bin-tar.gz.asc=530eec11fd24e47a9ef0917f6b2e34f7d3eef7e83089b421fab907c54ebcec8d
commons-dbcp2-2.4.0-src-zip=eb1ee5760dd9e8875f2950297c20dee7307eff09e02a348c621cb5fad9d44a63
commons-dbcp2-2.4.0-javadoc-jar.asc=48c4e82ed05f6ba2c0aafcddc810ef5388c5ab063cd982bec0708fe0d09f75a8
commons-dbcp2-2.4.0-test-sources-java-source=da10f54b4705e706b57b372581b982bc1dcec21ee574864785c54c201fd0
commons-dbcp2-2.4.0-test-sources-jar.asc=7952567ebe6071ebc95bf9c50ad07f2fb0188876130b770d063bf81170657107
commons-dbcp2-2.4.0-bin-zip.asc=95aaa78797145eac624b03389c44a1e0f77c4babb53cf5b2cd436f342ae3a2da
commons-dbcp2-2.4.0-bin-zip=7f87a408dcfaf9ff94fbbd7c1fa6b21a071c0a61ca869c44e749a1fe579b6ca8
commons-dbcp2-2.4.0-sources-java-source=fd36da64513813e6c12a9f101ed6f8b7838834283893dd5654a76f4c39a9
commons-dbcp2-2.4.0-src-tar.gz=a9b305f623f8c45e6bb392aaf5c045248ff7f326aba69bc6db0869947179ce0e
commons-dbcp2-2.4.0-javadoc-javadoc=27ec0b63947ba5e3bdc5a7fdac592590ca74aa35ece35e5eacee73a5cfc61dce
commons-dbcp2-2.4.0-bin-tar.gz=7a88aca498cd1547e4e15f80ce7dfa89425a6a00c9fe93bbd6f94afee2150c4d
commons-dbcp2-2.4.0-src-tar.gz.asc=115344f789d33094b6d8e8be50562337dc9f62881105b61fedeca17f9b9c20e4
commons-dbcp2-2.4.0-src-zip.asc=2f9a10da8df8bb1d283afb3a7f6567fe1354c60fb97b4bce7766dff3041c1a64
commons-dbcp2-2.4.0-null-pom.asc=a841c9899ef5c341a26b2e4145f7c215c568e577a417d5641201a24686e33450
commons-dbcp2-2.4.0-tests-jar.asc=fbe62bf9d4c0d3db92bfa53215d640d5677f7403665ccdee8f0fab6f205e42fa
commons-dbcp2-2.4.0-sources-jar.asc=550a5fd3427da1aec9fe9c6bcb2935aaf4daf68f098dd2769cab4089cc373c48
commons-dbcp2-2.4.0-tests-test-jar=6f5f5114aa25905a88f2912e2c3425dbb97ae4a6c79daaf5ee5ed98a95dfaca7
commons-dbcp2-2.4.0-null-jar.asc=a8c4e8405ecc14b9aeba997c2886bfe740dd074333bd7164bc4489ce0470bf4b

I have tested this with ***'mvn clean install site'*** using:
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T12:49:05-07:00)
Maven home: C:\Java\apache-maven-3.5.3\bin\..
Java version: 1.8.0_172, vendor: Oracle Corporation
Java home: C:\Program Files\Java\jdk1.8.0_172\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"

Details of changes since 2.3.0 are in the release notes:

https://dist.apache.org/repos/dist/dev/commons/dbcp/2.4.0-RC1/RELEASE-NOTES.txt

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

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

CLIRR Report (compared to 2.3.0):

https://dist.apache.org/repos/dist/dev/commons/dbcp/2.4.0-RC1/site/clirr-report.html
There are no errors 

[GitHub] commons-collections issue #43: Javadoc fixes

[coveralls]

Github user coveralls commented on the issue:

https://github.com/apache/commons-collections/pull/43
  

[![Coverage 
Status](https://coveralls.io/builds/17475056/badge)](https://coveralls.io/builds/17475056)

Coverage increased (+0.007%) to 87.393% when pulling 
**5e44c8e3d79ec36235530a310d9181fd7f0ee4b2 on sfuhrm:JavadocFixes** into 
**8f9e66fbf060b219ca810e7b8d1153699e410237 on apache:master**.



---

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

[GitHub] commons-collections pull request #43: Javadoc fixes

[sfuhrm]

GitHub user sfuhrm opened a pull request:

https://github.com/apache/commons-collections/pull/43

Javadoc fixes

Multiple small Javadoc fixes for obvious mistakes

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sfuhrm/commons-collections JavadocFixes

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/commons-collections/pull/43.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #43


commit 5e44c8e3d79ec36235530a310d9181fd7f0ee4b2
Author: Stephan Fuhrmann 
Date:   2018-06-13T19:17:14Z

Javadoc fixes




---

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

Re: [release-plugin] fail on dist

[Gary Gregory]

On Wed, Jun 13, 2018 at 12:52 PM Rob Tompkins  wrote:

>
>
> > On Jun 13, 2018, at 2:21 PM, Gary Gregory 
> wrote:
> >
> > Hi Rob,
> >
> > I just tried to use the release plugin and I am getting this problem
> > (again?).
> >
> > Is there a workaround?
> >
> > mvn -Dcommons.release-plugin.version=1.3-SNAPSHOT -Prelease clean package
> > site deploy
>
> The main work around would be to cd into
> `target/commons-release-plugin/scm` and svn commit everything in there.
> This bug was a quick fix (which I’ll commit right now), but it lead to the
> following:
>
> The issue at hand here becomes that we’re committing files and not
> explicitly committing their parent directories before hand. I’ve been
> chipping away at writing code to do that, but am still working on it.
>

Thanks Rob.

Gary


>
>
> -Rob
>
> >
> > [INFO] --- commons-release-plugin:1.3-SNAPSHOT:stage-distributions
> > (stage-distributions) @ commons-dbcp2 ---
> > [INFO] Preparing to stage distributions
> > [INFO] Checking out dist from: scm:svn:
> > https://dist.apache.org/repos/dist/dev/commons/dbcp
> > Executing: cmd.exe /X /C "svn --username ggregory --no-auth-cache
> > --non-interactive checkout
> > https://dist.apache.org/repos/dist/dev/commons/dbcp
> > C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin\scm"
> > Working directory:
> > C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin
> > [INFO] Copying RELEASE-NOTES.txt to working directory.
> > Executing: cmd.exe /X /C "svn add --parents --non-recursive --targets
> >
> C:\Users\ggregory\AppData\Local\Temp\maven-scm-3697247083144163331-targets"
> > Working directory:
> > C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin\scm
> > [ERROR] Adding dist files failed: svn: E155007:
> > 'C:\vcs\git\apache\commons\commons-dbcp\target\site\apidocs' is not a
> > working copy
> >
> > [INFO]
> > 
> > [INFO] BUILD FAILURE
> > [INFO]
> > 
> > [INFO] Total time: 05:36 min
> > [INFO] Finished at: 2018-06-13T12:18:34-06:00
> > [INFO]
> > 
> > [ERROR] Failed to execute goal
> >
> org.apache.commons:commons-release-plugin:1.3-SNAPSHOT:stage-distributions
> > (stage-distributions) on project commons-dbcp2: Adding dist files failed:
> > svn: E155007:
> 'C:\vcs\git\apache\commons\commons-dbcp\target\site\apidocs'
> > is not a working copy
> > [ERROR]
> > [ERROR] -> [Help 1]
> > [ERROR]
> > [ERROR] To see the full stack trace of the errors, re-run Maven with the
> -e
> > switch.
> > [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> > [ERROR]
> > [ERROR] For more information about the errors and possible solutions,
> > please read the following articles:
> > [ERROR] [Help 1]
> > http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> >
> > Gary
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [release-plugin] fail on dist

[Rob Tompkins]

> On Jun 13, 2018, at 2:21 PM, Gary Gregory  wrote:
> 
> Hi Rob,
> 
> I just tried to use the release plugin and I am getting this problem
> (again?).
> 
> Is there a workaround?
> 
> mvn -Dcommons.release-plugin.version=1.3-SNAPSHOT -Prelease clean package
> site deploy

The main work around would be to cd into `target/commons-release-plugin/scm` 
and svn commit everything in there. This bug was a quick fix (which I’ll commit 
right now), but it lead to the following:

The issue at hand here becomes that we’re committing files and not explicitly 
committing their parent directories before hand. I’ve been chipping away at 
writing code to do that, but am still working on it.


-Rob

> 
> [INFO] --- commons-release-plugin:1.3-SNAPSHOT:stage-distributions
> (stage-distributions) @ commons-dbcp2 ---
> [INFO] Preparing to stage distributions
> [INFO] Checking out dist from: scm:svn:
> https://dist.apache.org/repos/dist/dev/commons/dbcp
> Executing: cmd.exe /X /C "svn --username ggregory --no-auth-cache
> --non-interactive checkout
> https://dist.apache.org/repos/dist/dev/commons/dbcp
> C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin\scm"
> Working directory:
> C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin
> [INFO] Copying RELEASE-NOTES.txt to working directory.
> Executing: cmd.exe /X /C "svn add --parents --non-recursive --targets
> C:\Users\ggregory\AppData\Local\Temp\maven-scm-3697247083144163331-targets"
> Working directory:
> C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin\scm
> [ERROR] Adding dist files failed: svn: E155007:
> 'C:\vcs\git\apache\commons\commons-dbcp\target\site\apidocs' is not a
> working copy
> 
> [INFO]
> 
> [INFO] BUILD FAILURE
> [INFO]
> 
> [INFO] Total time: 05:36 min
> [INFO] Finished at: 2018-06-13T12:18:34-06:00
> [INFO]
> 
> [ERROR] Failed to execute goal
> org.apache.commons:commons-release-plugin:1.3-SNAPSHOT:stage-distributions
> (stage-distributions) on project commons-dbcp2: Adding dist files failed:
> svn: E155007: 'C:\vcs\git\apache\commons\commons-dbcp\target\site\apidocs'
> is not a working copy
> [ERROR]
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
> 
> Gary


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

[release-plugin] fail on dist

[Gary Gregory]

Hi Rob,

I just tried to use the release plugin and I am getting this problem
(again?).

Is there a workaround?

mvn -Dcommons.release-plugin.version=1.3-SNAPSHOT -Prelease clean package
site deploy

[INFO] --- commons-release-plugin:1.3-SNAPSHOT:stage-distributions
(stage-distributions) @ commons-dbcp2 ---
[INFO] Preparing to stage distributions
[INFO] Checking out dist from: scm:svn:
https://dist.apache.org/repos/dist/dev/commons/dbcp
Executing: cmd.exe /X /C "svn --username ggregory --no-auth-cache
--non-interactive checkout
https://dist.apache.org/repos/dist/dev/commons/dbcp
C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin\scm"
Working directory:
C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin
[INFO] Copying RELEASE-NOTES.txt to working directory.
Executing: cmd.exe /X /C "svn add --parents --non-recursive --targets
C:\Users\ggregory\AppData\Local\Temp\maven-scm-3697247083144163331-targets"
Working directory:
C:\vcs\git\apache\commons\commons-dbcp\target\commons-release-plugin\scm
[ERROR] Adding dist files failed: svn: E155007:
'C:\vcs\git\apache\commons\commons-dbcp\target\site\apidocs' is not a
working copy

[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 05:36 min
[INFO] Finished at: 2018-06-13T12:18:34-06:00
[INFO]

[ERROR] Failed to execute goal
org.apache.commons:commons-release-plugin:1.3-SNAPSHOT:stage-distributions
(stage-distributions) on project commons-dbcp2: Adding dist files failed:
svn: E155007: 'C:\vcs\git\apache\commons\commons-dbcp\target\site\apidocs'
is not a working copy
[ERROR]
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException

Gary

[GitHub] commons-collections issue #42: Fix for 5 CheckStyle 3.0.0 plugin warnings.

[coveralls]

Github user coveralls commented on the issue:

https://github.com/apache/commons-collections/pull/42
  

[![Coverage 
Status](https://coveralls.io/builds/17473023/badge)](https://coveralls.io/builds/17473023)

Coverage remained the same at 87.386% when pulling 
**2a9a1105428fc37a1dea4b50baac3c5fce796b49 on sfuhrm:CheckStyleFixes** into 
**8f9e66fbf060b219ca810e7b8d1153699e410237 on apache:master**.



---

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

[GitHub] commons-collections pull request #42: Fix for 5 CheckStyle 3.0.0 plugin warn...

[sfuhrm]

GitHub user sfuhrm opened a pull request:

https://github.com/apache/commons-collections/pull/42

Fix for 5 CheckStyle 3.0.0 plugin warnings.

Fixed 5 CheckStyle warnings.

There are still 11 warnings left which are false positive (JavadocMethod
Unable to get class information for @throws tag 'FunctorException'.). 
See also: https://github.com/checkstyle/checkstyle/issues/5088

Maven Checkstyle Plugin 3.0.0 uses CheckStyle 6.18.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/sfuhrm/commons-collections CheckStyleFixes

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/commons-collections/pull/42.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #42


commit 2a9a1105428fc37a1dea4b50baac3c5fce796b49
Author: Stephan Fuhrmann 
Date:   2018-06-13T17:30:01Z

Fixed 5 CheckStyle 3.0.0 plugin warnings.




---

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

Re: commons-release-plugin git commit: (rat) update excludes for test artifacts

[Rob Tompkins]

Yeah…saw that. Thoughts on those? I don’t know if it matters or not, given that 
those artifacts are actually released artifacts.

-Rob

> On Jun 13, 2018, at 12:55 PM, Gary Gregory  wrote:
> 
> Almost ;-)
> 
> Files with unapproved licenses:
> 
> 
> src/test/resources/mojos/detach-distributions/target/commons-text-1.4-bin.tar.gz.asc
> 
> src/test/resources/mojos/detach-distributions/target/commons-text-1.4-bin.zip.asc
> 
> src/test/resources/mojos/detach-distributions/target/commons-text-1.4-javadoc.jar.asc
> 
> src/test/resources/mojos/detach-distributions/target/commons-text-1.4-sources.jar.asc
> 
> src/test/resources/mojos/detach-distributions/target/commons-text-1.4-src.tar.gz.asc
> 
> src/test/resources/mojos/detach-distributions/target/commons-text-1.4-src.zip.asc
> 
> src/test/resources/mojos/detach-distributions/target/commons-text-1.4-test-sources.jar.asc
> 
> src/test/resources/mojos/detach-distributions/target/commons-text-1.4-tests.jar.asc
> 
> src/test/resources/mojos/detach-distributions/target/commons-text-1.4.jar.asc
> 
> src/test/resources/mojos/detach-distributions/target/commons-text-1.4.pom.asc
> 
> Gary
> 
> On Wed, Jun 13, 2018 at 10:53 AM  wrote:
> 
>> Repository: commons-release-plugin
>> Updated Branches:
>>  refs/heads/master 1900a67fb -> d86ff62ce
>> 
>> 
>> (rat) update excludes for test artifacts
>> 
>> 
>> Project:
>> http://git-wip-us.apache.org/repos/asf/commons-release-plugin/repo
>> Commit:
>> http://git-wip-us.apache.org/repos/asf/commons-release-plugin/commit/d86ff62c
>> Tree:
>> http://git-wip-us.apache.org/repos/asf/commons-release-plugin/tree/d86ff62c
>> Diff:
>> http://git-wip-us.apache.org/repos/asf/commons-release-plugin/diff/d86ff62c
>> 
>> Branch: refs/heads/master
>> Commit: d86ff62ce4dcb2af0fa4b3e0fd8c2d23ba26a263
>> Parents: 1900a67
>> Author: Rob Tompkins 
>> Authored: Wed Jun 13 12:52:05 2018 -0400
>> Committer: Rob Tompkins 
>> Committed: Wed Jun 13 12:52:05 2018 -0400
>> 
>> --
>> pom.xml | 4 ++--
>> 1 file changed, 2 insertions(+), 2 deletions(-)
>> --
>> 
>> 
>> 
>> http://git-wip-us.apache.org/repos/asf/commons-release-plugin/blob/d86ff62c/pom.xml
>> --
>> diff --git a/pom.xml b/pom.xml
>> index 1e56a45..6e95e7f 100755
>> --- a/pom.xml
>> +++ b/pom.xml
>> @@ -242,8 +242,8 @@
>>   
>> 
>>   site-content/**
>> -  src/site/resources/download_lang.cgi
>> -
>> src/test/resources/stringEscapeUtilsTestData.txt
>> +
>> src/site/resources/download_commons-release-plugin.cgi
>> +
>> src/test/resources/mojos/detach-distributions/commons-text*
>> 
>> src/site/resources/release-notes/RELEASE-NOTES-*.txt
>> 
>>   
>> 
>> 


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

Re: commons-release-plugin git commit: (rat) update excludes for test artifacts

[Gary Gregory]

Almost ;-)

Files with unapproved licenses:


src/test/resources/mojos/detach-distributions/target/commons-text-1.4-bin.tar.gz.asc

src/test/resources/mojos/detach-distributions/target/commons-text-1.4-bin.zip.asc

src/test/resources/mojos/detach-distributions/target/commons-text-1.4-javadoc.jar.asc

src/test/resources/mojos/detach-distributions/target/commons-text-1.4-sources.jar.asc

src/test/resources/mojos/detach-distributions/target/commons-text-1.4-src.tar.gz.asc

src/test/resources/mojos/detach-distributions/target/commons-text-1.4-src.zip.asc

src/test/resources/mojos/detach-distributions/target/commons-text-1.4-test-sources.jar.asc

src/test/resources/mojos/detach-distributions/target/commons-text-1.4-tests.jar.asc

src/test/resources/mojos/detach-distributions/target/commons-text-1.4.jar.asc

src/test/resources/mojos/detach-distributions/target/commons-text-1.4.pom.asc

Gary

On Wed, Jun 13, 2018 at 10:53 AM  wrote:

> Repository: commons-release-plugin
> Updated Branches:
>   refs/heads/master 1900a67fb -> d86ff62ce
>
>
> (rat) update excludes for test artifacts
>
>
> Project:
> http://git-wip-us.apache.org/repos/asf/commons-release-plugin/repo
> Commit:
> http://git-wip-us.apache.org/repos/asf/commons-release-plugin/commit/d86ff62c
> Tree:
> http://git-wip-us.apache.org/repos/asf/commons-release-plugin/tree/d86ff62c
> Diff:
> http://git-wip-us.apache.org/repos/asf/commons-release-plugin/diff/d86ff62c
>
> Branch: refs/heads/master
> Commit: d86ff62ce4dcb2af0fa4b3e0fd8c2d23ba26a263
> Parents: 1900a67
> Author: Rob Tompkins 
> Authored: Wed Jun 13 12:52:05 2018 -0400
> Committer: Rob Tompkins 
> Committed: Wed Jun 13 12:52:05 2018 -0400
>
> --
>  pom.xml | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> --
>
>
>
> http://git-wip-us.apache.org/repos/asf/commons-release-plugin/blob/d86ff62c/pom.xml
> --
> diff --git a/pom.xml b/pom.xml
> index 1e56a45..6e95e7f 100755
> --- a/pom.xml
> +++ b/pom.xml
> @@ -242,8 +242,8 @@
>
>  
>site-content/**
> -  src/site/resources/download_lang.cgi
> -
> src/test/resources/stringEscapeUtilsTestData.txt
> +
> src/site/resources/download_commons-release-plugin.cgi
> +
> src/test/resources/mojos/detach-distributions/commons-text*
>
>  src/site/resources/release-notes/RELEASE-NOTES-*.txt
>  
>
>
>

Re: commons-release-plugin git commit: (fix) uniquely identify hashes in sha256 and sha1 artifact maps

[Rob Tompkins]

@Gary - I think this will fix the problem.

-ROb

> On Jun 13, 2018, at 12:39 PM, chtom...@apache.org wrote:
> 
> Repository: commons-release-plugin
> Updated Branches:
>  refs/heads/master 3b775f6f6 -> 812ea8f51
> 
> 
> (fix) uniquely identify hashes in sha256 and sha1 artifact maps
> 
> 
> Project: http://git-wip-us.apache.org/repos/asf/commons-release-plugin/repo
> Commit: 
> http://git-wip-us.apache.org/repos/asf/commons-release-plugin/commit/812ea8f5
> Tree: 
> http://git-wip-us.apache.org/repos/asf/commons-release-plugin/tree/812ea8f5
> Diff: 
> http://git-wip-us.apache.org/repos/asf/commons-release-plugin/diff/812ea8f5
> 
> Branch: refs/heads/master
> Commit: 812ea8f5150124756c991632ead795202e72197d
> Parents: 3b775f6
> Author: Rob Tompkins 
> Authored: Wed Jun 13 12:38:57 2018 -0400
> Committer: Rob Tompkins 
> Committed: Wed Jun 13 12:38:57 2018 -0400
> 
> --
> .../CommonsDistributionDetachmentMojo.java  |   7 +
> .../CommonsDistributionDetachmentMojoTest.java  |  62 ++-
> .../DistributionDetachmentProjectStub.java  | 200 ++---
> .../target/commons-text-1.4-bin.tar.gz  | Bin 0 -> 1812152 bytes
> .../target/commons-text-1.4-bin.tar.gz.asc  |  11 +
> .../target/commons-text-1.4-bin.zip | Bin 0 -> 2183252 bytes
> .../target/commons-text-1.4-bin.zip.asc |  11 +
> .../target/commons-text-1.4-javadoc.jar | Bin 0 -> 537451 bytes
> .../target/commons-text-1.4-javadoc.jar.asc |  16 +
> .../target/commons-text-1.4-sources.jar | Bin 0 -> 213808 bytes
> .../target/commons-text-1.4-sources.jar.asc |  16 +
> .../target/commons-text-1.4-src.tar.gz  | Bin 0 -> 273552 bytes
> .../target/commons-text-1.4-src.tar.gz.asc  |  11 +
> .../target/commons-text-1.4-src.zip | Bin 0 -> 434498 bytes
> .../target/commons-text-1.4-src.zip.asc |  11 +
> .../target/commons-text-1.4-test-sources.jar| Bin 0 -> 136486 bytes
> .../commons-text-1.4-test-sources.jar.asc   |  16 +
> .../target/commons-text-1.4-tests.jar   | Bin 0 -> 248578 bytes
> .../target/commons-text-1.4-tests.jar.asc   |  16 +
> .../target/commons-text-1.4.jar | Bin 0 -> 183750 bytes
> .../target/commons-text-1.4.jar.asc |  16 +
> .../target/commons-text-1.4.pom | 442 +++
> .../target/commons-text-1.4.pom.asc |  16 +
> .../target/mockAttachedFile.html|  24 -
> .../target/mockAttachedTar-bin.tar.gz   | Bin 327 -> 0 bytes
> .../target/mockAttachedTar-bin.tar.gz.asc   | Bin 566 -> 0 bytes
> .../target/mockAttachedTar-src.tar.gz   | Bin 327 -> 0 bytes
> .../target/mockAttachedTar-src.tar.gz.asc   | Bin 566 -> 0 bytes
> .../target/mockAttachedZip-bin.zip  | Bin 1323 -> 0 bytes
> .../target/mockAttachedZip-bin.zip.asc  | Bin 566 -> 0 bytes
> .../target/mockAttachedZip-src.zip  | Bin 1323 -> 0 bytes
> .../target/mockAttachedZip-src.zip.asc  | Bin 566 -> 0 bytes
> 32 files changed, 775 insertions(+), 100 deletions(-)
> --
> 
> 
> http://git-wip-us.apache.org/repos/asf/commons-release-plugin/blob/812ea8f5/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java
> --
> diff --git 
> a/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java
>  
> b/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java
> index fd5972d..9c95127 100755
> --- 
> a/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java
> +++ 
> b/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java
> @@ -163,6 +163,7 @@ public class CommonsDistributionDetachmentMojo extends 
> AbstractMojo {
> artifactKey
> .append(artifact.getArtifactId()).append('-')
> .append(artifact.getVersion()).append('-')
> +.append(artifact.getClassifier()).append('-')
> .append(artifact.getType());
> try (FileInputStream fis = new 
> FileInputStream(artifact.getFile())) {
> artifactSha1s.put(artifactKey.toString(), 
> DigestUtils.sha1Hex(fis));
> @@ -172,6 +173,8 @@ public class CommonsDistributionDetachmentMojo extends 
> AbstractMojo {
> "Could not find artifact signature for: "
> + artifact.getArtifactId()
> + "-"
> ++ artifact.getClassifier()
> ++ "-"
> + artifact.getVersion()
> + " type: "
> + artifact.getType(),
> @@ -191,6 +194,7 @@ public class CommonsDistributionDetachmentMojo extends 
> AbstractMojo {
> 

Re: [release-plugin] No longer publish MD5 files to Apache's dev and release folders.

[Rob Tompkins]

It seems that this does not carry sufficient specificity for uniquely 
identifying the artifact:
https://github.com/apache/commons-release-plugin/blob/master/src/main/java/org/apache/commons/release/plugin/mojos/CommonsDistributionDetachmentMojo.java#L164-L166
 

I’ll fix that now.

-Rob

> On Jun 13, 2018, at 11:48 AM, Gary Gregory  wrote:
> 
> Note that I fixed the SHA-1 and SHA-256 files in SVN.
> 
> Gary
> 
> On Wed, Jun 13, 2018 at 9:45 AM Rob Tompkins  wrote:
> 
>> We don’t create the .md5 files that reside in nexus, it does when the
>> build get’s pushed up. So no concern there. Regarding the signatures, those
>> seem to be the ones from the -src artifacts. Reading more closely to see
>> where that happened. Thinking about checking in text-1.4 to the unit tests
>> and using those artifacts as our unit testing mechanism.
>> 
>> -Rob
>> 
>>> On Jun 13, 2018, at 11:39 AM, Gary Gregory 
>> wrote:
>>> 
>>> Rob,
>>> 
>>> While Nexus still uses MD5 files, we should no longer publish MD5 files
>> to
>>> Apache's dev and release folders. I manually deleted the ones for Commons
>>> Text just now, which leaves us with SHA-1 and SHA-256.
>>> 
>>> Gary
>> 
>> 
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>> 
>> 

Re: [release-plugin] No longer publish MD5 files to Apache's dev and release folders.

[Gary Gregory]

Note that I fixed the SHA-1 and SHA-256 files in SVN.

Gary

On Wed, Jun 13, 2018 at 9:45 AM Rob Tompkins  wrote:

> We don’t create the .md5 files that reside in nexus, it does when the
> build get’s pushed up. So no concern there. Regarding the signatures, those
> seem to be the ones from the -src artifacts. Reading more closely to see
> where that happened. Thinking about checking in text-1.4 to the unit tests
> and using those artifacts as our unit testing mechanism.
>
> -Rob
>
> > On Jun 13, 2018, at 11:39 AM, Gary Gregory 
> wrote:
> >
> > Rob,
> >
> > While Nexus still uses MD5 files, we should no longer publish MD5 files
> to
> > Apache's dev and release folders. I manually deleted the ones for Commons
> > Text just now, which leaves us with SHA-1 and SHA-256.
> >
> > Gary
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [release-plugin] No longer publish MD5 files to Apache's dev and release folders.

[Rob Tompkins]

We don’t create the .md5 files that reside in nexus, it does when the build 
get’s pushed up. So no concern there. Regarding the signatures, those seem to 
be the ones from the -src artifacts. Reading more closely to see where that 
happened. Thinking about checking in text-1.4 to the unit tests and using those 
artifacts as our unit testing mechanism.

-Rob

> On Jun 13, 2018, at 11:39 AM, Gary Gregory  wrote:
> 
> Rob,
> 
> While Nexus still uses MD5 files, we should no longer publish MD5 files to
> Apache's dev and release folders. I manually deleted the ones for Commons
> Text just now, which leaves us with SHA-1 and SHA-256.
> 
> Gary


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

[release-plugin] No longer publish MD5 files to Apache's dev and release folders.

[Gary Gregory]

Rob,

While Nexus still uses MD5 files, we should no longer publish MD5 files to
Apache's dev and release folders. I manually deleted the ones for Commons
Text just now, which leaves us with SHA-1 and SHA-256.

Gary

Re: svn commit: r27426 - /dev/commons/lang/3.8-SNAPSHOT-RC1/site/

[Rob Tompkins]

Correct, I’m testing the release plugin adding the directories first before any 
of the sub-files. I think I’m getting weird parent-child commit failures in the 
svn mechanics.

> On Jun 13, 2018, at 11:19 AM, Gary Gregory  wrote:
> 
> Hi Rob,
> 
> Shouldn't the release plugin should do that? After a release, I usually
> just blow away the whole dev folder, sub-folders and all.
> 
> Gary
> 
> On Wed, Jun 13, 2018 at 9:16 AM  wrote:
> 
>> Author: chtompki
>> Date: Wed Jun 13 15:16:41 2018
>> New Revision: 27426
>> 
>> Log:
>> Adding release directories: commons-lang3, version: 3.8-SNAPSHOT
>> 
>> Added:
>>dev/commons/lang/3.8-SNAPSHOT-RC1/site/
>> 
>> 


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

Re: svn commit: r27427 - /dev/commons/lang/3.8-SNAPSHOT-RC1/site/apidocs/

[Rob Tompkins]

Agreed, that what I’m testing with to distinguish it from a real release 
staging event.

> On Jun 13, 2018, at 11:20 AM, Gary Gregory  wrote:
> 
> We should not have a "-SNAPSHOT" in the folder names for RCs I do not think.
> 
> Gary
> 
> On Wed, Jun 13, 2018 at 9:16 AM  wrote:
> 
>> Author: chtompki
>> Date: Wed Jun 13 15:16:43 2018
>> New Revision: 27427
>> 
>> Log:
>> Adding release directories: commons-lang3, version: 3.8-SNAPSHOT
>> 
>> Added:
>>dev/commons/lang/3.8-SNAPSHOT-RC1/site/apidocs/
>> 
>> 


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

Re: svn commit: r27427 - /dev/commons/lang/3.8-SNAPSHOT-RC1/site/apidocs/

[Gary Gregory]

We should not have a "-SNAPSHOT" in the folder names for RCs I do not think.

Gary

On Wed, Jun 13, 2018 at 9:16 AM  wrote:

> Author: chtompki
> Date: Wed Jun 13 15:16:43 2018
> New Revision: 27427
>
> Log:
> Adding release directories: commons-lang3, version: 3.8-SNAPSHOT
>
> Added:
> dev/commons/lang/3.8-SNAPSHOT-RC1/site/apidocs/
>
>

Re: svn commit: r27426 - /dev/commons/lang/3.8-SNAPSHOT-RC1/site/

[Gary Gregory]

Hi Rob,

Shouldn't the release plugin should do that? After a release, I usually
just blow away the whole dev folder, sub-folders and all.

Gary

On Wed, Jun 13, 2018 at 9:16 AM  wrote:

> Author: chtompki
> Date: Wed Jun 13 15:16:41 2018
> New Revision: 27426
>
> Log:
> Adding release directories: commons-lang3, version: 3.8-SNAPSHOT
>
> Added:
> dev/commons/lang/3.8-SNAPSHOT-RC1/site/
>
>

Re: svn commit: r27427 - /dev/commons/lang/3.8-SNAPSHOT-RC1/site/apidocs/

[Rob Tompkins]

Been debugging committing everything for a few days now. Pardon if there are 
commits that periodically happen.

> On Jun 13, 2018, at 11:16 AM, chtom...@apache.org wrote:
> 
> Author: chtompki
> Date: Wed Jun 13 15:16:43 2018
> New Revision: 27427
> 
> Log:
> Adding release directories: commons-lang3, version: 3.8-SNAPSHOT
> 
> Added:
>dev/commons/lang/3.8-SNAPSHOT-RC1/site/apidocs/
> 


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

[REPORT] Apache Commons June 2018

[Gary Gregory]

## Description:
 - Apache Commons is an Apache project focused on all aspects of reusable
Java components.

## Issues:
 - There are no issues requiring board attention at this time.

## Activity:
 - Activity is medium with the release of 4 components and 4 internal
components.

## Health report:
 - The project is moderately healthy but suffers from a lack of committer
and PMC growth.
 - Releases for existing components are in the planning stage for
Collections, Lang, IO, Pool, DBCP, RNG, Numbers, and Weaver (for Apache
BVal 2.0.)
 - We are discussing the addition of a new component, mailing activity is
good and JIRAs are addressed in a timely manner.

## PMC changes:

 - Currently 38 PMC members.
 - No new PMC members added in the last 3 months
 - Last PMC addition was Rob Tompkins on Fri Jun 30 2017

## Committer base changes:

 - Currently 146 committers.
 - No new committers added in the last 3 months
 - Last committer addition was Sergio Fernández at Sat Nov 04 2017

## Releases:

 - BUILDPLUGIN-1.8 was released on Wed Apr 04 2018
 - COMPRESS-1.17 was released on Sat Jun 02 2018
 - DBCP-2.3.0 was released on Fri May 11 2018
 - PARENT-45 was released on Wed Mar 14 2018
 - PARENT-46 was released on Sun Apr 15 2018
 - RELEASEPLUGIN-1.2 was released on Wed Apr 04 2018
 - TEXT-1.3 was released on Tue Mar 20 2018
 - TEXT-1.4 was released on Mon Jun 11 2018

## JIRA activity:

 - 170 JIRA tickets created in the last 3 months
 - 133 JIRA tickets closed/resolved in the last 3 months

## Odds and ends:

- Incomplete stats from https://demo.kibble.apache.org:
- 1,570 Commits this period
- 72 Authors this period
- 204,475 Lines changed this period
- 40 Committers this period

Gary Gregory
Apache Commons PMC Chair.

Re: [ALL][DRAFT] Board report

[Matt Benson]

Fwiw, [weaver] will also be released in the near future, and will be
reported as being the primary remaining blocker for Apache BVal 2.0.

Matt

On Wed, Jun 13, 2018, 12:27 AM Gilles  wrote:

> Hello.
>
> On Tue, 12 Jun 2018 16:11:30 -0600, Gary Gregory wrote:
> > Thank you for your review Gilles (more below.)
> >
> > On Tue, Jun 12, 2018 at 3:50 PM Gilles 
> > wrote:
> >
> >> Hi.
> >>
> >> On Tue, 12 Jun 2018 12:53:52 -0600, Gary Gregory wrote:
> >> > I plan on sending this tomorrow at the latest:
> >> >
> >> > ## Description:
> >> >  - Apache Commons is an Apache project focused on all aspects of
> >> > reusable
> >> > Java components.
> >> >
> >> > ## Issues:
> >> >  - There are no issues requiring board attention at this time.
> >> >
> >> > ## Activity:
> >> >  - Activity is medium with the release of 4 components and 4
> >> internal
> >> > components.
> >> >
> >> > ## Health report:
> >> >  - The project is healthy. We are discussing the addition of a new
> >> > component,
> >>
> >> Which one?
> >>
> >
> > The board does not care I am sure. I am going for short and sweet
> > here but
> > I think we had talked about a timing component and someone pointed
> > out that
> > there was an old entire project at Apache that basically already did
> > that
> > but that it was also dead or dormant.
> >
> >
> >>
> >> > mailing activity is good and JIRAs are addressed in a timely
> >> > manner.
> >> >  - Releases for existing components are in the planning stage
> >> > (Collections,
> >> > Lang, IO, Pool, DBCP.)
> >>
> >> RNG (if the next CP fixes the "japicmp" issue)
> >> Numbers (if it gets reviews from people other than me)
> >>
> >
> > I will add those but I am sure the board does not care so we could
> > also
> > omit the list.
> >
> >
> >>
> >> >
> >> > ## PMC changes:
> >> >
> >> >  - Currently 38 PMC members.
> >>
> >> This is highly not representative of the project's activity.
> >> It would be more meaningful to report active members.
> >>
> >> >  - No new PMC members added in the last 3 months
> >>
> >> This is representative.
> >>
> >
> > I just shows lack of growth.
> >
> >
> >>
> >> >  - Last PMC addition was Rob Tompkins on Fri Jun 30 2017
> >> >
> >> > ## Committer base changes:
> >> >
> >> >  - Currently 146 committers.
> >>
> >> All Apache committers are Commmons committers; so what?
> >> It would be (much) more meaningful to provide the number
> >> of people who made a commit in the last 3 months...
> >> Something like: "x committers changed y lines of code
> >> over z commits."[1]
> >
> >
> > Feel free to provide such stats ;-) But we all know how valuable LOC
> > stats
> > are... While those [1] numbers are fun, they tell you nothing of the
> > kind
> > of changes...
>
> 1,570
> Commits this period
>
> 72
> Authors this period
>
> 204,475
> Lines changed this period
>
> 40
> Committers this period
>
>
> Those numbers are not totally accurate: "kibble"[1] is missing
> the latest repositories (it would add a few lines and commits
> but no authors or committers AFAICT).
>
> >>
> >> >  - No new committers added in the last 3 months
> >>
> >> IMHO, this does not fit with the "healthy" qualifier.
> >>
> >
> > Hm, perhaps 'moderately healthy and not currently growing' is more
> > accurate
> > though.
>
> Don't you think there is a trend (not just "currently")?
> Isn't it a sign that the number of people interested in
> the latest developments is declining?
> For "common" code, isn't this something to worry about?
>
> Regards,
> Gilles
>
> >
> > Gary
>
> [1] https://demo.kibble.apache.org
>
> >
> >
> >> >  - Last committer addition was Sergio Fernández at Sat Nov 04 2017
> >> >
> >> > ## Releases:
> >> >
> >> >  - BUILDPLUGIN-1.8 was released on Wed Apr 04 2018
> >> >  - COMPRESS-1.17 was released on Sat Jun 02 2018
> >> >  - DBCP-2.3.0 was released on Fri May 11 2018
> >> >  - PARENT-45 was released on Wed Mar 14 2018
> >> >  - PARENT-46 was released on Sun Apr 15 2018
> >> >  - RELEASEPLUGIN-1.2 was released on Wed Apr 04 2018
> >> >  - TEXT-1.3 was released on Tue Mar 20 2018
> >> >  - TEXT-1.4 was released on Mon Jun 11 2018
> >> >
> >> > ## JIRA activity:
> >> >
> >> >  - 170 JIRA tickets created in the last 3 months
> >> >  - 133 JIRA tickets closed/resolved in the last 3 months
> >> >
> >> > Gary Gregory,
> >> > Apache Commons PMC Chair.
> >>
> >> Regards,
> >> Gilles
> >>
> >> [1] https://blogs.apache.org/foundation/entry/apache-in-2017-by-the
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>