[ 
https://issues.apache.org/jira/browse/SOLR-5109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14047162#comment-14047162
 ] 

Michael Dodsworth commented on SOLR-5109:
-----------------------------------------

ah, fun. Those tests don't run under java 8 due to a Saxon-HE issue (which is 
actually fixed in 9.5.1-5).
The guava issue has been fixed in kite-sdk:master - 
https://github.com/kite-sdk/kite/commit/0ab2795872e4e5721f477d79e5049371a17ab8db.
 We'll have to wait for the next drop of kite-sdk before guava can be upgraded.

I'll create a separate issue for updating Saxon-HE and reinstating the affected 
tests. Apologies and thanks for looking this, Shalin.

> Solr 4.4 will not deploy in Glassfish 4.x
> -----------------------------------------
>
>                 Key: SOLR-5109
>                 URL: https://issues.apache.org/jira/browse/SOLR-5109
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.4
>         Environment: Glassfish 4.x
>            Reporter: jamon camisso
>            Priority: Blocker
>              Labels: guava
>         Attachments: LUCENE-5109.patch, guava-15.0-SNAPSHOT.jar
>
>
> The bundled Guava 14.0.1 JAR blocks deploying Solr 4.4 in Glassfish 4.x.
> This failure is a known issue with upstream Guava and is described here:
> https://code.google.com/p/guava-libraries/issues/detail?id=1433
> Building Guava guava-15.0-SNAPSHOT.jar from master and bundling it in Solr 
> allows for a successful deployment.
> Until the Guava developers release version 15 using their HEAD or even an RC 
> tag seems like the only way to resolve this.
> This is frustrating since it was proposed that Guava be removed as a 
> dependency before Solr 4.0 was released and yet it remains and blocks 
> upgrading: https://issues.apache.org/jira/browse/SOLR-3601



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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

Reply via email to