lw-nick commented on a change in pull request #888: SOLR-13774 add lucene/solr 
openjdk compatibility matrix to ref guide.
URL: https://github.com/apache/lucene-solr/pull/888#discussion_r329157760
 
 

 ##########
 File path: solr/solr-ref-guide/src/solr-system-requirements.adoc
 ##########
 @@ -93,3 +93,119 @@ The success rate in our automated tests is similar with 
all the Java versions te
 * This version has continuous testing with Java 9, 10, 11, 12 and the 
pre-release version of Java 13.
 * There were known issues with Kerberos with Java 9+ prior to Solr 8.1. If 
using 8.0, you should test in your environment.
 * Be sure to test with SSL/TLS and/or authorization enabled in your 
environment if you require either when using Java 9+.
+
+=== Lucene/Solr OpenJDK Compatibility
+The following compatibility matrix was generated by running an `ant test` 
command for each version of Solr and OpenJDK. The tests were run in a 
non-SSL/TLS environment without authorization enabled. A BUILD SUCCESSFUL 
message resulted in a "Y" and a BUILD FAILED message resulted in a "_N_".
+
+[cols="1,6*^" options="header"]
+|===
+|Lucene/Solr|OpenJDK 8|OpenJDK 9|OpenJDK 10|OpenJDK 11|OpenJDK 12|OpenJDK 13
+|*3.1.0* |_N_     |_N_     |_N_      |_N_      |_N_      |_N_
 
 Review comment:
   Thank you for providing your feedback. I have added some additional context 
and a couple clarifying questions below:
   
   I believe this compatibility matrix has a benefit to Solr end users and it 
will be helpful in the planning of deployments. I am not able to find these 
specific details in the current reference guide and I think that is the best 
place for this information.
   
   The primary use case is for an IT environment with many installations of 
Solr and different JDK versions, where migration and standardization efforts 
require this level of detailed planning.
   
   The secondary use case is for anyone planning a new deployment of Solr with 
latest JDK version. For example, when I run ant test for Solr 8.0.0 using 
OpenJDK 13, I get a compilation error and build failed message. I am sure there 
is a workaround for this issue but it may create confusion when end users are 
evaluating Solr for a new project.
   
   @anshumg The ant test suite runs many tests, and if the build is successful, 
then that is a good indication of compatibility in my view. The majority of the 
failures resulted from compilation errors. What method would you suggest for 
generating the compatibility matrix?
   
   @janhoy I am happy to add other versions of commonly deployed open JDKs. The 
build system is extensible and new JDKs and Solr versions can be added 
relatively easily. If you could add one other JDK+version what would it be and 
why?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
[email protected]


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to