[GitHub] commons-rdf issue #43: COMMONSRDF-49: Make AbstractRDFParser serializable

Github user stain commented on the issue: https://github.com/apache/commons-rdf/pull/43 You may have better ideas on how to do something like

[GitHub] commons-rdf issue #43: COMMONSRDF-49: Make AbstractRDFParser serializable

Github user stain commented on the issue: https://github.com/apache/commons-rdf/pull/43 Thanks, @ajs6f ! I found some old code where I had tried to make a fluent interface.. I managed to update it to the current master and sorted some issues. I pushed it to the

Re: [text] LocalHostStringLookupTest: correct order of assertEquals arguments

You are welcome! -Pascal Am 14.02.2018 um 21:31 schrieb Gary Gregory: Good catch Pascal, thank you! Gary On Wed, Feb 14, 2018 at 12:59 PM, wrote: Repository: commons-text Updated Branches: refs/heads/master fb5d8c93a -> 6e9107dc8

Re: [text] LocalHostStringLookupTest: correct order of assertEquals arguments

Good catch Pascal, thank you! Gary On Wed, Feb 14, 2018 at 12:59 PM, wrote: > Repository: commons-text > Updated Branches: > refs/heads/master fb5d8c93a -> 6e9107dc8 > > > LocalHostStringLookupTest: correct order of assertEquals arguments > > > Project:

Re: commons-release-plugin git commit: Add self.

> On Feb 14, 2018, at 12:17 PM, Gary Gregory wrote: > >> On Wed, Feb 14, 2018 at 8:04 AM, Rob Tompkins wrote: >> >> Given the typographical errors, should we roll a 1.1? >> > > Why not? :-) Meaning "Go for it" :-) I’ll try to get to it tonight.

[GitHub] commons-text pull request #44: TEXT-80: Fixed confusing StrLookup API

Github user asfgit closed the pull request at: https://github.com/apache/commons-text/pull/44 --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

[GitHub] commons-text pull request #24: TEXT-25: Add a duration parser

Github user asfgit closed the pull request at: https://github.com/apache/commons-text/pull/24 --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

[GitHub] commons-text issue #44: TEXT-80: Fixed confusing StrLookup API

Github user PascalSchumacher commented on the issue: https://github.com/apache/commons-text/pull/44 I'm closing this as `StrLookup` will deprecated and replaced with `StringLookup` in the next release. --- - To

[GitHub] commons-rdf pull request #49: Cleanup for FindBugs and PMD warnings in -simp...

Github user ajs6f commented on a diff in the pull request: https://github.com/apache/commons-rdf/pull/49#discussion_r168275645 --- Diff: commons-rdf-simple/src/main/java/org/apache/commons/rdf/simple/experimental/AbstractRDFParser.java --- @@ -58,8 +60,12 @@ */ public

[GitHub] commons-rdf issue #43: COMMONSRDF-49: Make AbstractRDFParser serializable

Github user ajs6f commented on the issue: https://github.com/apache/commons-rdf/pull/43 Okay, I'll get to work on factoring out a (serializable) factory. Thanks for the discussion everyone! I think the parser types will be much stronger for it. ---

[GitHub] commons-rdf pull request #49: Cleanup for FindBugs and PMD warnings in -simp...

Github user stain commented on a diff in the pull request: https://github.com/apache/commons-rdf/pull/49#discussion_r168274256 --- Diff: commons-rdf-simple/src/main/java/org/apache/commons/rdf/simple/experimental/AbstractRDFParser.java --- @@ -58,8 +60,12 @@ */ public

[GitHub] commons-rdf pull request #43: COMMONSRDF-49: Make AbstractRDFParser serializ...

Github user asfgit closed the pull request at: https://github.com/apache/commons-rdf/pull/43 --- - To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org

[GitHub] commons-rdf issue #43: COMMONSRDF-49: Make AbstractRDFParser serializable

Github user ajs6f commented on the issue: https://github.com/apache/commons-rdf/pull/43 Hm... if @afs and @stain are both feeling reluctant to go this way... I would still be happy to merge it as-is and then work forward to the fluent-ish factory design (since @ansell has given a

[GitHub] commons-rdf pull request #49: Cleanup for FindBugs and PMD warnings in -simp...

Github user ajs6f commented on a diff in the pull request: https://github.com/apache/commons-rdf/pull/49#discussion_r168260775 --- Diff: commons-rdf-simple/src/main/java/org/apache/commons/rdf/simple/experimental/AbstractRDFParser.java --- @@ -58,8 +60,12 @@ */ public

[All][RNG] FindBugs discontinued

Hi. FindBugs chokes on Java 9 "module-info" files[1] and the project has been shut down. There is a replacement: https://spotbugs.github.io/ Is there some common configuration that could be included in CP? Is someone intending to do it? In the meantime, does someone know how to work around

Re: commons-release-plugin git commit: Add self.

On Wed, Feb 14, 2018 at 8:04 AM, Rob Tompkins wrote: > Given the typographical errors, should we roll a 1.1? > Why not? :-) Meaning "Go for it" :-) Gary > > > On Feb 14, 2018, at 9:45 AM, ggreg...@apache.org wrote: > > > > Repository: commons-release-plugin > > Updated

Apache EU Roadshow CFP Closing Soon (23 February)

Hello Everyone This is an initial reminder to let you all know that we are holding an Apache EU Roadshow co-located with FOSS Backstage in Berlin on 13^th and 14^th June 2018. https://s.apache.org/tCHx The Call for Proposals (CFP) for the Apache EU Roadshow is currently open and will close

Re: commons-release-plugin git commit: Add self.

Given the typographical errors, should we roll a 1.1? > On Feb 14, 2018, at 9:45 AM, ggreg...@apache.org wrote: > > Repository: commons-release-plugin > Updated Branches: > refs/heads/master efce48a13 -> 144b5ce3b > > > Add self. > > Project:

Re: [text] Update from Java 7 to Java 8?

On Feb 14, 2018 03:05, "Jochen Wiedmann" wrote: On Tue, Feb 13, 2018 at 11:13 PM, Gary Gregory wrote: > Fine with me. Let's see if anyone objects... As there seem to be other incompatible changes in the pipeline (StrBuilder, etc.), this

Re: [text] Update from Java 7 to Java 8?

On Tue, Feb 13, 2018 at 11:13 PM, Gary Gregory wrote: > Fine with me. Let's see if anyone objects... As there seem to be other incompatible changes in the pipeline (StrBuilder, etc.), this should be a good opportunity. Jochen

Re: Discussion: New commons module/project

@Charles, I thought of Commons because it is where people go to find common code. it provides a web presence to base the code and discussion from. Though perhaps Github would suffice. @Ralph, I agree that reference implementations would be good. But I didn't want to start a "language war" with