Build failed in Jenkins: commons-jexl #20

See Changes: [henrib] JEXL: Various updates & improvements related to last fixes [henrib] JEXL-211: Add callable method to JexlExpression interface - breaks compatibility but it is not expected than any

Build failed in Jenkins: commons-jexl #21

See Changes: [henrib] JEXL: Removed (wrong) statement about Java7 [henrib] JEXL: Added clear statement about compatibility break [henrib] JEXL: Avoiding clirr error --

[GitHub] commons-rdf pull request #33: COMMONSRDF-59 - fix minor javadocs warnings

GitHub user acoburn opened a pull request: https://github.com/apache/commons-rdf/pull/33 COMMONSRDF-59 - fix minor javadocs warnings This add some missing `@return` values, fixes an HTML error and adds some text to two otherwise undocumented parameters. You can merge this pull

Re: [jexl] 3.1 release review

Resurrecting the thread...Hopefully Emmanuel has a few spare cycles. :-) I've commented JEXL-220 with the 3 Clirr errors that correspond to adding methods to interfaces that only Jexl is supposed to implement. I've also added a very clear statements as a waning in the release-notes; it reads as:

[GitHub] commons-rdf pull request #34: COMMONSRDF-60: update commons-parent version

GitHub user acoburn opened a pull request: https://github.com/apache/commons-rdf/pull/34 COMMONSRDF-60: update commons-parent version This upgrades the parent pom to the latest version of `commons-parent`. You can merge this pull request into a Git repository by running: $ git

Jenkins build is back to normal : commons-jexl #22

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

Re: [VOTE] Release Commons Text 1.0 based on RC1

The vote can pass with the following (in order of appearance): Bruno P. Kinoshita: +1 Oliver Heger: +1 Jörg Schaible: +1. Personally, I’m in the +/- 0 area for the reasons that Oliver and Sebb stated. I’m entirely willing to re-build the candidate to get a “spotless” 1.0 release. Does anyone

Re: [VOTE] Release Commons Text 1.0 based on RC1

If you change the artefacts, that's a new release candidate. New vote, too. On 10 March 2017 at 20:23, Bruno P. Kinoshita < brunodepau...@yahoo.com.br.invalid> wrote: > I have never been a RM, but maybe generate new artefacts with the > corrected text files, then release it and send the notes to

Re: [VOTE] Release Commons Text 1.0 based on RC1

I have never been a RM, but maybe generate new artefacts with the corrected text files, then release it and send the notes to the announce e-mail? Users can trace the reason for the changes in your commit message and here in the vote thread. CheersBruno From: Rob Tompkins