[
https://issues.apache.org/jira/browse/SOLR-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13250649#comment-13250649
]
Steven Rowe commented on SOLR-3344:
-----------------------------------
Benson, where are you seeing these failures? Why hasn't Jenkins unearthed them?
Why should Solr test-framework declare these dependencies at all? That is, why
can't modules with Jetty test dependencies simply declare the dependency there
(with scope=test)? This is already the case for the following Solr modules:
solr-core, clustering, and dataimporthandler.
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?
> 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
> Attachments: 0001-Add-jetty-deps.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: [email protected]
For additional commands, e-mail: [email protected]
