[jira] [Commented] (SOLR-11087) Get rid of jar duplicates in release

["Shawn Heisey (Jira)" <ji...@apache.org>]

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

Shawn Heisey commented on SOLR-11087:
-------------------------------------

I like the idea of replacing the duplicates in dist with a README describing exactly which jars to copy out of the webapp if they are needed and where to find them.  One thing I wonder is whether we expect hardlinks to be supported across all operating systems that natively support tarballs -- if we do, we could use hardlinks to share files in dist and the webapp, and mention this fact in the README.  If we think that hardlinks might be a specialty item, then just the README would be appropriate.

While looking at SOLR-13841 I found that we have duplicate jars other than the ones in dist, which currently are expected.  My question for the moment:  Should I open a new issue for those other duplicates, or would we want to expand this issue to cover a full audit of the jars in the binary release?  I almost started with a new issue ... glad I searched first.


> Get rid of jar duplicates in release
> ------------------------------------
>
>                 Key: SOLR-11087
>                 URL: https://issues.apache.org/jira/browse/SOLR-11087
>             Project: Solr
>          Issue Type: Sub-task
>          Components: Build
>            Reporter: Jan Høydahl
>            Priority: Major
>             Fix For: 8.1, master (9.0)
>
>         Attachments: SOLR-11087.patch
>
>
> Sub task of SOLR-6806
> The {{dist/}} folder contains many duplicate jar files, totalling 10,5M:
> {noformat}
> 4,6M   ./dist/solr-core-6.6.0.jar (WEB-INF/lib)
> 1,2M   ./dist/solr-solrj-6.6.0.jar (WEB-INF/lib)
> 4,7M   ./dist/solrj-lib/* (WEB-INF/lib and server/lib/ext)
> {noformat}
> The rest of the files in dist/ are contrib jars and test-framework.
> To weed out the duplicates and save 10,5M, we can simply add a {{dist/README.md}} file listing what jar files are located where. The file could also contain a bash one-liner to copy them to the dist folder. Another possibility is to ship the binary release tarball with symlinks in the dist folder, and advise people to use {{cp -RL dist mydist}} which will make a copy with the real files. Downside is that this won't work for ZIP archives that do not preserve symlinks, and neither on Windows.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org