[
https://issues.apache.org/jira/browse/LUCENE-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uwe Schindler updated LUCENE-5273:
----------------------------------
Attachment: LUCENE-5273-optimized.patch
Here the patch. ant generate-maven-articfatcs succeeds (it would fail if some
needed files were not extracted from tgz). I did not smoke, as I have only
windows.
In general there is one problem with the whole approach of untaring: It seems
to me that you can no longer build maven artifacts for a single module, it
still builds everything and fails lately (e.g. dist-maven). So I would suggest
to rename those tasks to use "-" as prefix, so you can no longer call them:
"dist-maven" is one that is affected, rename to "-dist-maven". We should do
this in a separate issue.
[~steve_rowe]: Should I commit this optimization? It also largely reduces disk
usage!
> 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, 5.0
>
> Attachments: LUCENE-5273-optimized.patch, 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: [email protected]
For additional commands, e-mail: [email protected]
