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

2017-10-03 Thread scela
Github user scela commented on the issue: https://github.com/apache/maven-indexer/pull/17 I'll be preparing a migration directly to just-released Lucene 7. --- - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.o

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

2017-07-30 Thread olamy
Github user olamy commented on the issue: https://github.com/apache/maven-indexer/pull/17 @scela fair enough. But as Lucene API change really often... Maybe migrate to the latest now so we are safe for a bit of time :-) --- If your project is set up for it, you can reply to this ema

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

2017-07-28 Thread scela
Github user scela commented on the issue: https://github.com/apache/maven-indexer/pull/17 https://issues.apache.org/jira/browse/MINDEXER-104 Done On Fri, Jul 28, 2017 at 3:43 PM, Martin Todorov wrote: > @scela , > > You can file

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

2017-07-28 Thread carlspring
Github user carlspring commented on the issue: https://github.com/apache/maven-indexer/pull/17 @scela , You can file a new issue under [MINDEXER](https://issues.apache.org/jira/browse/MINDEXER) Jira. Cheers, Martin --- If your project is set up for it, you

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

2017-07-28 Thread scela
Github user scela commented on the issue: https://github.com/apache/maven-indexer/pull/17 Sure. Can you point me where the Jira project is hosted? Lucene usually makes major changes so I suspect going to 6.6 would be much more work. I'd prefer to move to 6.1 first and then after

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

2017-07-28 Thread carlspring
Github user carlspring commented on the issue: https://github.com/apache/maven-indexer/pull/17 The changes, (despite my minor remarks), look good! Thanks for this pull! :) --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well.

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

2017-07-28 Thread cstamas
Github user cstamas commented on the issue: https://github.com/apache/maven-indexer/pull/17 @olamy @scela sounds fine to me --- 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 have this feature enabl

[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