[
https://issues.apache.org/jira/browse/LUCENE-873?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12493830
]
Nigel Daley commented on LUCENE-873:
------------------------------------
On or around April 9th, I changed the build to use the "old" nightly.sh script
(but slightly modified). The main modification was that I commented out the
copy of the docs and tar files to the release server (since Hudson takes care
of publishing these now). Unforunately, this meant that the subsequent clover
build further down in the script over-wrote the tar files with clover
references, which Hudson then archives once the script completes.
I've rearranged the script to run clover first then the regular build. I've
run a new build and it seems to be fixed.
> nightly builds depend on clover
> -------------------------------
>
> Key: LUCENE-873
> URL: https://issues.apache.org/jira/browse/LUCENE-873
> Project: Lucene - Java
> Issue Type: Bug
> Reporter: Hoss Man
>
> as reported by Michael Pelz Sherman on [EMAIL PROTECTED] and [EMAIL
> PROTECTED] the nightly builds coming out of hudson current depend on clover...
> [EMAIL PROTECTED] tmp]# strings lucene-core-nightly.jar | grep -i
> clover|more
> org/apache/lucene/LucenePackage$__CLOVER_0_0.class
> org/apache/lucene/analysis/Analyzer$__CLOVER_1_0.class
> ...
> the old nightly.sh dealt with this by running ant nightly twice, first
> without clover to get the jars and then with clover to get the report. it
> loks like maybe this logic never made it into the hudson setup.
> someone with hudson admin access/knowledge will need to look into this.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
