Originally, gemfire-json and gemfire-joptsimple were bundled to fix bugs present in those libs. There’s an intent to move away from the JSON parser entirely in GEODE-629. Attached to that bug is a diff of the changes made to the original source. For the joptsimple library, I’ve filed a new JIRA as GEODE-826 (also with diffs attached).
In general, I do think it makes sense to move away from redistributing these libs though I’m still looking for ASF policy discussions on this topic. Anyone have specific pointers to previous discussions? Anthony > On Jan 19, 2016, at 8:07 PM, Niall Pemberton <niall.pember...@gmail.com> > wrote: > > Hi, > > Firstly, great job on producing the first RC. From an ASF release PoV, the > main concerns for me would be gemfire-joptsimple and the binary distro > NOTICE file and those stop me giving a +1 vote. From a user PoV the > dependencies in the maven pom look painful, trying to determine which can > safely be excluded. > > > 3. Maven Artifacts > * 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.
signature.asc
Description: Message signed with OpenPGP using GPGMail
