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

Grant Ingersoll commented on SOLR-1300:
---------------------------------------

Hmm, part of the problem, I think, lies in:
{quote}
<tar destfile="${dist}/${fullnamever}.tgz" compression="gzip" longfile="gnu">
      <tarfileset dir="."
        prefix="${fullnamever}"
        includes="LICENSE.txt NOTICE.txt *.txt *.xml lib/** src/** example/** 
client/** contrib/"
        excludes="lib/README.committers.txt **/data/ **/logs/* **/classes/ 
**/*.sh **/bin/ src/scripts/ src/site/build/ **/target/ client/ruby/flare/ 
client/python" />
      <tarfileset dir="."
        mode="755"
        prefix="${fullnamever}"
        includes="**/*.sh **/bin/ src/scripts/" />
      <tarfileset dir="."
        prefix="${fullnamever}"
        includes="dist/**"
        excludes="*.tgz *.zip *.md5 ${dist}/*src-* ${dist}/*docs-*" />
      <tarfileset dir="${build.docs}"
        prefix="${fullnamever}/docs/" />
    </tar>
{quote}

Where we blindly include all of contrib.  Still looking...

> need to exlcude downloaded clustering libs from release packages
> ----------------------------------------------------------------
>
>                 Key: SOLR-1300
>                 URL: https://issues.apache.org/jira/browse/SOLR-1300
>             Project: Solr
>          Issue Type: Task
>            Reporter: Hoss Man
>            Assignee: Grant Ingersoll
>             Fix For: 1.4
>
>
> As noted by grant...
> http://www.nabble.com/Re%3A-cleaning-up-example-p24469638.html
> the build file for the clustering contrib downloads some optional jars that 
> can't be included in the release.  Yonik/Hoss simplified the build files, but 
> as a side effect *all* libs are included in the dist (even the ones that 
> shouldn't be)
> we need to exclude them (one way or another) before we release 1.4.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to