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

Steve Rowe commented on LUCENE-5273:
------------------------------------

[~markrmil...@gmail.com], do you want this on the 4.5 release branch?  It would 
produce a better set of distributions, but is maybe a little too risky, so soon 
after committing it?

FWIW, {{ant nightly-smoke}} passed for me on both trunk and branch_4x before I 
committed each place, and I re-ran the 4.5RC5 test from branch_4x (converting 
exceptions to debug prints for the non-identicality tests and for missing 
stuff, to allow the script to continue e.g. when it didn't find the new 
expressions module), and it complained in the right places.

> Binary artifacts in Lucene and Solr convenience binary distributions 
> accompanying a release, including on Maven Central, should be identical 
> across all distributions
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: LUCENE-5273
>                 URL: https://issues.apache.org/jira/browse/LUCENE-5273
>             Project: Lucene - Core
>          Issue Type: Bug
>          Components: general/build
>            Reporter: Steve Rowe
>            Assignee: Steve Rowe
>             Fix For: 4.6
>
>         Attachments: LUCENE-5273.patch
>
>
> As mentioned in various issues (e.g. LUCENE-3655, LUCENE-3885, SOLR-4766), we 
> release multiple versions of the same artifact: binary Maven artifacts are 
> not identical to the ones in the Lucene and Solr binary distributions, and 
> the Lucene jars in the Solr binary distribution, including within the war, 
> are not identical to the ones in the Lucene binary distribution.  This is bad.
> It's (probably always?) not horribly bad, since the differences all appear to 
> be caused by the build re-creating manifests and re-building jars and the 
> Solr war from their constituents at various points in the release build 
> process; as a result, manifest timestamp attributes, as well as archive 
> metadata (at least constituent timestamps, maybe other things?), differ each 
> time a jar is rebuilt.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

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

Reply via email to