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

Steven Rowe commented on SOLR-3260:
-----------------------------------

bq. I am a bit confused why it is giving the "eval failed..." message though.

It's an NPE, but beyond that I'm not sure what's happening.

The branch_3x Maven job compiles under a 1.5 JDK, then runs tests via Maven's 
Surefire plugin under a 1.6 (OpenJDK) JVM.  

These tests appear to pass on the Solr_3x job under the same 1.6 JVM, though, 
so there's something weird going on here.  (The Solr_3x job runs under Ant, but 
I'm not sure why the Ant/Maven difference would be the cause of this.)

bq. Why don't you make the fix you've proposed and I'll look later to see if 
there is something less-blunt we can do. Sound ok?

Sure, I'll commit those changes now.
                
> Improve exception handling / logging for ScriptTransformer.init()
> -----------------------------------------------------------------
>
>                 Key: SOLR-3260
>                 URL: https://issues.apache.org/jira/browse/SOLR-3260
>             Project: Solr
>          Issue Type: Bug
>          Components: contrib - DataImportHandler
>    Affects Versions: 3.5, 4.0
>            Reporter: James Dyer
>            Assignee: James Dyer
>            Priority: Trivial
>             Fix For: 3.6, 4.0
>
>         Attachments: SOLR-3260.patch
>
>
> This came up on the user-list.  ScriptTransformer logs the same "need a >=1.6 
> jre" message for several problems, making debugging difficult for users.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Reply via email to