Has anybody heard of the Lucene version 2.3.1.3?
We're using it in a production project.
However the stable version of Lucene version 2.0.0.4.
Should I push to have the project's dependencies moved to version 2.0.0.4?
Are you talking about Lucene or Lucene.NET? These are different but related projects. Lucene.NET is a .NET port of the Lucene Java code.
2.0.0.4 is the stable version of Lucene.NET.
However, there is a version 2.3.1 of Lucene (for Java). The Lucene Website makes it seem like 2.4.1 is the most recent release suitable for production.
I'm running 2.3.1.3 over here in production at about 50 sites.
I wouldn't recommend downgrading the version as a lot of performance and memory leak issues are adressed in 2.3.1.
Related
I am planning to use MapStruct in my project. Using JDK11, Spring boot 2.7.x has my current version but soon planning to upgrade it to JDK17 and Spring Boot 3.0. Based on documentation, latest library will support JDK8 onwards. Would like to know, whether library will support for above said specification. And also would like to know, how actively the project is going to support in near future?
We are maintaining an application using GraphDB as a backend service. This application is built on spring-boot, and we are testing the application with a test-dependency to graphdb-runtime. It seems like GDB relies on an old version of Dropwizard (3.x), which had it's last release many years ago. Version 3.2.6 seems to be the last 3.x version.
This old version dependency clashes with the spring-boot dependency management (4.x), and these Dropwizard dependencies are managed manually. This is something we would like to avoid. Are there any plans to lift the Dropwizard dependency in GDB to version 4.x?
Unfortunately upgrading the version of dropwizard isn’t straightforward because of major differences between dropwizard 3.x and 4.x but we’ll see if we can plan this for a future GraphDB version.
I am using grails 2.3.0 and wanted to know which version of mongodb GORM is compatible with it.
The latest version of mongodb GORM requires 2.3.2 > http://grails.org/plugin/mongodb
My mongodb version currently is 2.6.0 but that should not matter I suppose.
It would be great If I could also know the gorm datastore dependencies version for grails 2.3.0 and mongodb gorm. Below are the ones for the latest mongo gorm.
dependencies {
…
compile 'org.grails:grails-datastore-gorm:3.1.0.RELEASE'
compile 'org.grails:grails-datastore-core:3.1.0.RELEASE'
test 'org.grails:grails-datastore-simple:3.1.0.RELEASE'
}
I also tried to go thru all the releases for mongodb gorm here: https://github.com/grails/grails-data-mapping/releases but did not get much of help.
In my Grails 2.3.11 app I'm using
compile ':mongodb:3.0.2'
before upgrade from 2.2.x to 2.3.x I was using :mongodb:3.0.1.
In another Grails 1.3.7 app I'm using :mongodb:1.0.0.RC4 with some hacks to enable aggregation.
I tried to find a version of plugin in between to match my Grails version best, but it's not trivial. The branch names in github have nothing to do with released plugin versions.
BTW,
early versions of Grails 2.3.0 has severe problems (don't remember which ones exactly, but they made the upgrade from 2.2.x impossible). So, I'd recommend to upgrade your Grails to the most recent 2.3.11
This JIRA issue and this wiki page imply that there is an up-and-coming component called org.apache.solr.spelling.suggest.Suggester for doing improved auto-complete with Solr. But I'm having trouble trying to find a release that actually has this code.
The wiki says that Solr 3.x and 4.x have include it; is that insider-speak for Solr 1.3 and 1.4 respectively? I'm using 1.4.1 (via Maven), and I see no such component.
Pulling the source from here, I find it in src/java/org/apache/solr/spelling/suggest/Suggester.java. But it fails to build with:
[javac] Compiling 8 source files to /Users/user/Downloads/apache-solr-4.0-2011-02-22_08-06-33/apache-solr-4.0-2011-02-22_08-06-33/contrib/analysis-extras/build/classes
BUILD FAILED
/Users/user/Downloads/apache-solr-4.0-2011-02-22_08-06-33/apache-solr-4.0-2011-02-22_08-06-33/common-build.xml:275: /Users/user/Downloads/apache-solr-4.0-2011-02-22_08-06-33/apache-solr-4.0-2011-02-22_08-06-33/contrib/analysis-extras/lib does not exist.
Is there a way to get a reasonably stable Solr artifact with the Suggester included, preferably via Maven?
Solr 3.x and 4.x are not 1.3 and 1.4.
1.3 and 1.4 are stable releases. 3.x and 4.x are yet unreleased. Versioning scheme changed due to Solr merging with Lucene.
If you need a 4.x build I recommend getting one from the build server.
Also note there are several ways to implement autocomplete with 1.4.1, see Simple Solr schema problem for autocomplete
Do anyone know when Eclipse plans to move its codebase to > 1.5 (i.e. using generic & annotation)?
Even the latest plan for the upcoming eclipse 3.6 Helios still mentions:
Most of the Eclipse SDK is "pure" Java code and has no direct dependence on the underlying operating system. The chief dependence is therefore on the Java Platform itself.
Portions are targeted to specific classes of operating environments, requiring their source code to only reference facilities available in particular class libraries (e.g. J2ME Foundation 1.1, J2SE 1.4, Java 5, etc).
In general, the 3.6 release of the Eclipse Project is developed on a mix of Java 1.4, Java 5 and Java 6 VMs.
As such, the Eclipse SDK as a whole is targeted at all modern, desktop Java VMs.
Most functionality is available for 1.4 level development everywhere, and extended development capabilities are made available on the VMs that support them.
So as long as they want to support platforms with an old JDK, the incentive to rewrite a large portion of the codebase in recent JDK is low.
Note: e4 (Eclipse 4.0) will be based on Java 5.
In general, the 1.0 release of the e4 Project is developed on Java SE 5.
Some of Eclipse codebase (the Java EE part) is already using 1.5 level. As for the rest of it, I don't think they have any plans - I doubt if it is worth the effort.
More here -> http://www.eclipse.org/downloads/moreinfo/jre.php