geode-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dan Smith (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (GEODE-823) RC Feedback: Fix build artifacts
Date Thu, 04 Feb 2016 21:39:39 GMT

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

Dan Smith commented on GEODE-823:
---------------------------------

I believe GEODE-883 has fixed the empty gemfire-junit jar.

> 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
>
> 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)

Mime
View raw message