You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@geode.apache.org by "Anthony Baker (JIRA)" <ji...@apache.org> on 2016/02/25 18:57:18 UTC

[jira] [Updated] (GEODE-823) RC Feedback: Fix build artifacts

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

Anthony Baker updated GEODE-823:
--------------------------------
    Fix Version/s: 1.0.0-incubating.M2

> RC Feedback: Fix build artifacts
> --------------------------------
>
>                 Key: GEODE-823
>                 URL: https://issues.apache.org/jira/browse/GEODE-823
>             Project: Geode
>          Issue Type: Task
>    Affects Versions: 1.0.0-incubating.M1
>            Reporter: Nitin Lamba
>             Fix For: 1.0.0-incubating.M2
>
>
> From [~niall.pemberton@btinternet.com]: NEEDS TO BE SPLIT-UP INTO SUBTASKS OR SEPARATE ISSUES:
> * The ASF frowns upon distributing other open source projects without their consent and gemfire-joptsimple (& perhaps gemfire-json) raises concerns
> * Also not re-packaging it means users could face a dependency issue if they also use joptsimple
> * Lastly, "gemfire-joptsimple" could violate someone elses mark
> More specific feedback:
> * pom dependencies look like an issue - see GEODE-818
> * It would be better if the maven artifacts were named "geode" rather than "gemfire"
> * pom files don't have the license header
> * The gemfire-junit-1.0.0-incubating.M1.jar is empty so would be better to not create this maven artifact
> * The ".asc" files don't need checksums (".asc.md5" & ".asc.sha1" files)



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