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

Jan Høydahl commented on SOLR-11087:
------------------------------------

Ah, now I see. You mean jaring up the {{webapp/web}} folder. I did a count and 
those are 310 files. I agree it would compress better and make fewer files to 
unzip.
But on the other hand I like the fact that you very easily can simply edit a 
HTML or JS file and see the change in Solr's Admin. I think it has helped 
people identifying and fixing UI bugs for us. If it was all inside a jar that 
needed unpack -> edit -> re-pack to see the change, then hacking on Solr's UI 
would be less accessible both for users and developers.

Moving all the {{solr.xml}} things into Java code is actually just a benefit, 
it keeps folks from treating Solr as a Web app and doing things the wrong way. 
At the same time, I think we'll see complaints once we do the move, from people 
who depend on their custom filters etc. But as I said, I think that is just a 
positive step towards a truly standalone app.

> 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
>             Fix For: master (8.0), 7.1
>
>         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
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to