[GitHub] maven-indexer issue #17: Migration to Lucene 6.1.0

2017-07-27 Thread olamy
Github user olamy commented on the issue: https://github.com/apache/maven-indexer/pull/17 @scela maybe you can create a Jira entry for the project? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not

[GitHub] maven-indexer issue #17: Migration to Lucene 6.1.0

2017-07-27 Thread olamy
Github user olamy commented on the issue: https://github.com/apache/maven-indexer/pull/17 what about last one 6.6.0? :-) @cstamas do you have any issues with that? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If yo

Re: [VOTE] Release Apache Maven Enforcer Plugin version 3.0.0-M1

2017-07-27 Thread Peter Ansell
The sha1 matches for me and the plugin (including requireJavaVersion) works under both Oracle JDK 8+u131 and Oracle JDK 9+177. Thanks, Peter On 27 July 2017 at 06:58, Robert Scholte wrote: > Hi, > > We solved 14 issues: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317520

Re: Any feedback for MNG-6261?

2017-07-27 Thread Dawid Weiss
I added a comment on that issue. The problem is not deterministic for some reason -- I can execute identical maven on identical code on the same computer and get two different outcomes (consistenly). I have no idea how to debug it better too -- passing -X doesn't yield any reasonable logs. Looks ve

Re: Any feedback for MNG-6261?

2017-07-27 Thread Robert Scholte
I had a look at it, but can't reproduce the issue with the attached project Even when using exactly the same directory (D:\repositories\carrotsearch.com\lingo4g) my build succeeds. A failing project is really required to fix this. Robert On Thu, 27 Jul 2017 13:41:16 +0200, Dawid Weiss wrot

Any feedback for MNG-6261?

2017-07-27 Thread Dawid Weiss
Hello, Just wanted to hear if anybody has any idea about MNG-6261 I filed recently -- there is a relatively simple repro attached and it fails with Maven 3.5.0+; I've been wondering if it's a bug or an illegal abuse of the submodule/parent pom relationship. Dawid