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

Hoss Man commented on SOLR-2588:
--------------------------------

bq. With some small changes, Velocity could be optional.

Velocity (and the velocitywriter) were optional before, and a conscious and 
deliberate choice was made to promote it into a core dependency so that admin 
code (and users) could start expecting it to reliable always work.

if we want to re-consider i'm fine with having that discussion, but it 
shouldn't be an "optional core" feature ... either it's a core feature and 
dependency, or it's an optional contrib.

It's not a bug that code in solr has a direct dependency on jars in the lib dir.

> Solr doesn't work without Velocity on classpath
> -----------------------------------------------
>
>                 Key: SOLR-2588
>                 URL: https://issues.apache.org/jira/browse/SOLR-2588
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 3.2
>            Reporter: Gunnar Wagenknecht
>             Fix For: 3.3
>
>
> In 1.4. it was fine to run Solr without Velocity on the classpath. However, 
> in 3.2. SolrCore won't load because of a hard reference to the Velocity 
> response writer in a static initializer.
> {noformat}
> ... ERROR org.apache.solr.core.CoreContainer - 
> java.lang.NoClassDefFoundError: org/apache/velocity/context/Context
>       at org.apache.solr.core.SolrCore.<clinit>(SolrCore.java:1447)
>       at org.apache.solr.core.CoreContainer.create(CoreContainer.java:463)
>       at org.apache.solr.core.CoreContainer.load(CoreContainer.java:316)
>       at org.apache.solr.core.CoreContainer.load(CoreContainer.java:207)
> {noformat}

--
This message is automatically generated by JIRA.
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