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

Steven Rowe commented on LUCENE-2923:
-------------------------------------

The nightly hudson trunk maven build failed last night because the benchmark 
jar wasn't being produced by the {{dist-maven}} target, which is called from 
the {{generate-maven-artifacts}} target.  From 
https://hudson.apache.org/hudson/job/Lucene-Solr-Maven-trunk/31/consoleText :

{noformat}
dist-maven:
[artifact:deploy] Deploying to 
file:///usr/home/hudson/hudson-slave/workspace/Lucene-Solr-Maven-trunk/checkout/modules/dist/maven
[artifact:deploy] An error has occurred while processing the Maven artifact 
tasks.
[artifact:deploy]  Diagnosis:
[artifact:deploy] 
[artifact:deploy] Error deploying artifact 
'org.apache.lucene:lucene-benchmark:jar': Error deploying artifact:
 File 
/usr/home/hudson/hudson-slave/workspace/Lucene-Solr-Maven-trunk/checkout/modules/benchmark/build/lucene-benchmark-4.0-SNAPSHOT.jar
 does not exist

BUILD FAILED
{noformat}

This can be fixed by putting back the {{dist-maven}} specialization that I took 
out of {{modules/benchmark/build.xml}}:

{code:xml}
<target name="dist-maven" depends="jar-core,javadocs,contrib-build.dist-maven"/>
{code}

Committing shortly.

> cleanup contrib/demo
> --------------------
>
>                 Key: LUCENE-2923
>                 URL: https://issues.apache.org/jira/browse/LUCENE-2923
>             Project: Lucene - Java
>          Issue Type: Improvement
>            Reporter: Michael McCandless
>            Assignee: Steven Rowe
>            Priority: Minor
>             Fix For: 3.1, 4.0
>
>         Attachments: LUCENE-2923.patch, LUCENE-2923.patch, LUCENE-2923.patch, 
> LUCENE-2923.patch, LUCENE-2923.patch
>
>
> I don't think we should include optimize in the demo; many people start from 
> the demo and may think you must optimize to do searching, and that's clearly 
> not the case.
> I think we should also use a buffered reader in FileDocument?
> And... I'm tempted to remove IndexHTML (and the html parser) entirely.  It's 
> ancient, and we now have Tika to extract text from many doc formats.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to