[
https://issues.apache.org/jira/browse/LUCENE-5273?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13793299#comment-13793299
]
Uwe Schindler edited comment on LUCENE-5273 at 10/12/13 8:31 AM:
-----------------------------------------------------------------
bq. Hmm, the Maven Ant Tasks install and deploy tasks require that the source
resources be files - at least, the documentation makes no mention of anything
but files - so I don't think there's any way to avoid unpacking the archives.
Yeah, I noticed this, too.
I am not sure of the overhead, but as the binary artifact also contains
javadocs and those are many small files, this makes the task run slowly on
windows and some filesystems. How about *only* extracting JAR files on the
untar task? I would only add some patternset matching only {{\*\*/\*.jar}} to
the untar task (see last example on
http://ant.apache.org/manual/Tasks/unzip.html).
I will try this out soon, just need breakfast!
was (Author: thetaphi):
bq. Hmm, the Maven Ant Tasks install and deploy tasks require that the source
resources be files - at least, the documentation makes no mention of anything
but files - so I don't think there's any way to avoid unpacking the archives.
Yeah, I noticed this, too.
I am not sure of the overhead, but as the binary artifact also contains
javadocs and those are many small files, this makes the task run slowly on
windows and some filesystems. How about *only* extracting JAR files on the
untar task? I would only add some patternset matching only {{**/*.jar}} to the
untar task (see last example on http://ant.apache.org/manual/Tasks/unzip.html).
I will try this out soon, just need breakfast!
> 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.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]
