[jira] [Resolved] (SPARK-10511) Source releases should not include maven jars

["Sean Owen (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/SPARK-10511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen resolved SPARK-10511.
-------------------------------
       Resolution: Fixed
    Fix Version/s: 1.5.1
                   1.6.0

Resolved by https://github.com/apache/spark/pull/8774

> Source releases should not include maven jars
> ---------------------------------------------
>
>                 Key: SPARK-10511
>                 URL: https://issues.apache.org/jira/browse/SPARK-10511
>             Project: Spark
>          Issue Type: Bug
>          Components: Build
>    Affects Versions: 1.5.0
>            Reporter: Patrick Wendell
>            Assignee: Luciano Resende
>            Priority: Blocker
>             Fix For: 1.6.0, 1.5.1
>
>
> I noticed our source jars seemed really big for 1.5.0. At least one contributing factor is that, likely due to some change in the release script, the maven jars are being bundled in with the source code in our build directory. This runs afoul of the ASF policy on binaries in source releases - we should fix it in 1.5.1.
> The issue (I think) is that we might invoke maven to compute the version between when we checkout Spark from github and when we package the source file. I think it could be fixed by simply clearing out the build/ directory after that statement runs.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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