Re: [VOTE] Release Apache Commons Weaver 1.3 based on RC2

[sebb]

On 13 October 2016 at 22:30, Matt Benson  wrote:
> I would like to release the [weaver] component.
>
> Apache Commons Weaver 1.3 RC2 is available for review at:
>   https://dist.apache.org/repos/dist/dev/commons/weaver/ (r16517).
>
> Maven artifacts are at:
>   https://repository.apache.org/content/repositories/orgapachecommons-1210 .
>
> Tested with Oracle JDKs 6, 7 and 8; IBM JDKs 6 and 7.
>
> The Subversion tag is:
>   http://svn.apache.org/repos/asf/commons/proper/weaver/tags/1.3_RC2
>  (r1764791).
>
> Site (note some links may be broken; this will be fixed when the site
> is deployed):
>   http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/index.html

The download page has not been updated with the new versions:

http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/download_weaver.html

It still shows 1.2

The download file needs to be regenerated and committed, and the site rebuilt.

> RAT Report:
>   http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/rat-report.html
>
> Quality Reports (PMD/Checkstyle/Findbugs/japicmp):
>
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-processor/project-reports.html
>
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer-api/project-reports.html
>
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer/project-reports.html
>
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-normalizer/project-reports.html
>
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-maven-plugin/project-reports.html
>
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-antlib/project-reports.html
>
> Note that compatibility (japicmp) reports have only been produced for
> artifacts that could conceivably be used programmatically by downstream
> users: namely, *not* weaver modules.
>
> The only change from RC1 to RC2 has been the regeneration of the release
> notes.
>
> Keys: https://dist.apache.org/repos/dist/release/commons/KEYS
>
> Please review the release candidate and vote.
>   This vote will close no sooner than 72 hours from now, i.e. after
> 2130UTC 16-October 2016
>
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
>
>   Thanks!

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

Re: [VOTE] Release Apache Commons Lang 3.5 based on RC2

[Rob Tompkins]

+1 (non-binding)
Note that here:

https://github.com/apache/commons-lang/commit/6d8b64945160eb0f9f3b626730348f066585a913

the date on line 48 of chanes.xml is 2014. That might be overly nitpicky,
but I wanted to make not of it.

-Rob

On Fri, Oct 14, 2016 at 4:18 AM, Bruno P. Kinoshita <
brunodepau...@yahoo.com.br.invalid> wrote:

> +1 (not binding)
>
> Build works fine with Java 8;
>
> java version "1.8.0_101"
> Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)
>
> on Ubuntu 16.04 64 bits;
>
> Linux local 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016
> x86_64 x86_64 x86_64 GNU/Linux
>
>
> On locale en_NZ.UTF-8, time zone Pacific/Auckland. And Maven 3.3.9
>
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
> 2015-11-11T05:41:47+13:00)
> Maven home: /opt/maven
> Java version: 1.8.0_101, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-oracle/jre
> Default locale: en_NZ, platform encoding: UTF-8
> OS name: "linux", version: "4.4.0-38-generic", arch: "amd64", family:
> "unix"
> All tests pass, site successfully generated. Coverage about the same.
>
>
> Less issues in CPD, PMD, and Checkstyle; with no new issues added in the
> 3.5 release for these reports.
>
> On FindBugs, 3.5 got +1 warning, for an IOException that is being ignored
> in SerializationUtils#deserialize, but not a blocker IMO.
>
> The changes report is showing the release date as 2014-10-13, but I assume
> it is fixed during the release process?
>
> Keys OK. All good, kudos all!
>
> Bruno
> >
> > From: Benedikt Ritter 
> >To: Commons Developers List 
> >Sent: Friday, 14 October 2016 9:20 AM
> >Subject: [VOTE] Release Apache Commons Lang 3.5 based on RC2
> >
> >
> >Hi,
> >
> >finally I found the time to prepare Apache Commons Lang 3.5 RC2 :-)
> >We could not release RC1, because I messed up the release archives. They
> >contained some snapshot artifacts. This has been fixed in RC2. Furthermore
> >LANG-1275 has been incorporated.
> >
> >Lang 3.5 RC2 is available for review here:
> >  https://dist.apache.org/repos/dist/dev/commons/lang/LANG_3_5_RC2 (svn
> >revision 16505)
> >
> >Tag name:
> >   LANG_3_5_RC2 (signature can be checked from git using 'git tag -v')
> >
> >Tag URL:
> >
> >https://git-wip-us.apache.org/repos/asf?p=commons-lang.git;a=commit;h=
> 36f98d87b24c2f542b02abbf6ec1ee742f1b158b
> >
> >Commit ID the tag points at:
> >   36f98d87b24c2f542b02abbf6ec1ee742f1b158b
> >
> >Maven artifacts are here:
> >  https://repository.apache.org/content/repositories/
> orgapachecommons-1209
> >
> >These are the Maven artifacts and their hashes:
> >
> >commons-lang3-3.5-javadoc.jar
> >(SHA1: 337310e98410d577aca675930bb46405a0a8fb0c)
> >commons-lang3-3.5-sources.jar
> >(SHA1: f7d878153e86a1cdddf6b37850e00a9f8bff726f)
> >commons-lang3-3.5-test-sources.jar
> >(SHA1: dfb8a086a03cc9499cff808733fac667f5f50688)
> >commons-lang3-3.5-tests.jar
> >(SHA1: 8ca309192f104265c67a1570245ae827a8650af9)
> >commons-lang3-3.5.jar
> >(SHA1: 6c6c702c89bfff3cd9e80b04d668c5e190d588c6)
> >commons-lang3-3.5.pom
> >(SHA1: 08b969f02dfa03fa493fd6eba4cb9dcceea5aefd)
> >
> >I've tested with JDK 1.6 using Maven 3.2.5 and Java 7, 8 and Java 9 EA
> >using Maven 3.2.5.
> >Note that there are some problems when building on Java 9. We're currently
> >investigating this, see https://issues.apache.org/jira/browse/LANG-1265
> >To build on Java 9 you need to explicitly set the local provide to JRE:
> >
> >  mvn -Djava.locale.providers=JRE clean test
> >
> >Details of changes since 3.4 are in the release notes:
> >
> >https://dist.apache.org/repos/dist/dev/commons/lang/
> LANG_3_5_RC2/RELEASE-NOTES.txt
> >  http://home.apache.org/~britter/commons/lang/3_5_RC2/
> changes-report.html
> >
> >Site:
> >  http://home.apache.org/~britter/commons/lang/3_5_RC2
> >
> >Clirr Report (compared to 3.4):
> >  http://home.apache.org/~britter/commons/lang/3_5_RC2/clirr-report.html
> >(sorry, I messed up the site build and had to add the Clirr report
> >manually...)
> >
> >Note that Clirr reports several errors due to additions in the interface
> >org.apache.commons.lang3.time.DatePrinter
> >These are considered okay, since the DatePrinter interface is not meant to
> >be implemented by clients. This change is documented in the release notes.
> >
> >RAT report:
> >  http://home.apache.org/~britter/commons/lang/3_5_RC2/rat-report.html
> >
> >KEYS:
> >  https://www.apache.org/dist/commons/KEYS
> >
> >Please review the release candidate and vote.
> >This vote will close no sooner than 72 hours from now,
> >i.e. sometime after 22:30 UTC+2 16-October 2016.
> >
> >[ ] +1 Release these artifacts
> >[ ] +0 Okay, but...
> >[ ] -0 Okay, but really should fix...
> >[ ] -1 I oppose this release because...
> >
> >Thank you,
> >Benedikt
> >
> >
> >
>
> -
> To unsubscribe, 

Re: [VOTE] Release Apache Commons Weaver 1.3 based on RC2

[Romain Manni-Bucau]

+1, thanks Matt


Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Wordpress Blog
 | Github  |
LinkedIn  | Tomitriber
 | JavaEE Factory


2016-10-14 17:44 GMT+02:00 Oliver Heger :

> Build worked for me with Java 1.6 and 1.8 on Windows 10. The site build
> failed with Java 1.8, but was successful with 1.7 (following the build
> instructions).
>
> Artifacts and site look good.
>
> +1
>
> Minor nit: The OSGi meta data is problematic because all bundles have
> the same symbolic name. But I guess, this is not relevant for the
> intended use case.
>
> Oliver
>
> Am 13.10.2016 um 23:30 schrieb Matt Benson:
> > I would like to release the [weaver] component.
> >
> > Apache Commons Weaver 1.3 RC2 is available for review at:
> >   https://dist.apache.org/repos/dist/dev/commons/weaver/ (r16517).
> >
> > Maven artifacts are at:
> >   https://repository.apache.org/content/repositories/
> orgapachecommons-1210 .
> >
> > Tested with Oracle JDKs 6, 7 and 8; IBM JDKs 6 and 7.
> >
> > The Subversion tag is:
> >   http://svn.apache.org/repos/asf/commons/proper/weaver/tags/1.3_RC2
> >  (r1764791).
> >
> > Site (note some links may be broken; this will be fixed when the site
> > is deployed):
> >   http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/index.html
> >
> > RAT Report:
> >   http://people.apache.org/~mbenson/commons-weaver-1.3-
> rc2/rat-report.html
> >
> > Quality Reports (PMD/Checkstyle/Findbugs/japicmp):
> >
> > http://people.apache.org/~mbenson/commons-weaver-1.3-
> rc2/commons-weaver-parent/commons-weaver-processor/project-reports.html
> >
> > http://people.apache.org/~mbenson/commons-weaver-1.3-
> rc2/commons-weaver-parent/commons-weaver-modules-parent/
> commons-weaver-privilizer-parent/commons-weaver-privilizer-api/project-
> reports.html
> >
> > http://people.apache.org/~mbenson/commons-weaver-1.3-
> rc2/commons-weaver-parent/commons-weaver-modules-parent/
> commons-weaver-privilizer-parent/commons-weaver-
> privilizer/project-reports.html
> >
> > http://people.apache.org/~mbenson/commons-weaver-1.3-
> rc2/commons-weaver-parent/commons-weaver-modules-parent/
> commons-weaver-normalizer/project-reports.html
> >
> > http://people.apache.org/~mbenson/commons-weaver-1.3-
> rc2/commons-weaver-parent/commons-weaver-maven-plugin/project-reports.html
> >
> > http://people.apache.org/~mbenson/commons-weaver-1.3-
> rc2/commons-weaver-parent/commons-weaver-antlib/project-reports.html
> >
> > Note that compatibility (japicmp) reports have only been produced for
> > artifacts that could conceivably be used programmatically by downstream
> > users: namely, *not* weaver modules.
> >
> > The only change from RC1 to RC2 has been the regeneration of the release
> > notes.
> >
> > Keys: https://dist.apache.org/repos/dist/release/commons/KEYS
> >
> > Please review the release candidate and vote.
> >   This vote will close no sooner than 72 hours from now, i.e. after
> > 2130UTC 16-October 2016
> >
> >   [ ] +1 Release these artifacts
> >   [ ] +0 OK, but...
> >   [ ] -0 OK, but really should fix...
> >   [ ] -1 I oppose this release because...
> >
> >   Thanks!
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [VOTE] Release Apache Commons Weaver 1.3 based on RC2

[Oliver Heger]

Build worked for me with Java 1.6 and 1.8 on Windows 10. The site build
failed with Java 1.8, but was successful with 1.7 (following the build
instructions).

Artifacts and site look good.

+1

Minor nit: The OSGi meta data is problematic because all bundles have
the same symbolic name. But I guess, this is not relevant for the
intended use case.

Oliver

Am 13.10.2016 um 23:30 schrieb Matt Benson:
> I would like to release the [weaver] component.
> 
> Apache Commons Weaver 1.3 RC2 is available for review at:
>   https://dist.apache.org/repos/dist/dev/commons/weaver/ (r16517).
> 
> Maven artifacts are at:
>   https://repository.apache.org/content/repositories/orgapachecommons-1210 .
> 
> Tested with Oracle JDKs 6, 7 and 8; IBM JDKs 6 and 7.
> 
> The Subversion tag is:
>   http://svn.apache.org/repos/asf/commons/proper/weaver/tags/1.3_RC2
>  (r1764791).
> 
> Site (note some links may be broken; this will be fixed when the site
> is deployed):
>   http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/index.html
> 
> RAT Report:
>   http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/rat-report.html
> 
> Quality Reports (PMD/Checkstyle/Findbugs/japicmp):
> 
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-processor/project-reports.html
> 
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer-api/project-reports.html
> 
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer/project-reports.html
> 
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-normalizer/project-reports.html
> 
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-maven-plugin/project-reports.html
> 
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-antlib/project-reports.html
> 
> Note that compatibility (japicmp) reports have only been produced for
> artifacts that could conceivably be used programmatically by downstream
> users: namely, *not* weaver modules.
> 
> The only change from RC1 to RC2 has been the regeneration of the release
> notes.
> 
> Keys: https://dist.apache.org/repos/dist/release/commons/KEYS
> 
> Please review the release candidate and vote.
>   This vote will close no sooner than 72 hours from now, i.e. after
> 2130UTC 16-October 2016
> 
>   [ ] +1 Release these artifacts
>   [ ] +0 OK, but...
>   [ ] -0 OK, but really should fix...
>   [ ] -1 I oppose this release because...
> 
>   Thanks!
> 

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

Re: [logging] Is Apache Commons Logging still alive?

[Matt Sicker]

Seconded on Log4j 2. It provides an API that is also compatible with other
logging implementations besides Log4j 2, so you are not locked into using
it.

On 14 October 2016 at 03:30, Gary Gregory  wrote:

> Apache Log4j 2 is the preferred migration path IMO.
>
> Log4j 2 provides a clean separation between API and implementation and a
> ton of powerful features. Version 2.7 was just released.
>
> Gary
>
> On Fri, Oct 14, 2016 at 12:14 AM, Christian Effertz <
> christian.effe...@web.de> wrote:
>
> > Hello,
> >
> > we support several applications that rely on Apache Commons Logging and
> > Log4j as implementation. After some years we got the budget to polish
> them.
> > So we are currently considering how to update the logging framework those
> > applications use. Log4j apparently received an update in recent time,
> > whereas Commons Logging is unchanged since 2014.
> >
> > So we are wondering if it would be a good idea to (a) propose pull
> requests
> > via GitHub or (b) to migrate away from Commons Logging.
> >
> > Probably option (b) is the wiser choice as there has been a similar
> > discussion in the related Jira Project,
> > https://issues.apache.org/jira/browse/LOGGING-136.
> >
> > Any official or unofficial comments and thoughts on this topic?
> >
> > Regards
> > Christian Effertz
> >
>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
>  tl?ie=UTF8=1789=9325=1617290459&
> linkCode=as2=garygregory-20=cadb800f39946ec62ea2b1af9fe6a2b8>
>
>  1617290459>
> JUnit in Action, Second Edition
>  tl?ie=UTF8=1789=9325=1935182021&
> linkCode=as2=garygregory-20=31ecd1f6b6d1eaf8886ac902a24de418%22
> >
>
>  1935182021>
> Spring Batch in Action
>  tl?ie=UTF8=1789=9325=1935182951&
> linkCode=%7B%7BlinkCode%7D%7D=garygregory-20=%7B%
> 7Blink_id%7D%7D%22%3ESpring+Batch+in+Action>
>  1935182951>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>



-- 
Matt Sicker 

Re: [VOTE] Release Apache Commons Weaver 1.3 based on RC2

[Matt Benson]

The site is generated with Java 7. I thought the building instructions
mentioned this but I may have accidentally deleted the Java 8 caveat as
part of the obsolete information about clirr. The mention of permgen
implies pre-8 Java.

Matt

On Oct 14, 2016 4:07 AM, "Bruno P. Kinoshita"
 wrote:

Hi Matt,

Did you generate the site with Java 8? I tried:

`mvn clean test install`

`mvn site:site`

In the parent project, but the site generation stopped while creating the
Javadocs.

I'm using Java 8, with Maven 3.3.9.

--x snip x--

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.4:site
(default-cli) on project commons-weaver-base: Error generating
maven-javadoc-plugin:2.10.4:javadoc:
[ERROR] Exit code: 1 - /home/kinow/Development/java/apache/1.3_RC2/modules/
privilizer/weaver/src/main/java/org/apache/commons/
weaver/privilizer/package-info.java:20: warning: a package-info.java file
has already been seen for package org.apache.commons.weaver.privilizer
[ERROR] package org.apache.commons.weaver.privilizer;
[ERROR] ^
[ERROR] javadoc: warning - Multiple sources of package comments found for
package "org.apache.commons.weaver.privilizer"
[ERROR] /home/kinow/Development/java/apache/1.3_RC2/processor/src/
main/java/org/apache/commons/weaver/Consumes.java:42: warning: no @return
[ERROR] Class>[] value();
[ERROR] ^
[ERROR] /home/kinow/Development/java/apache/1.3_RC2/processor/src/
main/java/org/apache/commons/weaver/Produces.java:42: warning: no @return
[ERROR] Class>[] value();
[ERROR] ^
[ERROR] /home/kinow/Development/java/apache/1.3_RC2/processor/src/
main/java/org/apache/commons/weaver/lifecycle/WeaveLifecycleToken.java:43:
warning: no @return
[ERROR] WeaveLifecycle value();
[ERROR] ^
[ERROR] /home/kinow/Development/java/apache/1.3_RC2/ant/src/main/
java/org/apache/commons/weaver/ant/WeaverSettings.java:113: error: unknown
tag: String
[ERROR] * @return List
[ERROR] ^
[ERROR] /home/kinow/Development/java/apache/1.3_RC2/modules/
privilizer/weaver/src/main/java/org/apache/commons/
weaver/privilizer/Privilized.java:32: warning: no @return
[ERROR] String value();
[ERROR] ^
[ERROR] /home/kinow/Development/java/apache/1.3_RC2/modules/
privilizer/api/src/main/java/org/apache/commons/weaver/
privilizer/Privilizing.java:49: warning: no @return
[ERROR] CallTo[] value();
[ERROR] ^
[ERROR] /home/kinow/Development/java/apache/1.3_RC2/modules/
privilizer/api/src/main/java/org/apache/commons/weaver/
privilizer/Privilizing.java:38: warning: no @return
[ERROR] Class value();
[ERROR] ^
[ERROR] /home/kinow/Development/java/apache/1.3_RC2/modules/
privilizer/api/src/main/java/org/apache/commons/weaver/
privilizer/Privilizing.java:43: warning: no @return
[ERROR] String[] methods() default { };
[ERROR] ^
[ERROR]
[ERROR] Command line was: /usr/lib/jvm/java-8-oracle/jre/../bin/javadoc
@options @packages
[ERROR]
[ERROR] Refer to the generated Javadoc files in
'/home/kinow/Development/java/apache/1.3_RC2/target/site/apidocs' dir.
[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

--x snip x--

Cheers
Bruno



- Original Message -
> From: Matt Benson 
> To: Commons Developers List 
> Sent: Friday, 14 October 2016 10:30 AM
> Subject: [VOTE] Release Apache Commons Weaver 1.3 based on RC2
>
> I would like to release the [weaver] component.
>
> Apache Commons Weaver 1.3 RC2 is available for review at:
>   https://dist.apache.org/repos/dist/dev/commons/weaver/ (r16517).
>
> Maven artifacts are at:
>   https://repository.apache.org/content/repositories/orgapachecommons-1210
.
>
> Tested with Oracle JDKs 6, 7 and 8; IBM JDKs 6 and 7.
>
> The Subversion tag is:
>   http://svn.apache.org/repos/asf/commons/proper/weaver/tags/1.3_RC2
> (r1764791).
>
> Site (note some links may be broken; this will be fixed when the site
> is deployed):
>   http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/index.html
>
> RAT Report:
>   http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/rat-report.html
>
> Quality Reports (PMD/Checkstyle/Findbugs/japicmp):
>
> http://people.apache.org/~mbenson/commons-weaver-1.3-
rc2/commons-weaver-parent/commons-weaver-processor/project-reports.html
>
> http://people.apache.org/~mbenson/commons-weaver-1.3-
rc2/commons-weaver-parent/commons-weaver-modules-parent/
commons-weaver-privilizer-parent/commons-weaver-privilizer-api/project-
reports.html
>
> http://people.apache.org/~mbenson/commons-weaver-1.3-
rc2/commons-weaver-parent/commons-weaver-modules-parent/
commons-weaver-privilizer-parent/commons-weaver-privilizer/project-reports.
html
>
> 

Re: Commons CLI Nested Groups

[Gary Gregory]

FWIW, I use JCommander but it does not do complex and/or options.

Gary

On Fri, Oct 14, 2016 at 3:35 AM, sebb  wrote:

> On 14 October 2016 at 11:25, John Patrick  wrote:
> > Imaging your stand alone jar runs an embedded http server, by default
> > it has a embedded testing certificate for the https listener. But in
> > some environments you need to disable https and others you want to
> > overwrite with values.
> >
> > So you have options, something like;
> > [ A or [ B and C and [ D or E ] ] ]
> >
> > [ -no-https | [ -https-port  -keyStoreLocation
> >  [ -keyStorePassword  |
> > -keyStorePassword-prompt ] ] ]
> >
> > -no-https
> >> will explicitly disable https
> >
> > -https-port 
> >> will explicitly enabled https and has and optional port parameter
> >> if you specify -https-port you also need to explicitly specify the
> keystore location and either the password on the command line or state it
> will prompt via the console
> >
> > -keyStoreLocation 
> >> required if -https-port is specified and also has a required parameter
> >
> > -keyStorePassword 
> > -keyStorePassword-prompt
> >> only one of the above must be supplied, not both
> >> if "-keyStorePassword" supplied then it has a required password property
> >> if "keyStorePassword-prompt" supplied then it will request via the
> console when booting
> >
> > I hope that is a clear example. This is something that I'm trying to
> > implement at the moment but having to do several if/else if/else
> > blocks to get it working as needed.
>
> Seems like a good idea.
>
> You could implement most of your example by use of
>
> A not B, C, D, E
> B and C
> D not E
>
> However one would need to group D not E to add
>
> B and DnotE
>
> That should give the behaviour you require with only a single group,
> but you could combine them for simplicity.
>
> I think the dormant/retired Avalon CLI implemented AND or NOT.
> The version in JMeter implements both AND and NOT IIRC.
>
>
> > Cheers,
> > John
> >
> >
> >
> > On 14 October 2016 at 00:26, Gilles 
> wrote:
> >> Hi.
> >>
> >> On Thu, 13 Oct 2016 15:57:00 +0100, John Patrick wrote:
> >>>
> >>> I've posted a message to the users list, but on reflecting I think
> >>> what I'm trying to achieve might be beyond commons-cli current
> >>> ability.
> >>>
> >>> If I fork and work on adding nested OptionGroup's, would it stand a
> >>> change of being merged?
> >>> Is it a feature you want to support/provide?
> >>
> >>
> >> Please describe what you propose in more details.
> >>
> >>>
> >>> I want to check with dev's before wasting time on the potential
> feature...
> >>
> >>
> >> Good precaution, indeed...
> >>
> >> Regards,
> >> Gilles
> >>
> >>>
> >>> cheers,
> >>> John
> >>>
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> >> For additional commands, e-mail: dev-h...@commons.apache.org
> >>
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> > For additional commands, e-mail: dev-h...@commons.apache.org
> >
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition



JUnit in Action, Second Edition



Spring Batch in Action


Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: Commons CLI Nested Groups

[sebb]

On 14 October 2016 at 11:25, John Patrick  wrote:
> Imaging your stand alone jar runs an embedded http server, by default
> it has a embedded testing certificate for the https listener. But in
> some environments you need to disable https and others you want to
> overwrite with values.
>
> So you have options, something like;
> [ A or [ B and C and [ D or E ] ] ]
>
> [ -no-https | [ -https-port  -keyStoreLocation
>  [ -keyStorePassword  |
> -keyStorePassword-prompt ] ] ]
>
> -no-https
>> will explicitly disable https
>
> -https-port 
>> will explicitly enabled https and has and optional port parameter
>> if you specify -https-port you also need to explicitly specify the keystore 
>> location and either the password on the command line or state it will prompt 
>> via the console
>
> -keyStoreLocation 
>> required if -https-port is specified and also has a required parameter
>
> -keyStorePassword 
> -keyStorePassword-prompt
>> only one of the above must be supplied, not both
>> if "-keyStorePassword" supplied then it has a required password property
>> if "keyStorePassword-prompt" supplied then it will request via the console 
>> when booting
>
> I hope that is a clear example. This is something that I'm trying to
> implement at the moment but having to do several if/else if/else
> blocks to get it working as needed.

Seems like a good idea.

You could implement most of your example by use of

A not B, C, D, E
B and C
D not E

However one would need to group D not E to add

B and DnotE

That should give the behaviour you require with only a single group,
but you could combine them for simplicity.

I think the dormant/retired Avalon CLI implemented AND or NOT.
The version in JMeter implements both AND and NOT IIRC.


> Cheers,
> John
>
>
>
> On 14 October 2016 at 00:26, Gilles  wrote:
>> Hi.
>>
>> On Thu, 13 Oct 2016 15:57:00 +0100, John Patrick wrote:
>>>
>>> I've posted a message to the users list, but on reflecting I think
>>> what I'm trying to achieve might be beyond commons-cli current
>>> ability.
>>>
>>> If I fork and work on adding nested OptionGroup's, would it stand a
>>> change of being merged?
>>> Is it a feature you want to support/provide?
>>
>>
>> Please describe what you propose in more details.
>>
>>>
>>> I want to check with dev's before wasting time on the potential feature...
>>
>>
>> Good precaution, indeed...
>>
>> Regards,
>> Gilles
>>
>>>
>>> cheers,
>>> John
>>>
>>
>>
>> -
>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>> For additional commands, e-mail: dev-h...@commons.apache.org
>>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

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

Re: Commons CLI Nested Groups

[John Patrick]

Imaging your stand alone jar runs an embedded http server, by default
it has a embedded testing certificate for the https listener. But in
some environments you need to disable https and others you want to
overwrite with values.

So you have options, something like;
[ A or [ B and C and [ D or E ] ] ]

[ -no-https | [ -https-port  -keyStoreLocation
 [ -keyStorePassword  |
-keyStorePassword-prompt ] ] ]

-no-https
> will explicitly disable https

-https-port 
> will explicitly enabled https and has and optional port parameter
> if you specify -https-port you also need to explicitly specify the keystore 
> location and either the password on the command line or state it will prompt 
> via the console

-keyStoreLocation 
> required if -https-port is specified and also has a required parameter

-keyStorePassword 
-keyStorePassword-prompt
> only one of the above must be supplied, not both
> if "-keyStorePassword" supplied then it has a required password property
> if "keyStorePassword-prompt" supplied then it will request via the console 
> when booting

I hope that is a clear example. This is something that I'm trying to
implement at the moment but having to do several if/else if/else
blocks to get it working as needed.

Cheers,
John



On 14 October 2016 at 00:26, Gilles  wrote:
> Hi.
>
> On Thu, 13 Oct 2016 15:57:00 +0100, John Patrick wrote:
>>
>> I've posted a message to the users list, but on reflecting I think
>> what I'm trying to achieve might be beyond commons-cli current
>> ability.
>>
>> If I fork and work on adding nested OptionGroup's, would it stand a
>> change of being merged?
>> Is it a feature you want to support/provide?
>
>
> Please describe what you propose in more details.
>
>>
>> I want to check with dev's before wasting time on the potential feature...
>
>
> Good precaution, indeed...
>
> Regards,
> Gilles
>
>>
>> cheers,
>> John
>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>

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

Re: [VOTE] Release Apache Commons Weaver 1.3 based on RC2

[Bruno P. Kinoshita]

Hi Matt,

Did you generate the site with Java 8? I tried:

`mvn clean test install`

`mvn site:site`

In the parent project, but the site generation stopped while creating the 
Javadocs.

I'm using Java 8, with Maven 3.3.9.

--x snip x--

[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-site-plugin:3.4:site (default-cli) on project 
commons-weaver-base: Error generating maven-javadoc-plugin:2.10.4:javadoc:
[ERROR] Exit code: 1 - 
/home/kinow/Development/java/apache/1.3_RC2/modules/privilizer/weaver/src/main/java/org/apache/commons/weaver/privilizer/package-info.java:20:
 warning: a package-info.java file has already been seen for package 
org.apache.commons.weaver.privilizer
[ERROR] package org.apache.commons.weaver.privilizer;
[ERROR] ^
[ERROR] javadoc: warning - Multiple sources of package comments found for 
package "org.apache.commons.weaver.privilizer"
[ERROR] 
/home/kinow/Development/java/apache/1.3_RC2/processor/src/main/java/org/apache/commons/weaver/Consumes.java:42:
 warning: no @return
[ERROR] Class>[] value();
[ERROR] ^
[ERROR] 
/home/kinow/Development/java/apache/1.3_RC2/processor/src/main/java/org/apache/commons/weaver/Produces.java:42:
 warning: no @return
[ERROR] Class>[] value();
[ERROR] ^
[ERROR] 
/home/kinow/Development/java/apache/1.3_RC2/processor/src/main/java/org/apache/commons/weaver/lifecycle/WeaveLifecycleToken.java:43:
 warning: no @return
[ERROR] WeaveLifecycle value();
[ERROR] ^
[ERROR] 
/home/kinow/Development/java/apache/1.3_RC2/ant/src/main/java/org/apache/commons/weaver/ant/WeaverSettings.java:113:
 error: unknown tag: String
[ERROR] * @return List
[ERROR] ^
[ERROR] 
/home/kinow/Development/java/apache/1.3_RC2/modules/privilizer/weaver/src/main/java/org/apache/commons/weaver/privilizer/Privilized.java:32:
 warning: no @return
[ERROR] String value();
[ERROR] ^
[ERROR] 
/home/kinow/Development/java/apache/1.3_RC2/modules/privilizer/api/src/main/java/org/apache/commons/weaver/privilizer/Privilizing.java:49:
 warning: no @return
[ERROR] CallTo[] value();
[ERROR] ^
[ERROR] 
/home/kinow/Development/java/apache/1.3_RC2/modules/privilizer/api/src/main/java/org/apache/commons/weaver/privilizer/Privilizing.java:38:
 warning: no @return
[ERROR] Class value();
[ERROR] ^
[ERROR] 
/home/kinow/Development/java/apache/1.3_RC2/modules/privilizer/api/src/main/java/org/apache/commons/weaver/privilizer/Privilizing.java:43:
 warning: no @return
[ERROR] String[] methods() default { };
[ERROR] ^
[ERROR] 
[ERROR] Command line was: /usr/lib/jvm/java-8-oracle/jre/../bin/javadoc 
@options @packages
[ERROR] 
[ERROR] Refer to the generated Javadoc files in 
'/home/kinow/Development/java/apache/1.3_RC2/target/site/apidocs' dir.
[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

--x snip x--

Cheers
Bruno



- Original Message -
> From: Matt Benson 
> To: Commons Developers List 
> Sent: Friday, 14 October 2016 10:30 AM
> Subject: [VOTE] Release Apache Commons Weaver 1.3 based on RC2
> 
> I would like to release the [weaver] component.
> 
> Apache Commons Weaver 1.3 RC2 is available for review at:
>   https://dist.apache.org/repos/dist/dev/commons/weaver/ (r16517).
> 
> Maven artifacts are at:
>   https://repository.apache.org/content/repositories/orgapachecommons-1210 .
> 
> Tested with Oracle JDKs 6, 7 and 8; IBM JDKs 6 and 7.
> 
> The Subversion tag is:
>   http://svn.apache.org/repos/asf/commons/proper/weaver/tags/1.3_RC2
> (r1764791).
> 
> Site (note some links may be broken; this will be fixed when the site
> is deployed):
>   http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/index.html
> 
> RAT Report:
>   http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/rat-report.html
> 
> Quality Reports (PMD/Checkstyle/Findbugs/japicmp):
> 
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-processor/project-reports.html
> 
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer-api/project-reports.html
> 
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-privilizer-parent/commons-weaver-privilizer/project-reports.html
> 
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-modules-parent/commons-weaver-normalizer/project-reports.html
> 
> http://people.apache.org/~mbenson/commons-weaver-1.3-rc2/commons-weaver-parent/commons-weaver-maven-plugin/project-reports.html
> 
> 

Re: [logging] Is Apache Commons Logging still alive?

[Gary Gregory]

Apache Log4j 2 is the preferred migration path IMO.

Log4j 2 provides a clean separation between API and implementation and a
ton of powerful features. Version 2.7 was just released.

Gary

On Fri, Oct 14, 2016 at 12:14 AM, Christian Effertz <
christian.effe...@web.de> wrote:

> Hello,
>
> we support several applications that rely on Apache Commons Logging and
> Log4j as implementation. After some years we got the budget to polish them.
> So we are currently considering how to update the logging framework those
> applications use. Log4j apparently received an update in recent time,
> whereas Commons Logging is unchanged since 2014.
>
> So we are wondering if it would be a good idea to (a) propose pull requests
> via GitHub or (b) to migrate away from Commons Logging.
>
> Probably option (b) is the wiser choice as there has been a similar
> discussion in the related Jira Project,
> https://issues.apache.org/jira/browse/LOGGING-136.
>
> Any official or unofficial comments and thoughts on this topic?
>
> Regards
> Christian Effertz
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition



JUnit in Action, Second Edition



Spring Batch in Action


Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [VOTE] Release Apache Commons Lang 3.5 based on RC2

[Bruno P. Kinoshita]

+1 (not binding)

Build works fine with Java 8;

java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.101-b13, mixed mode)

on Ubuntu 16.04 64 bits;

Linux local 4.4.0-38-generic #57-Ubuntu SMP Tue Sep 6 15:42:33 UTC 2016 x86_64 
x86_64 x86_64 GNU/Linux


On locale en_NZ.UTF-8, time zone Pacific/Auckland. And Maven 3.3.9

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
2015-11-11T05:41:47+13:00)
Maven home: /opt/maven
Java version: 1.8.0_101, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-oracle/jre
Default locale: en_NZ, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-38-generic", arch: "amd64", family: "unix"
All tests pass, site successfully generated. Coverage about the same.


Less issues in CPD, PMD, and Checkstyle; with no new issues added in the 3.5 
release for these reports.

On FindBugs, 3.5 got +1 warning, for an IOException that is being ignored in 
SerializationUtils#deserialize, but not a blocker IMO.

The changes report is showing the release date as 2014-10-13, but I assume it 
is fixed during the release process? 

Keys OK. All good, kudos all!

Bruno
>
> From: Benedikt Ritter 
>To: Commons Developers List  
>Sent: Friday, 14 October 2016 9:20 AM
>Subject: [VOTE] Release Apache Commons Lang 3.5 based on RC2
> 
>
>Hi,
>
>finally I found the time to prepare Apache Commons Lang 3.5 RC2 :-)
>We could not release RC1, because I messed up the release archives. They
>contained some snapshot artifacts. This has been fixed in RC2. Furthermore
>LANG-1275 has been incorporated.
>
>Lang 3.5 RC2 is available for review here:
>  https://dist.apache.org/repos/dist/dev/commons/lang/LANG_3_5_RC2 (svn
>revision 16505)
>
>Tag name:
>   LANG_3_5_RC2 (signature can be checked from git using 'git tag -v')
>
>Tag URL:
>
>https://git-wip-us.apache.org/repos/asf?p=commons-lang.git;a=commit;h=36f98d87b24c2f542b02abbf6ec1ee742f1b158b
>
>Commit ID the tag points at:
>   36f98d87b24c2f542b02abbf6ec1ee742f1b158b
>
>Maven artifacts are here:
>  https://repository.apache.org/content/repositories/orgapachecommons-1209
>
>These are the Maven artifacts and their hashes:
>
>commons-lang3-3.5-javadoc.jar
>(SHA1: 337310e98410d577aca675930bb46405a0a8fb0c)
>commons-lang3-3.5-sources.jar
>(SHA1: f7d878153e86a1cdddf6b37850e00a9f8bff726f)
>commons-lang3-3.5-test-sources.jar
>(SHA1: dfb8a086a03cc9499cff808733fac667f5f50688)
>commons-lang3-3.5-tests.jar
>(SHA1: 8ca309192f104265c67a1570245ae827a8650af9)
>commons-lang3-3.5.jar
>(SHA1: 6c6c702c89bfff3cd9e80b04d668c5e190d588c6)
>commons-lang3-3.5.pom
>(SHA1: 08b969f02dfa03fa493fd6eba4cb9dcceea5aefd)
>
>I've tested with JDK 1.6 using Maven 3.2.5 and Java 7, 8 and Java 9 EA
>using Maven 3.2.5.
>Note that there are some problems when building on Java 9. We're currently
>investigating this, see https://issues.apache.org/jira/browse/LANG-1265
>To build on Java 9 you need to explicitly set the local provide to JRE:
>
>  mvn -Djava.locale.providers=JRE clean test
>
>Details of changes since 3.4 are in the release notes:
>
>https://dist.apache.org/repos/dist/dev/commons/lang/LANG_3_5_RC2/RELEASE-NOTES.txt
>  http://home.apache.org/~britter/commons/lang/3_5_RC2/changes-report.html
>
>Site:
>  http://home.apache.org/~britter/commons/lang/3_5_RC2
>
>Clirr Report (compared to 3.4):
>  http://home.apache.org/~britter/commons/lang/3_5_RC2/clirr-report.html
>(sorry, I messed up the site build and had to add the Clirr report
>manually...)
>
>Note that Clirr reports several errors due to additions in the interface
>org.apache.commons.lang3.time.DatePrinter
>These are considered okay, since the DatePrinter interface is not meant to
>be implemented by clients. This change is documented in the release notes.
>
>RAT report:
>  http://home.apache.org/~britter/commons/lang/3_5_RC2/rat-report.html
>
>KEYS:
>  https://www.apache.org/dist/commons/KEYS
>
>Please review the release candidate and vote.
>This vote will close no sooner than 72 hours from now,
>i.e. sometime after 22:30 UTC+2 16-October 2016.
>
>[ ] +1 Release these artifacts
>[ ] +0 Okay, but...
>[ ] -0 Okay, but really should fix...
>[ ] -1 I oppose this release because...
>
>Thank you,
>Benedikt
>
>
>

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

[logging] Is Apache Commons Logging still alive?

[Christian Effertz]

Hello,

we support several applications that rely on Apache Commons Logging and
Log4j as implementation. After some years we got the budget to polish them.
So we are currently considering how to update the logging framework those
applications use. Log4j apparently received an update in recent time,
whereas Commons Logging is unchanged since 2014.

So we are wondering if it would be a good idea to (a) propose pull requests
via GitHub or (b) to migrate away from Commons Logging.

Probably option (b) is the wiser choice as there has been a similar
discussion in the related Jira Project,
https://issues.apache.org/jira/browse/LOGGING-136.

Any official or unofficial comments and thoughts on this topic?

Regards
Christian Effertz