You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Steven Rowe (Reopened) (JIRA)" <ji...@apache.org> on 2012/04/10 21:01:13 UTC
[jira] [Reopened] (SOLR-3344) POM dependencies not all there yet
for solr-test-framework
[ https://issues.apache.org/jira/browse/SOLR-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Steven Rowe reopened SOLR-3344:
-------------------------------
bq. If it does turn out that Solr test-framework is the right place for these dependencies, it doesn't require Jetty to compile, so at a minimum, I would argue that the default compile scope you've used is inappropriate. Maybe scope=runtime?
I forgot to incorporate this change - reopening to change Solr test-framework's Jetty dependencies' scope from compile to runtime.
> POM dependencies not all there yet for solr-test-framework
> ----------------------------------------------------------
>
> Key: SOLR-3344
> URL: https://issues.apache.org/jira/browse/SOLR-3344
> Project: Solr
> Issue Type: Bug
> Components: Build
> Affects Versions: 4.0
> Reporter: Benson Margulies
> Assignee: Steven Rowe
> Fix For: 4.0
>
> Attachments: 0001-Add-jetty-deps.patch, SOLR-3344.patch
>
>
> The pom for solr-test-framework does not mention jetty, so a test case that doesn't get jetty into it's classpath otherwise fails with:
> {noformat}
> java.lang.NoClassDefFoundError: org/eclipse/jetty/server/SessionIdManager
> {noformat}
--
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: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org