lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Muir (JIRA)" <>
Subject [jira] [Commented] (SOLR-4050) Solr example fails to start in nightly-smoke
Date Thu, 08 Nov 2012 15:03:12 GMT


Robert Muir commented on SOLR-4050:

I really think the failure was due to the second pre-existing problem i mentioned above (I
caused these actually)

Really a horrible bug (thats why i want to know its fixed!): because we do "special" ivy stuff
here it was possible
for you to have a example/lib with both 8.1.2 and 8.1.7 jars. This would then get sucked into
binary packaging!

I had previously worked LUCENE-4390 to detect this issue and fail the build on it explicitly,
but i feel
like we maybe disabled that because of a problem deleting files in Windows jenkins...

Good that the smoketester found this!
> Solr example fails to start in nightly-smoke
> --------------------------------------------
>                 Key: SOLR-4050
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>            Reporter: Michael McCandless
>            Priority: Blocker
> The nightly smoke job is stalled (I'll go kill it shortly):
> It's stalled when trying to run the Solr example ... the server produced this output:
> {noformat}
> java.lang.ClassNotFoundException: org.eclipse.jetty.xml.XmlConfiguration
> 	at$
> 	at Method)
> 	at
> 	at java.lang.ClassLoader.loadClass(
> 	at java.lang.ClassLoader.loadClass(
> 	at org.eclipse.jetty.start.Main.invokeMain(
> 	at org.eclipse.jetty.start.Main.start(
> 	at org.eclipse.jetty.start.Main.main(
> ClassNotFound: org.eclipse.jetty.xml.XmlConfiguration
> Usage: java -jar start.jar [options] [properties] [configs]
>        java -jar start.jar --help  # for more information
> {noformat}
> Seems likely the Jetty upgrade somehow caused this...
> Separately I committed a fix to smoke tester so that it quickly fails if the Solr example
fails to start ...

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

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

View raw message