lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Steven Rowe (Commented) (JIRA)" <>
Subject [jira] [Commented] (SOLR-3344) POM dependencies not all there yet for solr-test-framework
Date Tue, 10 Apr 2012 13:43:19 GMT


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:
>             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:!default.jspa
For more information on JIRA, see:


To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message