[jira] [Updated] (GEODE-1360) need to support command line parameter to use my own log4j.xml in running tests
[ https://issues.apache.org/jira/browse/GEODE-1360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-1360: Fix Version/s: 1.0.0-incubating.M3 > need to support command line parameter to use my own log4j.xml in running > tests > --- > > Key: GEODE-1360 > URL: https://issues.apache.org/jira/browse/GEODE-1360 > Project: Geode > Issue Type: Bug > Components: general >Reporter: xiaojian zhou >Assignee: xiaojian zhou > Fix For: 1.0.0-incubating.M3 > > > The tests are mainly executed by gradle command line, however, we cannot > specify a log4j.xml to turn on trace. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-611) Remove Dependency on LGPL Licensed Findbugs Annoations
[ https://issues.apache.org/jira/browse/GEODE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-611: --- Sprint: 1.0.0-incubating.M3 > Remove Dependency on LGPL Licensed Findbugs Annoations > -- > > Key: GEODE-611 > URL: https://issues.apache.org/jira/browse/GEODE-611 > Project: Geode > Issue Type: Task > Components: core >Affects Versions: 1.0.0-incubating >Reporter: Niall Pemberton >Assignee: Anthony Baker > Fix For: 1.0.0-incubating.M1 > > > FindBugs Annoations (SuppressWarnings & SuppressFBWarnings) have been used in > 27 files in geode-core and the FindBugs LGPL License is not permitted under > ASF policy: > - http://findbugs.sourceforge.net/ > There is an Apache Licensed "clean room" implementation of the findbugs > annotations[1] and I have asked on the legal-discuss list[2] if theres any > reason this can't be used > [1] https://github.com/stephenc/findbugs-annotations > [2] http://markmail.org/message/ieczgjovzhll76yl -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-904) Update LICENSE for BSD/MIT dependencies
[
https://issues.apache.org/jira/browse/GEODE-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-904:
---
Sprint: (was: 1.0.0-incubating.M2)
> Update LICENSE for BSD/MIT dependencies
> ---
>
> Key: GEODE-904
> URL: https://issues.apache.org/jira/browse/GEODE-904
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Anthony Baker
>Assignee: Anthony Baker
> Fix For: 1.0.0-incubating.M2
>
>
> The following files need to be listed in the LICENSE:
> {noformat}
> - ANSIBuffer (BSD) [1]
> - font awesome (front are SIL and css is MIT) [2]
> - normalise.css (MIT) [3]
> - bootstrap (MIT) [3]
> - boot flat (MIT) [4]
> - headjs (MIT) [5]
> - iCheck (MIT) [6]
> - html5shiv (MIT) [7]
> - respond (MIT) [8]
> - polyfill (MIT/BSD) [8]
> - InternalDataSerializer.java [9] contains code from BSD license protobuf
> that should be in license
> 1.
> ./gemfire-core/src/main/java/com/gemstone/gemfire/management/internal/cli/shell/jline/ANSIBuffer.java
> 2. ./gemfire-site/website/content/font/*
> 3. ./gemfire-site/website/content/bootstrap/bootstrap.min.css
> 4. ./gemfire-site/website/content/css/bootflat*
> 5. ./gemfire-site/website/content/js/head.js
> 6. ./gemfire-site/website/content/js/jquery.icheck.js
> 7. ./gemfire-site/website/content/js/html5shiv.js
> 8. ./gemfire-site/website/content/js/respond.min.js
> 9
> ./gemfire-core/src/main/java/com/gemstone/gemfire/internal/InternalDataSerializer.java
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-53) Update and fix pages in the website
[ https://issues.apache.org/jira/browse/GEODE-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-53: -- Sprint: (was: 1.0.0-incubating.M2) > Update and fix pages in the website > --- > > Key: GEODE-53 > URL: https://issues.apache.org/jira/browse/GEODE-53 > Project: Geode > Issue Type: Improvement > Components: web-content >Reporter: William Markito Oliveira >Assignee: William Markito Oliveira > Fix For: 1.0.0-incubating.M1 > > > There are some pages in the website that may need attention and updates. > Here is a list of the main pages and initial ideas that can improve and fix > it: > Getting Started: > - How to section is not well formatted and need a better organization. > - Learn the Basics (Videos) > - Not sure it should be listed here and given that it's all GemFire it's a > bit confusing still. > - Download Geode link should be removed from this page since it's already in > the top. > - Understand some examples section should also go somewhere > - Documentation should be a direct link from the main menu and not the last > thing of this page. > Community > - Conferences need to be updated ad need to work on some automation here to > simplify things. > - Systems (JIRA, Wiki) and mailing lists links should be more accessible and > just listed - not in the middle of text or phrases. Also they should be moved > to the Contribute (or How to Contribute) page. > - Don't know why Project History is here, we should move this to a main > "About" page. > Contribute > - This page starts with text about GemFire/Geode history - Which IHMO should > also be moved to the "About" page or something like that. As well as the > incubator proposal link, etc. > - The contribute page should probably only have sections about: What can be > contributions and how to do them - Code, documentation, bugs, answers on > StackOverflow, etc. > Download > Since we don't have releases yet, as per ASF policy we can point them to the > GitHub repo and I'd say we should probably copy the very basics steps to > build the project here so people can start, with a pointer for the Wiki for > detailed instructions. Something like: git clone, build, gfsh.. > - Documentation section on this page should be moved to it's own page. > - Remove the Coming Soon section about the VM and include a pointer to the > Docker image on Docker Hub. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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
]
William Markito Oliveira updated GEODE-823:
---
Sprint: 1.0.0-incubating.M3
> RC Feedback: Fix build artifacts
>
>
> Key: GEODE-823
> URL: https://issues.apache.org/jira/browse/GEODE-823
> Project: Geode
> Issue Type: Task
> Components: build
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Nitin Lamba
> Fix For: 1.0.0-incubating.M3
>
>
> From [~niall.pember...@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)
[jira] [Updated] (GEODE-27) Apache Geode POM file(s) are incorrect!
[
https://issues.apache.org/jira/browse/GEODE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-27:
--
Sprint: 1.0.0-incubating.M3
> Apache Geode POM file(s) are incorrect!
> ---
>
> Key: GEODE-27
> URL: https://issues.apache.org/jira/browse/GEODE-27
> Project: Geode
> Issue Type: Bug
> Components: build, general
>Affects Versions: 1.0.0-incubating
> Environment: Apache Geode in Maven or Gradle-based applications.
>Reporter: John Blum
>Assignee: Dan Smith
>Priority: Critical
> Labels: ApacheGeode, Maven, POM
> Fix For: 1.0.0-incubating.M2
>
> Attachments: gemfire-8.2.0.pom,
> gemfire-core-1.0.0-incubating-SNAPSHOT.pom,
> gemfire-jgroups-1.0.0-incubating-SNAPSHOT.pom,
> gemfire-joptsimple-1.0.0-incubating-SNAPSHOT.pom,
> gemfire-json-1.0.0-incubating-SNAPSHOT.pom,
> geode-core-1.0.0-incubating.M2-SNAPSHOT.pom
>
>
> This JIRA is a followup to [GEODE-23] to note the additional issues that are
> considered
> ["out-of-scope"|http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201505.mbox/ajax/%3CCA%2BULb%2Btfm4LyjwMaB_B7j8WaBNoAYj1%2BkeZSW-pqv0Gdbq2T8g%40mail.gmail.com%3E]
> for [GEODE-23], yet need to be fixed, none-the-less.
> Specifically, the changes include...
> 1. The {{}} declarations need to be cleaned up (reduced).
> Technically, _Apache Geode_ should only require...
> {code:xml}
>
>
> gemstone-release
> GemStone Maven RELEASE Repository
> http://dist.gemstone.com/maven/release
>
> true
> always
>
>
>
> libs-release
> Spring Maven libs-release Repository
> http://repo.spring.io/libs-release
>
>
> {code}
> For instance, the "obscure" *jline-1.0.S2-B.jar* dependency is "resolvable"
> from, for instance...
> http://repo.spring.io/libs-release/net/sourceforge/jline/jline/1.0.S2-B/jline-1.0.S2-B.jar
> NOTE: by default, and unlike Gradle, Maven searches "Maven Central".
> 2. Add proper "scopes", "optional" settings and "exclusions" to the
> dependencies declared in the POM.
> 3. Many of the "explicitly" declared dependencies (e.g. spring-beans) need
> to be removed; Maven will resolve dependencies transitively.
> As an example, _Apache Geode's_ Maven POM file should be very similar to the
> {{Pivotal GemFire}} Maven POM file, as recently updated and validated for
> *GemFire 8.2* (see attached {{gemfire-8.2.0.pom}} file for further details
> and reference). This is particularly important where _Apache Geode_ and
> _Pivotal GemFire_ intersect.
> There maybe other issues with the POM file that need to be included within
> the "scope" of this +bug+ as well and should be included as such, otherwise
> this JIRA should *+not+* be marked "complete".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1133) SeparateClassloaderTestRunner has to be re-implemented
[ https://issues.apache.org/jira/browse/GEODE-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-1133: Sprint: 1.0.0-incubating.M3 > SeparateClassloaderTestRunner has to be re-implemented > -- > > Key: GEODE-1133 > URL: https://issues.apache.org/jira/browse/GEODE-1133 > Project: Geode > Issue Type: Improvement > Components: http session >Reporter: Sai Boorlagadda > Fix For: 1.0.0-incubating.M3 > > > While working on GEODE-52, it was found that `SeparateClassloaderTestRunner' > is copied from stackoverflow > (http://stackoverflow.com/questions/42102/using-different-classloaders-for-different-junit-tests) > Either this code has to be re-implemented or find an appropriate code from > another reliable source, so that we can add it to the NOTICE about the > license. > extensions/geode-modules-session/src/test/java/com/gemstone/gemfire/modules/session/junit/SeparateClassloaderTestRunner.java: -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1293) Align code and docs for modules
[ https://issues.apache.org/jira/browse/GEODE-1293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-1293: Sprint: 1.0.0-incubating.M3 > Align code and docs for modules > --- > > Key: GEODE-1293 > URL: https://issues.apache.org/jira/browse/GEODE-1293 > Project: Geode > Issue Type: Improvement > Components: docs, extensions, hibernate, http session >Reporter: Jens Deppe >Assignee: Jens Deppe > Fix For: 1.0.0-incubating.M3 > > > Need to ensure that the docs for the modules are correct. There are startup > script changes as well as config changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1256) Geode website - Unapproved licenses
[ https://issues.apache.org/jira/browse/GEODE-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-1256: Sprint: 1.0.0-incubating.M3 > Geode website - Unapproved licenses > --- > > Key: GEODE-1256 > URL: https://issues.apache.org/jira/browse/GEODE-1256 > Project: Geode > Issue Type: Improvement > Components: web-content >Reporter: Dave Barnes >Priority: Minor > Fix For: 1.0.0-incubating.M3 > > > A Geode build (on develop/M3) produces a list of 10 website files with > unapproved licenses: > * > Summary > --- > Generated at: 2016-04-19T09:38:24-07:00 > Notes: 11 > Binaries: 10 > Archives: 1 > Standards: 5974 > Apache Licensed: 5921 > Generated Documents: 0 > JavaDocs are generated and so license header is optional > Generated files do not required license headers > 10 Unknown Licenses > *** > Unapproved licenses: > > /Users/dbarnes/Repo/incubator-geode/geode-site/content/css/bootflat-extensions.css > > /Users/dbarnes/Repo/incubator-geode/geode-site/content/css/bootflat-square.css > /Users/dbarnes/Repo/incubator-geode/geode-site/content/css/bootflat.css > > /Users/dbarnes/Repo/incubator-geode/geode-site/content/css/font-awesome.min.css > > /Users/dbarnes/Repo/incubator-geode/geode-site/content/font/fontawesome-webfont-svg.svg > /Users/dbarnes/Repo/incubator-geode/geode-site/content/js/head.js > /Users/dbarnes/Repo/incubator-geode/geode-site/content/js/html5shiv.js > > /Users/dbarnes/Repo/incubator-geode/geode-site/content/js/jquery-1.10.1.min.js > /Users/dbarnes/Repo/incubator-geode/geode-site/content/js/jquery.icheck.js > /Users/dbarnes/Repo/incubator-geode/geode-site/content/js/respond.min.js -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1146) CI failure: QueryUsingPoolDUnitTest.testBindParamsWithMulitipleClients
[ https://issues.apache.org/jira/browse/GEODE-1146?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-1146: Sprint: 1.0.0-incubating.M3 > CI failure: QueryUsingPoolDUnitTest.testBindParamsWithMulitipleClients > -- > > Key: GEODE-1146 > URL: https://issues.apache.org/jira/browse/GEODE-1146 > Project: Geode > Issue Type: Bug > Components: membership >Reporter: Jianxia Chen >Assignee: Udo Kohlmeyer > Labels: CI, Flaky > Fix For: 1.0.0-incubating.M3 > > > https://brazil.gemstone.com:8080/job/Geode_develop_DistributedTests/2082/testReport/com.gemstone.gemfire.cache.query.dunit/QueryUsingPoolDUnitTest/testBindParamsWithMulitipleClients/ > java.lang.AssertionError: Suspicious strings were written to the log during > this run. > Fix the strings or use IgnoredException.addIgnoredException to ignore. > --- > Found suspect string in log4j at line 1143688 > [fatal 2016/03/29 22:31:26.669 PDT tid=0xc63] > Membership service failure: Member isn't responding to heartbeat requests > com.gemstone.gemfire.ForcedDisconnectException: Member isn't responding to > heartbeat requests > at > com.gemstone.gemfire.distributed.internal.membership.gms.mgr.GMSMembershipManager.forceDisconnect(GMSMembershipManager.java:2586) > at > com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.forceDisconnect(GMSJoinLeave.java:885) > at > com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.processRemoveRequest(GMSJoinLeave.java:578) > at > com.gemstone.gemfire.distributed.internal.membership.gms.membership.GMSJoinLeave.processMessage(GMSJoinLeave.java:1542) > at > com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessenger$JGroupsReceiver.receive(JGroupsMessenger.java:1089) > at org.jgroups.JChannel.invokeCallback(JChannel.java:817) > at org.jgroups.JChannel.up(JChannel.java:741) > at org.jgroups.stack.ProtocolStack.up(ProtocolStack.java:1030) > at org.jgroups.protocols.FRAG2.up(FRAG2.java:165) > at org.jgroups.protocols.FlowControl.up(FlowControl.java:392) > at org.jgroups.protocols.UNICAST3.deliverMessage(UNICAST3.java:1064) > at org.jgroups.protocols.UNICAST3.handleDataReceived(UNICAST3.java:779) > at org.jgroups.protocols.UNICAST3.up(UNICAST3.java:426) > at > com.gemstone.gemfire.distributed.internal.membership.gms.messenger.StatRecorder.up(StatRecorder.java:71) > at > com.gemstone.gemfire.distributed.internal.membership.gms.messenger.AddressManager.up(AddressManager.java:75) > at org.jgroups.protocols.TP.passMessageUp(TP.java:1590) > at org.jgroups.protocols.TP$SingleMessageHandler.run(TP.java:1802) > at org.jgroups.util.DirectExecutor.execute(DirectExecutor.java:10) > at org.jgroups.protocols.TP.handleSingleMessage(TP.java:1718) > at org.jgroups.protocols.TP.receive(TP.java:1643) > at > com.gemstone.gemfire.distributed.internal.membership.gms.messenger.Transport.receive(Transport.java:160) > at org.jgroups.protocols.UDP$PacketReceiver.run(UDP.java:701) > at java.lang.Thread.run(Thread.java:745) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1203) gfsh connect --use-http reports a ClassNotFoundException
[
https://issues.apache.org/jira/browse/GEODE-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-1203:
Sprint: 1.0.0-incubating.M3
> gfsh connect --use-http reports a ClassNotFoundException
>
>
> Key: GEODE-1203
> URL: https://issues.apache.org/jira/browse/GEODE-1203
> Project: Geode
> Issue Type: Bug
> Components: rest (admin)
>Affects Versions: 1.0.0-incubating.M2
>Reporter: Dan Smith
> Fix For: 1.0.0-incubating.M3
>
>
> Connecting with the admin REST API is now broken. I think it's because the
> spring-web jar is no longer placed in the lib directory or added to the
> gfsh-deps.jar. In geode-assembly/build.gradle, the gfshDepsJars tries to add
> spring-web to the classpath, but it is not actually part of the runtime
> configuration so this expression evaluates to null
> {code}
> def springWeb = configurations.runtime.collect { it.getName() }.find {
> it.contains('spring-web') }
> {code}
> {noformat}
> gfsh>connect --use-http --url=http://localhost:7070/gemfire/v1
> Exception in thread "Gfsh Launcher" java.lang.NoClassDefFoundError:
> org/springframework/http/client/ClientHttpRequestFactory
> at
> com.gemstone.gemfire.management.internal.cli.commands.ShellCommands.connect(ShellCommands.java:214)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.springframework.util.ReflectionUtils.invokeMethod(ReflectionUtils.java:216)
> at
> com.gemstone.gemfire.management.internal.cli.shell.GfshExecutionStrategy.execute(GfshExecutionStrategy.java:110)
> at
> org.springframework.shell.core.AbstractShell.executeCommand(AbstractShell.java:127)
> at
> com.gemstone.gemfire.management.internal.cli.shell.Gfsh.promptLoop(Gfsh.java:891)
> at org.springframework.shell.core.JLineShell.run(JLineShell.java:179)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException:
> org.springframework.http.client.ClientHttpRequestFactory
> at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 11 more
> Exception in thread "main" java.lang.NullPointerException
> at
> com.gemstone.gemfire.management.internal.cli.Launcher.parseOptions(Launcher.java:235)
> at
> com.gemstone.gemfire.management.internal.cli.Launcher.parseCommandLine(Launcher.java:243)
> at
> com.gemstone.gemfire.management.internal.cli.Launcher.main(Launcher.java:95)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1316) Update @since tags to include GemFire or Geode in the version name
[ https://issues.apache.org/jira/browse/GEODE-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-1316: Sprint: 1.0.0-incubating.M3 > Update @since tags to include GemFire or Geode in the version name > -- > > Key: GEODE-1316 > URL: https://issues.apache.org/jira/browse/GEODE-1316 > Project: Geode > Issue Type: Task > Components: docs >Reporter: Dan Smith > Fix For: 1.0.0-incubating.M3 > > > Based on [this > discussion|http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201604.mbox/%3CCAFh%2B7k1nPayKdS--rvqG4uvB%3DjKnTibNqHkfFJf0Kkiy9wQ7bw%40mail.gmail.com%3E] > on the mailing list, we want to update all of our \@since tags to be either > Geode x.y.z or GemFire x.y.z, depending on when the new method was added to > the public API. > We need to go through all of the existing tags and update them to match this > standard. Almost all of them should become \@since GemFire x.y.z unless they > are 1.0 or 9.0, in which case they should probably be \@since Geode 1.0.0. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1267) NOTICE file improvements
[
https://issues.apache.org/jira/browse/GEODE-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-1267:
Sprint: 1.0.0-incubating.M3
> NOTICE file improvements
>
>
> Key: GEODE-1267
> URL: https://issues.apache.org/jira/browse/GEODE-1267
> Project: Geode
> Issue Type: Bug
>Affects Versions: 1.0.0-incubating.M2
>Reporter: Anthony Baker
>Assignee: Anthony Baker
>Priority: Minor
> Fix For: 1.0.0-incubating.M3
>
>
> See
> http://mail-archives.apache.org/mod_mbox/incubator-general/201604.mbox/%3c06448bb1-9eac-48c5-9f63-41f09ecfc...@classsoftware.com%3e
> The following changes are suggested:
> 1) Simplify the included Spring NOTICE's to included what's required. For
> example:
> {noformat}
> This product includes software developed by the Spring LDAP Project
> (http://www.springframework.org/ldap).
> {noformat}
> 2) Remove name/copyright of bundled ASF projects from NOTICE. There are
> conflicting viewpoints on this one. We should try to get a consensus from
> the general@ list and follow their recommendation.
> We should also update the license wiki:
> https://cwiki.apache.org/confluence/display/GEODE/License+Guide+for+Contributors
> Affected files:
> * ./geode-assembly/src/main/dist/NOTICE
> * ./geode-pulse/src/main/webapp/META-INF/NOTICE
> * ./geode-web/src/main/webapp/META-INF/NOTICE
> * ./geode-web-api/src/main/webapp/META-INF/NOTICE
> * ./NOTICE
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1331) gfsh.bat on Windows is incorrect
[
https://issues.apache.org/jira/browse/GEODE-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-1331:
Sprint: 1.0.0-incubating.M3
> gfsh.bat on Windows is incorrect
>
>
> Key: GEODE-1331
> URL: https://issues.apache.org/jira/browse/GEODE-1331
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Jens Deppe
> Fix For: 1.0.0-incubating.M3
>
>
> Initial report:
> {quote}
> I am doing testing in windows STS. I am not adding these dependencies jars,
> gfsh.bat is what doing this.
>
> C:\DEV\Pivotal\GemFire_v82014\bin\gfsh.bat has below code, which is setting
> gemfire, antlr, gfsh-dependencies and pulse-dependencies jars in classpath.
> Line 26 to 29
> @set
> GEMFIRE_JARS=%GEMFIRE%\lib\gemfire.jar;%GEMFIRE%\lib\antlr.jar;%GEMFIRE%\lib\gfsh-dependencies.jar;%GEMFIRE%\lib\pulse-dependencies.jar
> @if defined CLASSPATH (
> @set GEMFIRE_JARS=%GEMFIRE_JARS%;%CLASSPATH%
> )
> C:\DEV\Pivotal\GemFire_v82014\lib\gemfire.jar // DUPLICATE
> C:\DEV\Pivotal\GemFire_v82014\lib\antlr.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\gfsh-dependencies.jar // DUPLICATE
> C:\DEV\Pivotal\GemFire_v82014\lib\pulse-dependencies.jar
>
> Unix C:\DEV\Pivotal\GemFire_v82014\bin script, does not set these jars in
> classpath.
>
>
> Another observation is that, if I pass --include-system-classpath to gfsh
> start server command, then it is prepending gemfire.jar and
> gfsh-dependencies.jar to the system classpath and adding that to the server,
> that is what is shown in logs
> Class Path:
> C:\DEV\Pivotal\GemFire_v82014\lib\gemfire.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\gfsh-dependencies.jar
>
> ………..
> C:\Program Files\Java\jdk1.7.0_67\lib\tools.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\server-dependencies.jar
>
> start server \
> --name=${NAME} --server-port=${PORT} \
> --properties-file=${GEMFIRE_PWD}/resources/cache.properties \
> --J=-Dgemfire.distributed-system-id=${DISTRIBUTED_SYSTEM_ID} \
> --J=-Dgemfire.bind-address=${HOST_NAME}
> --J=-Dgemfire.server-bind-address=${HOST_NAME} \
> --J=-Dgemfire.locators=${HOST_NAME}[${LOCATOR_PORT}] \
> --J=-Dgemfire.OSProcess.ENABLE_OUTPUT_REDIRECTION=true \
> --include-system-classpath
>
> If I don’t pass this parameter, then it does not add gfsh-dependencies
> Class Path:
> C:\DEV\Pivotal\GemFire_v82014\lib\gemfire.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\server-dependencies.jar
>
> I am trying to do testing without using –include-system-classpath instead add
> jars in to the start server –classpath as a work around.
> {quote}
> And a subsequent reply from John Blum:
> {quote}
> My apologies. I was not aware that you were launching your GemFire process
> (e.g. Server) using Gfsh, and specifically with gfsh.bat on Windows.
> I just confirmed the line(s) you were looking at in gfsh.bat, and indeed the
> BAT file is wrong! Specifically, the classpath for the GemFire process is
> being constructed from the following lines...
> @set
> GEMFIRE_JARS=%GEMFIRE%\lib\gemfire.jar;%GEMFIRE%\lib\antlr.jar;%GEMFIRE%\lib\gfsh-dependencies.jar;%GEMFIRE%\lib\pulse-dependencies.jar
> ...
> @set GFSH_JARS=;%GEMFIRE%\lib\gfsh-dependencies.jar
> @set CLASSPATH=%GFSH_JARS%;%GEMFIRE_JARS%
> The Windows BAT file is also inconsistent with the Bash shell version (gfsh),
> which rightfully only contains...
> GEMFIRE_JARS=$GEMFIRE/lib/gfsh-dependencies.jar
> if [ "x$CLASSPATH" != "x" ]; then
> GEMFIRE_JARS=$GEMFIRE_JARS:$CLASSPATH
> fi
> CLASSPATH=$GEMFIRE_JARS
> In addition, the Bash shell version launches the Gfsh process using the java
> -classpath option...
> "$GF_JAVA" -Dgfsh=true
> -Dlog4j.configurationFile=/com/gemstone/gemfire/internal/logging/log4j/log4j2-cli.xml
> ${JLINE_TERMINAL} -classpath "${CLASSPATH}" $JAVA_ARGS $LAUNCHER "$@"
> Which does not "export", or rather, set the global System CLASSPATH
> environment variable. Here it is only setting the Java System property to
> the Java process, where as, I believe, the Window BAT file is actually
> setting the System CLASSPATH environment variable, since there is no java
> -classpath option present in the command to launch Gfsh...
> @"%GF_JAVA%" -Dgfsh=true
> -Dlog4j.configurationFile=/com/gemstone/gemfire/internal/logging/log4j/log4j2-cli.xml
> %JAVA_ARGS% %LAUNCHER% %*
> Regarding...
> > I think we need Pivotal Engineering team to look into gfsh.bat and
> > –include-system-classpath behavior.
> Not exactly. --include-system-classpath basically functions such that it
> appends the value of the System CLASSPATH environment variable to the forked
> GemFire process launched from Gfsh if the user has set the global variable
> per environment and wishes to use it.
> In a nutshell, GemFire documentation use to erroneously recommend users to
> set the System CLASSPATH e
[jira] [Updated] (GEODE-818) Clean up the dependencies of geode-core by moving non-core features to subprojects
[ https://issues.apache.org/jira/browse/GEODE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-818: --- Sprint: (was: 1.0.0-incubating.M3) > Clean up the dependencies of geode-core by moving non-core features to > subprojects > -- > > Key: GEODE-818 > URL: https://issues.apache.org/jira/browse/GEODE-818 > Project: Geode > Issue Type: Task >Affects Versions: 1.0.0-incubating.M1 >Reporter: Nitin Lamba >Assignee: Dan Smith > > Maven and POM dependencies are too many for simple > From [~niall.pember...@btinternet.com]: > If I'm building a gemfire client and depend on gemfire-core, do I really need > all those dependencies? Do I always need them for a gemfire member? Looks to > me like some of them should be "optional" or "provided" - especially some of > the logging stuff. > * Spring Framework only referenced in CLI & Web, except XmlEntity (uses > org.springframework.util.Assert) and PdxInstanceImpl (uses > org.springframework.util.StringUtils) > * SequenceFile only class to directly reference commons-logging > * commons-lang only used in hdfs & CLI > * javax.mail only used in MailManager > * Jetty only referenced by ManagementAgent & RestAgent, except for > CumulativeNonDistinctResults > * Netty only referenced in the redis package > * Can't find any reference to slf4j -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1) Graduate from Apache Incubator and achieve the status of the TLP project
[ https://issues.apache.org/jira/browse/GEODE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-1: - Sprint: (was: 1.0.0-incubating.M3) > Graduate from Apache Incubator and achieve the status of the TLP project > > > Key: GEODE-1 > URL: https://issues.apache.org/jira/browse/GEODE-1 > Project: Geode > Issue Type: Wish > Components: general >Affects Versions: 1.0.0-incubating >Reporter: Roman Shaposhnik >Assignee: William Markito Oliveira > Original Estimate: 8,736h > Remaining Estimate: 8,736h > > While achieving the level of maturity required to graduate to the status of > the TLP project we might as well take care of world domination while we are > at it. After all, it may be possible to do to RAM what HDFS has done to disk > and Geode may very well be the thing that does it! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-37) Package renaming
[ https://issues.apache.org/jira/browse/GEODE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-37: -- Sprint: (was: 1.0.0-incubating.M3) > Package renaming > > > Key: GEODE-37 > URL: https://issues.apache.org/jira/browse/GEODE-37 > Project: Geode > Issue Type: Task > Components: docs, general >Affects Versions: 1.0.0-incubating >Reporter: William Markito Oliveira >Priority: Blocker > Fix For: 2.0.0-incubating > > > Geode packages should be renamed from com.gemstone -> org.apache.geode in > order to allow an easy transition from incubation to become a TLP. > Also, it allow the necessary work that may need to be done at the protocol > level in order to allow serialization/message exchange between nodes before > an actual release using the definitive class/package naming. > The issue was discussed in the following thread at dev@: > http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201505.mbox/ajax/%3C554B38C3.5050500%40pidster.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-828) Callbacks required to implement Declarable during restart
[
https://issues.apache.org/jira/browse/GEODE-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-828:
---
Sprint: (was: 1.0.0-incubating.M3)
> Callbacks required to implement Declarable during restart
> -
>
> Key: GEODE-828
> URL: https://issues.apache.org/jira/browse/GEODE-828
> Project: Geode
> Issue Type: Bug
> Components: general, tools
>Reporter: William Markito Oliveira
>
> When callbacks get created without implementing {code}Declarable{code} the
> cluster config seems to be writing them to cache.xml and them requiring that
> in order to restart the cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-818) Clean up the dependencies of geode-core by moving non-core features to subprojects
[ https://issues.apache.org/jira/browse/GEODE-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-818: --- Sprint: 1.0.0-incubating.M3 > Clean up the dependencies of geode-core by moving non-core features to > subprojects > -- > > Key: GEODE-818 > URL: https://issues.apache.org/jira/browse/GEODE-818 > Project: Geode > Issue Type: Task >Affects Versions: 1.0.0-incubating.M1 >Reporter: Nitin Lamba >Assignee: Dan Smith > > Maven and POM dependencies are too many for simple > From [~niall.pember...@btinternet.com]: > If I'm building a gemfire client and depend on gemfire-core, do I really need > all those dependencies? Do I always need them for a gemfire member? Looks to > me like some of them should be "optional" or "provided" - especially some of > the logging stuff. > * Spring Framework only referenced in CLI & Web, except XmlEntity (uses > org.springframework.util.Assert) and PdxInstanceImpl (uses > org.springframework.util.StringUtils) > * SequenceFile only class to directly reference commons-logging > * commons-lang only used in hdfs & CLI > * javax.mail only used in MailManager > * Jetty only referenced by ManagementAgent & RestAgent, except for > CumulativeNonDistinctResults > * Netty only referenced in the redis package > * Can't find any reference to slf4j -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-37) Package renaming
[ https://issues.apache.org/jira/browse/GEODE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-37: -- Sprint: 1.0.0-incubating.M3 > Package renaming > > > Key: GEODE-37 > URL: https://issues.apache.org/jira/browse/GEODE-37 > Project: Geode > Issue Type: Task > Components: docs, general >Affects Versions: 1.0.0-incubating >Reporter: William Markito Oliveira >Priority: Blocker > Fix For: 2.0.0-incubating > > > Geode packages should be renamed from com.gemstone -> org.apache.geode in > order to allow an easy transition from incubation to become a TLP. > Also, it allow the necessary work that may need to be done at the protocol > level in order to allow serialization/message exchange between nodes before > an actual release using the definitive class/package naming. > The issue was discussed in the following thread at dev@: > http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201505.mbox/ajax/%3C554B38C3.5050500%40pidster.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-828) Callbacks required to implement Declarable during restart
[
https://issues.apache.org/jira/browse/GEODE-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-828:
---
Sprint: 1.0.0-incubating.M3
> Callbacks required to implement Declarable during restart
> -
>
> Key: GEODE-828
> URL: https://issues.apache.org/jira/browse/GEODE-828
> Project: Geode
> Issue Type: Bug
> Components: general, tools
>Reporter: William Markito Oliveira
>
> When callbacks get created without implementing {code}Declarable{code} the
> cluster config seems to be writing them to cache.xml and them requiring that
> in order to restart the cluster.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-1) Graduate from Apache Incubator and achieve the status of the TLP project
[ https://issues.apache.org/jira/browse/GEODE-1?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-1: - Sprint: 1.0.0-incubating.M3 > Graduate from Apache Incubator and achieve the status of the TLP project > > > Key: GEODE-1 > URL: https://issues.apache.org/jira/browse/GEODE-1 > Project: Geode > Issue Type: Wish > Components: general >Affects Versions: 1.0.0-incubating >Reporter: Roman Shaposhnik >Assignee: William Markito Oliveira > Original Estimate: 8,736h > Remaining Estimate: 8,736h > > While achieving the level of maturity required to graduate to the status of > the TLP project we might as well take care of world domination while we are > at it. After all, it may be possible to do to RAM what HDFS has done to disk > and Geode may very well be the thing that does it! -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-914) Review NOTICE (again)
[ https://issues.apache.org/jira/browse/GEODE-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-914: --- Sprint: (was: 1.0.0-incubating.M2) > Review NOTICE (again) > - > > Key: GEODE-914 > URL: https://issues.apache.org/jira/browse/GEODE-914 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Anthony Baker >Assignee: Anthony Baker > Fix For: 1.0.0-incubating.M2 > > > Thanks to great feedback from IPMC on the general@ list we have a better idea > of how to construct the NOTICE file. Please review the following threads and > linked docs: > http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3c7ac725d7-ecec-45ff-95ae-bd77d1b18...@pivotal.io%3e > http://mail-archives.apache.org/mod_mbox/incubator-general/201601.mbox/%3cCADY20s5nLc9zLKoNYf_8W8vf+Q6ri=-utanuaxzgorbysxw...@mail.gmail.com%3e > https://nifi.apache.org/licensing-guide.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-946) Source and javadoc artifacts from modules have inconsistent locations
[
https://issues.apache.org/jira/browse/GEODE-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-946:
---
Sprint: (was: 1.0.0-incubating.M2)
> Source and javadoc artifacts from modules have inconsistent locations
> -
>
> Key: GEODE-946
> URL: https://issues.apache.org/jira/browse/GEODE-946
> Project: Geode
> Issue Type: Bug
> Components: extensions
>Reporter: Jens Deppe
>Assignee: Jens Deppe
> Fix For: 1.0.0-incubating.M2
>
>
> The current build process for the modules create artifacts as:
> {noformat}
> extensions> find gemfire-modules/build/libs/
> gemfire-modules/build/libs/
> gemfire-modules/build/libs/gemfire-modules-1.0.0-incubating-SNAPSHOT.jar
> gemfire-modules/build/libs/extensions
> gemfire-modules/build/libs/extensions/gemfire-modules-1.0.0-incubating-SNAPSHOT-sources.jar
> gemfire-modules/build/libs/extensions/gemfire-modules-1.0.0-incubating-SNAPSHOT-javadoc.jar
> {noformat}
> Both the sources and javadoc jars should be placed directly in {{libs/}} and
> not in {{libs/extensions}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-627) Generate source artifacts from gradle build
[ https://issues.apache.org/jira/browse/GEODE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-627: --- Sprint: 1.0.0-incubating.M3 > Generate source artifacts from gradle build > --- > > Key: GEODE-627 > URL: https://issues.apache.org/jira/browse/GEODE-627 > Project: Geode > Issue Type: Task >Reporter: Nitin Lamba >Assignee: Anthony Baker >Priority: Critical > Fix For: 1.0.0-incubating.M1 > > > The current gradle build generated in 'gemfire-assembly' does not include > source artifacts. As part of the release process, source distribution task > needs to be added. > Suggested by Niall Pemberton on Dec/02/2015. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-18) Initial Code Cleanup
[ https://issues.apache.org/jira/browse/GEODE-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-18: -- Sprint: 1.0.0-incubating.M3 > Initial Code Cleanup > > > Key: GEODE-18 > URL: https://issues.apache.org/jira/browse/GEODE-18 > Project: Geode > Issue Type: Task > Components: general >Affects Versions: 1.0.0-incubating >Reporter: Niall Pemberton >Assignee: Dick Cavender > Fix For: 1.0.0-incubating.M1 > > Attachments: > 0001-Replace-Pivotal-License-Header-with-Apache-License.patch, > 0002-Add-Missing-Apache-License-headers.patch, > 0003-Remove-Pivotal-VMWare-AsIs-License-and-add-ASF-Licen.patch, > 0004-Add-ASF-License-Header-to-scala-files.patch, > 0005-Add-ASF-License-Header-to-XML-files.patch, > 0006-Add-ASF-License-Header-to-DTD-XSD-files.patch, > 0007-Add-ASF-License-Header-to-HTML-files.patch, > 0008-Change-Swagger-ApiInfo-from-Pivotal-Gemfire-to-Apach.patch, > 0009-Add-Update-ASF-License-to-java-files.patch, > 0010-Add-ASF-License-to-html-xml-xsd-dtd-files.patch, > geode-rat-excludes-2015-10-19.txt, geode-rat-excludes-2015-10-24.txt, > geode-rat-excludes-2015-11-22.txt, geode-rat-report-2015-05-11.txt, > geode-rat-report-2015-05-17.txt, geode-rat-report-2015-10-19.txt, > geode-rat-report-2015-10-24.txt, geode-rat-report-2015-11-17.txt, > geode-rat-report-2015-11-22.txt > > > Please see the Incubator guide: > * http://incubator.apache.org/guides/mentor.html#initial-clean-up > Source & Notice File policy: > * http://www.apache.org/legal/src-headers.html > Apache RAT is a tool that can help with source file headers: > * http://creadur.apache.org/rat/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-944) ServerLauncherJUnitTest fails when ISP redirects DNS failures
[
https://issues.apache.org/jira/browse/GEODE-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-944:
---
Sprint: (was: 1.0.0-incubating.M2)
> ServerLauncherJUnitTest fails when ISP redirects DNS failures
> -
>
> Key: GEODE-944
> URL: https://issues.apache.org/jira/browse/GEODE-944
> Project: Geode
> Issue Type: Bug
> Components: management
>Reporter: Dan Smith
>Assignee: Jianxia Chen
> Fix For: 1.0.0-incubating.M2
>
>
> This test fails when using a DNS server that redirects DNS lookup failures to
> an ISP's search page.
> {noformat}
> om.gemstone.gemfire.distributed.LocatorLauncherJUnitTest >
> testSetBindAddressToUnknownHost FAILED
> java.lang.AssertionError: Expected exception:
> java.lang.IllegalArgumentException
> com.gemstone.gemfire.distributed.ServerLauncherJUnitTest >
> testSetServerBindAddressToUnknownHost FAILED
> java.lang.AssertionError: Expected exception:
> java.lang.IllegalArgumentException
> {noformat}
> The test is expecting to see an UnknownHostException, but because the ISP
> returns a real IP address rather than the expected DNS lookup failure, the
> test doesn't see the exception.
> We could probably just Use junit's Assume to cause these tests to get skipped
> in this environment.
> See this email thread for more details:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3CCAOqetn_FTeV9ee4R8mkg4Y%3D8a%3DjedgfdOSjDxcnj2N7W02maCw%40mail.gmail.com%3E
> A little more information on DNS hijacking:
> http://www.dnsknowledge.com/whatis/nxdomain-non-existent-domain-2/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-903) Update copyright year in website footer
[ https://issues.apache.org/jira/browse/GEODE-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-903: --- Sprint: (was: 1.0.0-incubating.M2) > Update copyright year in website footer > --- > > Key: GEODE-903 > URL: https://issues.apache.org/jira/browse/GEODE-903 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Anthony Baker > Fix For: 1.0.0-incubating.M2 > > > The publication year in the copyright notice should be updated to 2016: > gemfire-site/website/layouts/footer.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1025) Remove compile dependency on spring data gemfire/geode
[ https://issues.apache.org/jira/browse/GEODE-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-1025: Sprint: 1.0.0-incubating.M3 > Remove compile dependency on spring data gemfire/geode > -- > > Key: GEODE-1025 > URL: https://issues.apache.org/jira/browse/GEODE-1025 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Dan Smith >Assignee: Dan Smith > Fix For: 1.0.0-incubating.M2 > > > We have a compile dependency on spring data gemfire in the ServerLauncher > class to support launching a server using a spring data gemfire configuration > instead of a cache.xml file. > That's a good feature to have, but it should be part of spring data gemfire, > not geode. Because of this compile dependency on SDG, we currently have a > circular dependency on SDG -> Geode -> SDG. That makes it difficult to do > things like rename packages in geode (GEODE-37) because SDG is still using > the old packages. > Instead of directly depending on spring data gemfire, we should provide an > extension point that SDG can plug into to override the cache server startup > behavior. > The easiest place way to do this is just to use the java ServiceLoader > mechanism. We can provide an interface for a plugin that replaces startup > behavior of the server. SDG can provide an implementation of this interface. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-906) Clean up source header / modification text
[ https://issues.apache.org/jira/browse/GEODE-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-906: --- Sprint: 1.0.0-incubating.M3 > Clean up source header / modification text > -- > > Key: GEODE-906 > URL: https://issues.apache.org/jira/browse/GEODE-906 > Project: Geode > Issue Type: Bug >Reporter: Anthony Baker >Assignee: Sai Boorlagadda > Fix For: 1.0.0-incubating.M2 > > > IdentityArrayList and HashIndexSet should use the standard Apache source > header with a separate modification statement for clarity [1]. > [1] http://www.apache.org/dev/licensing-howto.html#mod-notice > May be required to add to source NOTICE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-906) Clean up source header / modification text
[ https://issues.apache.org/jira/browse/GEODE-906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-906: --- Sprint: (was: 1.0.0-incubating.M2) > Clean up source header / modification text > -- > > Key: GEODE-906 > URL: https://issues.apache.org/jira/browse/GEODE-906 > Project: Geode > Issue Type: Bug >Reporter: Anthony Baker >Assignee: Sai Boorlagadda > Fix For: 1.0.0-incubating.M2 > > > IdentityArrayList and HashIndexSet should use the standard Apache source > header with a separate modification statement for clarity [1]. > [1] http://www.apache.org/dev/licensing-howto.html#mod-notice > May be required to add to source NOTICE. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-608) Integrate RAT into build
[ https://issues.apache.org/jira/browse/GEODE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-608: --- Sprint: 1.0.0-incubating.M3 > Integrate RAT into build > > > Key: GEODE-608 > URL: https://issues.apache.org/jira/browse/GEODE-608 > Project: Geode > Issue Type: Improvement > Components: build >Affects Versions: 1.0.0-incubating >Reporter: Anthony Baker >Assignee: Anthony Baker > Fix For: 1.0.0-incubating.M1 > > > We need to ensure license requirements are met. See discussion at > http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201511.mbox/%3cCA+ULb+uLyB9_3QSA+qk5UZ5E8idXdCd=1z+9zr9y2c6n1vo...@mail.gmail.com%3e > Gradle plugin available at > https://plugins.gradle.org/plugin/org.nosphere.apache.rat -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-26) Apache Geode 'build.gradle' inappropriately declares mavenLocal() in Repository declarations.
[
https://issues.apache.org/jira/browse/GEODE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-26:
--
Sprint: (was: 1.0.0-incubating.M2)
> Apache Geode 'build.gradle' inappropriately declares mavenLocal() in
> Repository declarations.
> -
>
> Key: GEODE-26
> URL: https://issues.apache.org/jira/browse/GEODE-26
> Project: Geode
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0-incubating
> Environment: Any Gradle capable env for building Apache Geode.
>Reporter: John Blum
>Assignee: Anthony Baker
>Priority: Critical
> Labels: ApacheGeode, Gradle, Repositories, build.gradle,
> mavenLocal()
> Fix For: 1.0.0-incubating.M2
>
>
> In the
> [build.gradle|https://github.com/apache/incubator-geode/blob/master/build.gradle#L9-10]
> file of the _Apache Geode_ project, the {{repositories}} declaration
> inappropriately contains {{mavenLocal()}}.
> The problem with this is, if developers contributing patches to the _Apache
> Geode_ codebase inadvertently include a "local" dependency to the
> dependencies defined in Geode's {{build.gradle}} file(s), then Geode will
> build locally but not when the patch is submitted and Geode's build
> infrastructure runs the same build with the code changes dependent on the
> (possibly) non-existent, non-resolvable dependency, because, it only exists
> in the developers "local" Maven (env) repository ({{~/.m2/repository}}).
> There are other preferred ways in which users can specify the use of
> {{mavenLocal()}} to affect their work _Apache Geode_ codebase/build without
> modifying the actual _Apache Geode_ {{build.gradle}} file.
> For instance, a developer can created a {{~/.gradle/init.gradle}} script to
> tweak "available" Repositories, like so...
> {code:xml}
> allprojects {
> repositories {
> mavenLocal()
> maven { url "http://maven.domain.com/path/to/another/maven/repo"}
>// etc...
> }
> }
> {code}
> See the [Gradle documentation on
> init.scripts|https://docs.gradle.org/current/userguide/init_scripts.html] for
> more details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-608) Integrate RAT into build
[ https://issues.apache.org/jira/browse/GEODE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-608: --- Sprint: (was: 1.0.0-incubating.M2) > Integrate RAT into build > > > Key: GEODE-608 > URL: https://issues.apache.org/jira/browse/GEODE-608 > Project: Geode > Issue Type: Improvement > Components: build >Affects Versions: 1.0.0-incubating >Reporter: Anthony Baker >Assignee: Anthony Baker > Fix For: 1.0.0-incubating.M1 > > > We need to ensure license requirements are met. See discussion at > http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201511.mbox/%3cCA+ULb+uLyB9_3QSA+qk5UZ5E8idXdCd=1z+9zr9y2c6n1vo...@mail.gmail.com%3e > Gradle plugin available at > https://plugins.gradle.org/plugin/org.nosphere.apache.rat -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-907) Remove JSON code from pulse
[ https://issues.apache.org/jira/browse/GEODE-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-907: --- Sprint: 1.0.0-incubating.M3 > Remove JSON code from pulse > --- > > Key: GEODE-907 > URL: https://issues.apache.org/jira/browse/GEODE-907 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Anthony Baker >Assignee: Jens Deppe > Fix For: 1.0.0-incubating.M2 > > > The com.vmware.gemfire.tools.pulse.internal.json package contains the JSON > parser source. We should remove this code in favor of a binary dependency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-904) Update LICENSE for BSD/MIT dependencies
[
https://issues.apache.org/jira/browse/GEODE-904?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-904:
---
Sprint: 1.0.0-incubating.M3
> Update LICENSE for BSD/MIT dependencies
> ---
>
> Key: GEODE-904
> URL: https://issues.apache.org/jira/browse/GEODE-904
> Project: Geode
> Issue Type: Bug
> Components: docs
>Reporter: Anthony Baker
>Assignee: Anthony Baker
> Fix For: 1.0.0-incubating.M2
>
>
> The following files need to be listed in the LICENSE:
> {noformat}
> - ANSIBuffer (BSD) [1]
> - font awesome (front are SIL and css is MIT) [2]
> - normalise.css (MIT) [3]
> - bootstrap (MIT) [3]
> - boot flat (MIT) [4]
> - headjs (MIT) [5]
> - iCheck (MIT) [6]
> - html5shiv (MIT) [7]
> - respond (MIT) [8]
> - polyfill (MIT/BSD) [8]
> - InternalDataSerializer.java [9] contains code from BSD license protobuf
> that should be in license
> 1.
> ./gemfire-core/src/main/java/com/gemstone/gemfire/management/internal/cli/shell/jline/ANSIBuffer.java
> 2. ./gemfire-site/website/content/font/*
> 3. ./gemfire-site/website/content/bootstrap/bootstrap.min.css
> 4. ./gemfire-site/website/content/css/bootflat*
> 5. ./gemfire-site/website/content/js/head.js
> 6. ./gemfire-site/website/content/js/jquery.icheck.js
> 7. ./gemfire-site/website/content/js/html5shiv.js
> 8. ./gemfire-site/website/content/js/respond.min.js
> 9
> ./gemfire-core/src/main/java/com/gemstone/gemfire/internal/InternalDataSerializer.java
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-991) LuceneFunction is not marked as an internal function
[ https://issues.apache.org/jira/browse/GEODE-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-991: --- Sprint: (was: 1.0.0-incubating.M2) > LuceneFunction is not marked as an internal function > > > Key: GEODE-991 > URL: https://issues.apache.org/jira/browse/GEODE-991 > Project: Geode > Issue Type: Bug > Components: extensions >Affects Versions: 1.0.0-incubating.M1 >Reporter: Dan Smith >Assignee: Dan Smith > Fix For: 1.0.0-incubating.M2 > > > LuceneFunction shows up in the output of list functions from gfsh. It should > extend the InternalEntity marker interface. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-26) Apache Geode 'build.gradle' inappropriately declares mavenLocal() in Repository declarations.
[
https://issues.apache.org/jira/browse/GEODE-26?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-26:
--
Sprint: 1.0.0-incubating.M3
> Apache Geode 'build.gradle' inappropriately declares mavenLocal() in
> Repository declarations.
> -
>
> Key: GEODE-26
> URL: https://issues.apache.org/jira/browse/GEODE-26
> Project: Geode
> Issue Type: Bug
> Components: build
>Affects Versions: 1.0.0-incubating
> Environment: Any Gradle capable env for building Apache Geode.
>Reporter: John Blum
>Assignee: Anthony Baker
>Priority: Critical
> Labels: ApacheGeode, Gradle, Repositories, build.gradle,
> mavenLocal()
> Fix For: 1.0.0-incubating.M2
>
>
> In the
> [build.gradle|https://github.com/apache/incubator-geode/blob/master/build.gradle#L9-10]
> file of the _Apache Geode_ project, the {{repositories}} declaration
> inappropriately contains {{mavenLocal()}}.
> The problem with this is, if developers contributing patches to the _Apache
> Geode_ codebase inadvertently include a "local" dependency to the
> dependencies defined in Geode's {{build.gradle}} file(s), then Geode will
> build locally but not when the patch is submitted and Geode's build
> infrastructure runs the same build with the code changes dependent on the
> (possibly) non-existent, non-resolvable dependency, because, it only exists
> in the developers "local" Maven (env) repository ({{~/.m2/repository}}).
> There are other preferred ways in which users can specify the use of
> {{mavenLocal()}} to affect their work _Apache Geode_ codebase/build without
> modifying the actual _Apache Geode_ {{build.gradle}} file.
> For instance, a developer can created a {{~/.gradle/init.gradle}} script to
> tweak "available" Repositories, like so...
> {code:xml}
> allprojects {
> repositories {
> mavenLocal()
> maven { url "http://maven.domain.com/path/to/another/maven/repo"}
>// etc...
> }
> }
> {code}
> See the [Gradle documentation on
> init.scripts|https://docs.gradle.org/current/userguide/init_scripts.html] for
> more details.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-835) Replace joptsimple source with a binary dependency
[ https://issues.apache.org/jira/browse/GEODE-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-835: --- Sprint: 1.0.0-incubating.M3 > Replace joptsimple source with a binary dependency > -- > > Key: GEODE-835 > URL: https://issues.apache.org/jira/browse/GEODE-835 > Project: Geode > Issue Type: Bug > Components: build, gfsh >Reporter: Anthony Baker >Assignee: Kirk Lund > Fix For: 1.0.0-incubating.M3 > > Attachments: joptsimple.patch > > > The gemfire-jopsimple folder contains modified source code from the > joptsimple library. We should replace this with a binary dependency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-77) Replace JGroups 2.2.9
[ https://issues.apache.org/jira/browse/GEODE-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-77: -- Sprint: (was: 1.0.0-incubating.M2) > Replace JGroups 2.2.9 > - > > Key: GEODE-77 > URL: https://issues.apache.org/jira/browse/GEODE-77 > Project: Geode > Issue Type: Bug >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Blocker > Fix For: 1.0.0-incubating.M1 > > Attachments: > GEODE-MembershipManagerFunctionalSpecification-130715-1604-29054.pdf > > > The JGroups 2.2.9 sources that are currently included in Geode must be > replaced in order for Geode to leave incubation. A wiki document has been > created to investigate alternatives. > https://cwiki.apache.org/confluence/display/GEODE/Replacing+JGroups+2.2.9 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-52) Remove @author tags from Java source
[ https://issues.apache.org/jira/browse/GEODE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-52: -- Sprint: (was: 1.0.0-incubating.M2) > Remove @author tags from Java source > > > Key: GEODE-52 > URL: https://issues.apache.org/jira/browse/GEODE-52 > Project: Geode > Issue Type: Bug >Reporter: Jakob Homan >Assignee: Sai Boorlagadda > Fix For: 1.0.0-incubating.M2 > > > Apache generally frowns on @author tags (as they imply ownership of the code > by a single individual, see > https://blogs.oracle.com/ahe/entry/coding_conventions_and_attribution [best > asf link is not working, annoyingly] and > https://cwiki.apache.org/confluence/display/AVRO/How+To+Contribute as an > example) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-610) Review Geode's LICENSE & NOTICE File(s)
[ https://issues.apache.org/jira/browse/GEODE-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-610: --- Sprint: 1.0.0-incubating.M3 > Review Geode's LICENSE & NOTICE File(s) > --- > > Key: GEODE-610 > URL: https://issues.apache.org/jira/browse/GEODE-610 > Project: Geode > Issue Type: Task > Components: general >Affects Versions: 1.0.0-incubating >Reporter: Niall Pemberton >Assignee: Anthony Baker > Fix For: 1.0.0-incubating.M1 > > Attachments: Geode-Dependency-License-Review-2015-11-28.csv, > Geode-Source-License-Review-2015-11-28.csv, NOTICE, NOTICE-2, NOTICE-3.txt, > netty-4.0.33.Final-NOTICE.txt, spring-core-3.2.12.RELEASE-notice.txt > > > Need to review Geode's LICENSE & NOTICE File(s). > Guide on these files is available here: > - http://www.apache.org/dev/licensing-howto.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-562) Upgrade commons collections to v3.2.2
[ https://issues.apache.org/jira/browse/GEODE-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-562: --- Sprint: 1.0.0-incubating.M3 > Upgrade commons collections to v3.2.2 > - > > Key: GEODE-562 > URL: https://issues.apache.org/jira/browse/GEODE-562 > Project: Geode > Issue Type: Bug >Reporter: Anthony Baker >Assignee: Jason Huynh > Fix For: 1.0.0-incubating.M2 > > > The commons-collections jar v3.2.1 is present on the classpath as part of the > hdfs integration (see GEODE-10). We need to upgrade to version 3.2.2 due to > COLLECTIONS-580. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-914) Review NOTICE (again)
[ https://issues.apache.org/jira/browse/GEODE-914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-914: --- Sprint: 1.0.0-incubating.M3 > Review NOTICE (again) > - > > Key: GEODE-914 > URL: https://issues.apache.org/jira/browse/GEODE-914 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Anthony Baker >Assignee: Anthony Baker > Fix For: 1.0.0-incubating.M2 > > > Thanks to great feedback from IPMC on the general@ list we have a better idea > of how to construct the NOTICE file. Please review the following threads and > linked docs: > http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3c7ac725d7-ecec-45ff-95ae-bd77d1b18...@pivotal.io%3e > http://mail-archives.apache.org/mod_mbox/incubator-general/201601.mbox/%3cCADY20s5nLc9zLKoNYf_8W8vf+Q6ri=-utanuaxzgorbysxw...@mail.gmail.com%3e > https://nifi.apache.org/licensing-guide.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-946) Source and javadoc artifacts from modules have inconsistent locations
[
https://issues.apache.org/jira/browse/GEODE-946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-946:
---
Sprint: 1.0.0-incubating.M3
> Source and javadoc artifacts from modules have inconsistent locations
> -
>
> Key: GEODE-946
> URL: https://issues.apache.org/jira/browse/GEODE-946
> Project: Geode
> Issue Type: Bug
> Components: extensions
>Reporter: Jens Deppe
>Assignee: Jens Deppe
> Fix For: 1.0.0-incubating.M2
>
>
> The current build process for the modules create artifacts as:
> {noformat}
> extensions> find gemfire-modules/build/libs/
> gemfire-modules/build/libs/
> gemfire-modules/build/libs/gemfire-modules-1.0.0-incubating-SNAPSHOT.jar
> gemfire-modules/build/libs/extensions
> gemfire-modules/build/libs/extensions/gemfire-modules-1.0.0-incubating-SNAPSHOT-sources.jar
> gemfire-modules/build/libs/extensions/gemfire-modules-1.0.0-incubating-SNAPSHOT-javadoc.jar
> {noformat}
> Both the sources and javadoc jars should be placed directly in {{libs/}} and
> not in {{libs/extensions}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-12) Merge Pulse Source Code
[ https://issues.apache.org/jira/browse/GEODE-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-12: -- Sprint: 1.0.0-incubating.M3 > Merge Pulse Source Code > --- > > Key: GEODE-12 > URL: https://issues.apache.org/jira/browse/GEODE-12 > Project: Geode > Issue Type: New Feature > Components: management >Reporter: Dan Smith >Assignee: Jinmei Liao > Labels: starter > Fix For: 1.0.0-incubating.M2 > > > Pulse is a web application for monitoring a Geode cluster. Pivotal would like > to contribute pulse to the Geode project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-902) Remove Apache header from MX4JModelMBean.java
[ https://issues.apache.org/jira/browse/GEODE-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-902: --- Sprint: (was: 1.0.0-incubating.M2) > Remove Apache header from MX4JModelMBean.java > - > > Key: GEODE-902 > URL: https://issues.apache.org/jira/browse/GEODE-902 > Project: Geode > Issue Type: Bug > Components: jmx >Reporter: Anthony Baker >Assignee: Anthony Baker > Fix For: 1.0.0-incubating.M2 > > > MX4JModelMBean.java has an Apache header but should not as it is under the > MX4J license. Also, we need to handle this appropriately in LICENSE / NOTICE. > See http://mx4j.sourceforge.net/docs/ch01s06.html. > Discussion thread: > http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3ca44698bc-a87b-48e5-bdf2-29c1a1814...@classsoftware.com%3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-18) Initial Code Cleanup
[ https://issues.apache.org/jira/browse/GEODE-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-18: -- Sprint: (was: 1.0.0-incubating.M2) > Initial Code Cleanup > > > Key: GEODE-18 > URL: https://issues.apache.org/jira/browse/GEODE-18 > Project: Geode > Issue Type: Task > Components: general >Affects Versions: 1.0.0-incubating >Reporter: Niall Pemberton >Assignee: Dick Cavender > Fix For: 1.0.0-incubating.M1 > > Attachments: > 0001-Replace-Pivotal-License-Header-with-Apache-License.patch, > 0002-Add-Missing-Apache-License-headers.patch, > 0003-Remove-Pivotal-VMWare-AsIs-License-and-add-ASF-Licen.patch, > 0004-Add-ASF-License-Header-to-scala-files.patch, > 0005-Add-ASF-License-Header-to-XML-files.patch, > 0006-Add-ASF-License-Header-to-DTD-XSD-files.patch, > 0007-Add-ASF-License-Header-to-HTML-files.patch, > 0008-Change-Swagger-ApiInfo-from-Pivotal-Gemfire-to-Apach.patch, > 0009-Add-Update-ASF-License-to-java-files.patch, > 0010-Add-ASF-License-to-html-xml-xsd-dtd-files.patch, > geode-rat-excludes-2015-10-19.txt, geode-rat-excludes-2015-10-24.txt, > geode-rat-excludes-2015-11-22.txt, geode-rat-report-2015-05-11.txt, > geode-rat-report-2015-05-17.txt, geode-rat-report-2015-10-19.txt, > geode-rat-report-2015-10-24.txt, geode-rat-report-2015-11-17.txt, > geode-rat-report-2015-11-22.txt > > > Please see the Incubator guide: > * http://incubator.apache.org/guides/mentor.html#initial-clean-up > Source & Notice File policy: > * http://www.apache.org/legal/src-headers.html > Apache RAT is a tool that can help with source file headers: > * http://creadur.apache.org/rat/ -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-562) Upgrade commons collections to v3.2.2
[ https://issues.apache.org/jira/browse/GEODE-562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-562: --- Sprint: (was: 1.0.0-incubating.M2) > Upgrade commons collections to v3.2.2 > - > > Key: GEODE-562 > URL: https://issues.apache.org/jira/browse/GEODE-562 > Project: Geode > Issue Type: Bug >Reporter: Anthony Baker >Assignee: Jason Huynh > Fix For: 1.0.0-incubating.M2 > > > The commons-collections jar v3.2.1 is present on the classpath as part of the > hdfs integration (see GEODE-10). We need to upgrade to version 3.2.2 due to > COLLECTIONS-580. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-386) Change xsd namespace to apache
[
https://issues.apache.org/jira/browse/GEODE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-386:
---
Sprint: (was: 1.0.0-incubating.M2)
> Change xsd namespace to apache
> --
>
> Key: GEODE-386
> URL: https://issues.apache.org/jira/browse/GEODE-386
> Project: Geode
> Issue Type: Improvement
> Components: configuration, docs
>Reporter: Dan Smith
>Assignee: Jens Deppe
> Fix For: 1.0.0-incubating.M2
>
>
> The format cache.xml file for geode is currently specified by a xsd called
> cache-9.0.xsd. This xsd has a pivotal.io namespace. It should have an apache
> namespace and be hosted on apache infastructure.
> {code:xml}
> targetNamespace="http://schema.pivotal.io/gemfire/cache";
> xmlns:gf="http://schema.pivotal.io/gemfire/cache";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> elementFormDefault="qualified"
> attributeFormDefault="unqualified"
> version="9.0">
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-54) Missing javadocs
[ https://issues.apache.org/jira/browse/GEODE-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-54: -- Sprint: (was: 1.0.0-incubating.M2) > Missing javadocs > > > Key: GEODE-54 > URL: https://issues.apache.org/jira/browse/GEODE-54 > Project: Geode > Issue Type: Improvement > Components: build, docs, general, web-content >Reporter: William Markito Oliveira >Assignee: Dave Barnes > Fix For: 1.0.0-incubating.M2 > > > The current build process is not generating javadocs and once they're > generated it's still be defined where to host the pages. > Current Geode docs are hosted at http://geode-docs.cfapps.io/ but javadocs > can be part of that or be hosted under geode.incubator.apache.org. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-776) Add public KEYS to Apache Geode repo.
[ https://issues.apache.org/jira/browse/GEODE-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-776: --- Sprint: 1.0.0-incubating.M3 > Add public KEYS to Apache Geode repo. > - > > Key: GEODE-776 > URL: https://issues.apache.org/jira/browse/GEODE-776 > Project: Geode > Issue Type: Task >Reporter: Nitin Lamba >Assignee: Anthony Baker > Fix For: 1.0.0-incubating.M1 > > Attachments: KEYS, KEYS > > > As per release requirement, please comment with your public keys so that a > KEYS file can be created in the repo. Few references below: > http://www.apache.org/dist/ant/KEYS > https://dist.apache.org/repos/dist/release/bigtop/KEYS -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-907) Remove JSON code from pulse
[ https://issues.apache.org/jira/browse/GEODE-907?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-907: --- Sprint: (was: 1.0.0-incubating.M2) > Remove JSON code from pulse > --- > > Key: GEODE-907 > URL: https://issues.apache.org/jira/browse/GEODE-907 > Project: Geode > Issue Type: Improvement > Components: management >Reporter: Anthony Baker >Assignee: Jens Deppe > Fix For: 1.0.0-incubating.M2 > > > The com.vmware.gemfire.tools.pulse.internal.json package contains the JSON > parser source. We should remove this code in favor of a binary dependency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-905) HLL classes should preserve original source header
[ https://issues.apache.org/jira/browse/GEODE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-905: --- Sprint: (was: 1.0.0-incubating.M2) > HLL classes should preserve original source header > -- > > Key: GEODE-905 > URL: https://issues.apache.org/jira/browse/GEODE-905 > Project: Geode > Issue Type: Bug >Reporter: Anthony Baker >Assignee: Swapnil Bawaskar > Fix For: 1.0.0-incubating.M2 > > > Classes in the > gemfire-core/src/main/java/com/gemstone/gemfire/internal/redis/executor/hll/*.java > package have 2 source headers. We should preserve the original header and > remove the extra. We should also explore if we need to add anything to the > LICENSE or NOTICE for this bundled source dependency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-815) RC Feedback: Fix LICENSE and NOTICE files
[ https://issues.apache.org/jira/browse/GEODE-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-815: --- Sprint: 1.0.0-incubating.M3 > RC Feedback: Fix LICENSE and NOTICE files > - > > Key: GEODE-815 > URL: https://issues.apache.org/jira/browse/GEODE-815 > Project: Geode > Issue Type: Task >Affects Versions: 1.0.0-incubating.M1 >Reporter: Nitin Lamba >Assignee: Anthony Baker > Fix For: 1.0.0-incubating.M1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-824) Failure from JGroupsMessengerJUnitTest.testMulticastTest
[
https://issues.apache.org/jira/browse/GEODE-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-824:
---
Sprint: 1.0.0-incubating.M3
> Failure from JGroupsMessengerJUnitTest.testMulticastTest
>
>
> Key: GEODE-824
> URL: https://issues.apache.org/jira/browse/GEODE-824
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Bruce Schuchardt
> Labels: ci
> Fix For: 1.0.0-incubating.M2
>
>
> This test fails consistently on my ubuntu 15.10 machine. It looks like this
> was introduced in b826b4b0077dc159cbcee68775cc197b025d5586
> I'm running with 27f9c0e8775d50981241a67d792abb3e94adb939.
> {noformat}
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at org.junit.Assert.assertFalse(Assert.java:74)
> at
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessengerJUnitTest.testMulticastTest(JGroupsMessengerJUnitTest.java:818)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-52) Remove @author tags from Java source
[ https://issues.apache.org/jira/browse/GEODE-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-52: -- Sprint: 1.0.0-incubating.M3 > Remove @author tags from Java source > > > Key: GEODE-52 > URL: https://issues.apache.org/jira/browse/GEODE-52 > Project: Geode > Issue Type: Bug >Reporter: Jakob Homan >Assignee: Sai Boorlagadda > Fix For: 1.0.0-incubating.M2 > > > Apache generally frowns on @author tags (as they imply ownership of the code > by a single individual, see > https://blogs.oracle.com/ahe/entry/coding_conventions_and_attribution [best > asf link is not working, annoyingly] and > https://cwiki.apache.org/confluence/display/AVRO/How+To+Contribute as an > example) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-901) Remove invalid source headers
[
https://issues.apache.org/jira/browse/GEODE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-901:
---
Sprint: 1.0.0-incubating.M3
> Remove invalid source headers
> -
>
> Key: GEODE-901
> URL: https://issues.apache.org/jira/browse/GEODE-901
> Project: Geode
> Issue Type: Bug
>Reporter: Anthony Baker
>Assignee: Sai Boorlagadda
> Fix For: 1.0.0-incubating.M2
>
>
> ResultsBagJUnitTest contains an invalid header that should be removed.
> {code}
> //
> // ResultsBagJUnitTest.java
> // gemfire
> //
> // Created by Eric Zoerner on 2/13/08.
> // Copyright 2008 __MyCompanyName__. All rights reserved.
> //
> {code}
> Also, QueryFromClauseCanonicalizationJUnitTest.java has this comment which
> should be removed:
> {code}
> /*
>*
>* Copyright (C) GemStone Systems, Inc. 2000-2004. All Rights Reserved.
>*
>*
>*/
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-33) Create project examples
[ https://issues.apache.org/jira/browse/GEODE-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-33: -- Sprint: (was: 1.0.0-incubating.M2) > Create project examples > --- > > Key: GEODE-33 > URL: https://issues.apache.org/jira/browse/GEODE-33 > Project: Geode > Issue Type: Improvement > Components: docs, general, web-content >Reporter: William Markito Oliveira > Labels: gsoc2016 > Fix For: 1.0.0-incubating.M3 > > > Currently the project doesn't have examples. > Ideally it should be created as a separated project, include tests and be > used as part of build process tests as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-902) Remove Apache header from MX4JModelMBean.java
[ https://issues.apache.org/jira/browse/GEODE-902?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-902: --- Sprint: 1.0.0-incubating.M3 > Remove Apache header from MX4JModelMBean.java > - > > Key: GEODE-902 > URL: https://issues.apache.org/jira/browse/GEODE-902 > Project: Geode > Issue Type: Bug > Components: jmx >Reporter: Anthony Baker >Assignee: Anthony Baker > Fix For: 1.0.0-incubating.M2 > > > MX4JModelMBean.java has an Apache header but should not as it is under the > MX4J license. Also, we need to handle this appropriately in LICENSE / NOTICE. > See http://mx4j.sourceforge.net/docs/ch01s06.html. > Discussion thread: > http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3ca44698bc-a87b-48e5-bdf2-29c1a1814...@classsoftware.com%3e -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-874) v1.0.0-incubating.M1.RC2: Text file errors in the source distribution
[ https://issues.apache.org/jira/browse/GEODE-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-874: --- Sprint: 1.0.0-incubating.M3 > v1.0.0-incubating.M1.RC2: Text file errors in the source distribution > - > > Key: GEODE-874 > URL: https://issues.apache.org/jira/browse/GEODE-874 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Kenneth Howe >Assignee: Karen Smoler Miller > Fix For: 1.0.0-incubating.M2 > > > gradlew script is not included in the Geode release packages, but it is > called out in command examples in the following text files in the release > source distribution: > COMPILING.txt > RUNNING.txt > docker/Dockerfile > gemfire-spark-connector/doc/1_building.md > The easy fix is to change "gradlew" to "gradle" in affected files and include > a requirement for the user to install gradle from gradle.org. > There was a similar issue with README.md that was fixed for RC2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-824) Failure from JGroupsMessengerJUnitTest.testMulticastTest
[
https://issues.apache.org/jira/browse/GEODE-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-824:
---
Sprint: (was: 1.0.0-incubating.M2)
> Failure from JGroupsMessengerJUnitTest.testMulticastTest
>
>
> Key: GEODE-824
> URL: https://issues.apache.org/jira/browse/GEODE-824
> Project: Geode
> Issue Type: Bug
>Reporter: Dan Smith
>Assignee: Bruce Schuchardt
> Labels: ci
> Fix For: 1.0.0-incubating.M2
>
>
> This test fails consistently on my ubuntu 15.10 machine. It looks like this
> was introduced in b826b4b0077dc159cbcee68775cc197b025d5586
> I'm running with 27f9c0e8775d50981241a67d792abb3e94adb939.
> {noformat}
> java.lang.AssertionError
> at org.junit.Assert.fail(Assert.java:86)
> at org.junit.Assert.assertTrue(Assert.java:41)
> at org.junit.Assert.assertFalse(Assert.java:64)
> at org.junit.Assert.assertFalse(Assert.java:74)
> at
> com.gemstone.gemfire.distributed.internal.membership.gms.messenger.JGroupsMessengerJUnitTest.testMulticastTest(JGroupsMessengerJUnitTest.java:818)
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-54) Missing javadocs
[ https://issues.apache.org/jira/browse/GEODE-54?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-54: -- Sprint: 1.0.0-incubating.M3 > Missing javadocs > > > Key: GEODE-54 > URL: https://issues.apache.org/jira/browse/GEODE-54 > Project: Geode > Issue Type: Improvement > Components: build, docs, general, web-content >Reporter: William Markito Oliveira >Assignee: Dave Barnes > Fix For: 1.0.0-incubating.M2 > > > The current build process is not generating javadocs and once they're > generated it's still be defined where to host the pages. > Current Geode docs are hosted at http://geode-docs.cfapps.io/ but javadocs > can be part of that or be hosted under geode.incubator.apache.org. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-944) ServerLauncherJUnitTest fails when ISP redirects DNS failures
[
https://issues.apache.org/jira/browse/GEODE-944?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-944:
---
Sprint: 1.0.0-incubating.M3
> ServerLauncherJUnitTest fails when ISP redirects DNS failures
> -
>
> Key: GEODE-944
> URL: https://issues.apache.org/jira/browse/GEODE-944
> Project: Geode
> Issue Type: Bug
> Components: management
>Reporter: Dan Smith
>Assignee: Jianxia Chen
> Fix For: 1.0.0-incubating.M2
>
>
> This test fails when using a DNS server that redirects DNS lookup failures to
> an ISP's search page.
> {noformat}
> om.gemstone.gemfire.distributed.LocatorLauncherJUnitTest >
> testSetBindAddressToUnknownHost FAILED
> java.lang.AssertionError: Expected exception:
> java.lang.IllegalArgumentException
> com.gemstone.gemfire.distributed.ServerLauncherJUnitTest >
> testSetServerBindAddressToUnknownHost FAILED
> java.lang.AssertionError: Expected exception:
> java.lang.IllegalArgumentException
> {noformat}
> The test is expecting to see an UnknownHostException, but because the ISP
> returns a real IP address rather than the expected DNS lookup failure, the
> test doesn't see the exception.
> We could probably just Use junit's Assume to cause these tests to get skipped
> in this environment.
> See this email thread for more details:
> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3CCAOqetn_FTeV9ee4R8mkg4Y%3D8a%3DjedgfdOSjDxcnj2N7W02maCw%40mail.gmail.com%3E
> A little more information on DNS hijacking:
> http://www.dnsknowledge.com/whatis/nxdomain-non-existent-domain-2/
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-945) Javadoc references to javax.transaction classes are causing build warnings
[
https://issues.apache.org/jira/browse/GEODE-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-945:
---
Sprint: 1.0.0-incubating.M3
> Javadoc references to javax.transaction classes are causing build warnings
> --
>
> Key: GEODE-945
> URL: https://issues.apache.org/jira/browse/GEODE-945
> Project: Geode
> Issue Type: Bug
> Components: build
>Reporter: Kirk Lund
>Assignee: Dan Smith
> Fix For: 1.0.0-incubating.M2
>
>
> Javadoc references to javax.transaction classes are causing build warnings.
> {noformat}
> :pivotalgf-assembly:docsC:\dev\gemfire_CLEAN\open\gemfire-core\src\main\java\com\gemstone\gemfire\cache\FailedSynchronizationException.java:33:
> warning - Tag @see: reference not found:
> javax.transaction.UserTransaction#setRollbackOnly
> C:\dev\gemfire_CLEAN\open\gemfire-core\src\main\java\com\gemstone\gemfire\cache\FailedSynchronizationException.java:33:
> warning - Tag @see: reference not found:
> javax.transaction.Transaction#registerSynchronization
> C:\dev\gemfire_CLEAN\open\gemfire-core\src\main\java\com\gemstone\gemfire\cache\FailedSynchronizationException.java:33:
> warning - Tag @see: reference not found: javax.transaction.Status
> C:\dev\gemfire_CLEAN\open\gemfire-core\src\main\java\com\gemstone\gemfire\cache\SynchronizationCommitConflictException.java:27:
> warning - Tag @see: reference not found:
> javax.transaction.UserTransaction#commit
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-53) Update and fix pages in the website
[ https://issues.apache.org/jira/browse/GEODE-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-53: -- Sprint: 1.0.0-incubating.M3 > Update and fix pages in the website > --- > > Key: GEODE-53 > URL: https://issues.apache.org/jira/browse/GEODE-53 > Project: Geode > Issue Type: Improvement > Components: web-content >Reporter: William Markito Oliveira >Assignee: William Markito Oliveira > Fix For: 1.0.0-incubating.M1 > > > There are some pages in the website that may need attention and updates. > Here is a list of the main pages and initial ideas that can improve and fix > it: > Getting Started: > - How to section is not well formatted and need a better organization. > - Learn the Basics (Videos) > - Not sure it should be listed here and given that it's all GemFire it's a > bit confusing still. > - Download Geode link should be removed from this page since it's already in > the top. > - Understand some examples section should also go somewhere > - Documentation should be a direct link from the main menu and not the last > thing of this page. > Community > - Conferences need to be updated ad need to work on some automation here to > simplify things. > - Systems (JIRA, Wiki) and mailing lists links should be more accessible and > just listed - not in the middle of text or phrases. Also they should be moved > to the Contribute (or How to Contribute) page. > - Don't know why Project History is here, we should move this to a main > "About" page. > Contribute > - This page starts with text about GemFire/Geode history - Which IHMO should > also be moved to the "About" page or something like that. As well as the > incubator proposal link, etc. > - The contribute page should probably only have sections about: What can be > contributions and how to do them - Code, documentation, bugs, answers on > StackOverflow, etc. > Download > Since we don't have releases yet, as per ASF policy we can point them to the > GitHub repo and I'd say we should probably copy the very basics steps to > build the project here so people can start, with a pointer for the Wiki for > detailed instructions. Something like: git clone, build, gfsh.. > - Documentation section on this page should be moved to it's own page. > - Remove the Coming Soon section about the VM and include a pointer to the > Docker image on Docker Hub. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-627) Generate source artifacts from gradle build
[ https://issues.apache.org/jira/browse/GEODE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-627: --- Sprint: (was: 1.0.0-incubating.M2) > Generate source artifacts from gradle build > --- > > Key: GEODE-627 > URL: https://issues.apache.org/jira/browse/GEODE-627 > Project: Geode > Issue Type: Task >Reporter: Nitin Lamba >Assignee: Anthony Baker >Priority: Critical > Fix For: 1.0.0-incubating.M1 > > > The current gradle build generated in 'gemfire-assembly' does not include > source artifacts. As part of the release process, source distribution task > needs to be added. > Suggested by Niall Pemberton on Dec/02/2015. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-776) Add public KEYS to Apache Geode repo.
[ https://issues.apache.org/jira/browse/GEODE-776?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-776: --- Sprint: (was: 1.0.0-incubating.M2) > Add public KEYS to Apache Geode repo. > - > > Key: GEODE-776 > URL: https://issues.apache.org/jira/browse/GEODE-776 > Project: Geode > Issue Type: Task >Reporter: Nitin Lamba >Assignee: Anthony Baker > Fix For: 1.0.0-incubating.M1 > > Attachments: KEYS, KEYS > > > As per release requirement, please comment with your public keys so that a > KEYS file can be created in the repo. Few references below: > http://www.apache.org/dist/ant/KEYS > https://dist.apache.org/repos/dist/release/bigtop/KEYS -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-32) Complete wiki page for release process
[ https://issues.apache.org/jira/browse/GEODE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-32: -- Sprint: 1.0.0-incubating.M3 > Complete wiki page for release process > -- > > Key: GEODE-32 > URL: https://issues.apache.org/jira/browse/GEODE-32 > Project: Geode > Issue Type: Task > Components: web-content >Reporter: William Markito Oliveira >Assignee: Nitin Lamba >Priority: Minor > Fix For: 1.0.0-incubating.M1 > > > The release process needs to be finalized and documented in the following > wiki page. > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=57311453 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[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
]
William Markito Oliveira updated GEODE-823:
---
Sprint: (was: 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
> Components: build
>Affects Versions: 1.0.0-incubating.M1
>Reporter: Nitin Lamba
> Fix For: 1.0.0-incubating.M3
>
>
> From [~niall.pember...@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)
[jira] [Updated] (GEODE-12) Merge Pulse Source Code
[ https://issues.apache.org/jira/browse/GEODE-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-12: -- Sprint: (was: 1.0.0-incubating.M2) > Merge Pulse Source Code > --- > > Key: GEODE-12 > URL: https://issues.apache.org/jira/browse/GEODE-12 > Project: Geode > Issue Type: New Feature > Components: management >Reporter: Dan Smith >Assignee: Jinmei Liao > Labels: starter > Fix For: 1.0.0-incubating.M2 > > > Pulse is a web application for monitoring a Geode cluster. Pivotal would like > to contribute pulse to the Geode project. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-27) Apache Geode POM file(s) are incorrect!
[
https://issues.apache.org/jira/browse/GEODE-27?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-27:
--
Sprint: (was: 1.0.0-incubating.M2)
> Apache Geode POM file(s) are incorrect!
> ---
>
> Key: GEODE-27
> URL: https://issues.apache.org/jira/browse/GEODE-27
> Project: Geode
> Issue Type: Bug
> Components: build, general
>Affects Versions: 1.0.0-incubating
> Environment: Apache Geode in Maven or Gradle-based applications.
>Reporter: John Blum
>Assignee: Dan Smith
>Priority: Critical
> Labels: ApacheGeode, Maven, POM
> Fix For: 1.0.0-incubating.M2
>
> Attachments: gemfire-8.2.0.pom,
> gemfire-core-1.0.0-incubating-SNAPSHOT.pom,
> gemfire-jgroups-1.0.0-incubating-SNAPSHOT.pom,
> gemfire-joptsimple-1.0.0-incubating-SNAPSHOT.pom,
> gemfire-json-1.0.0-incubating-SNAPSHOT.pom,
> geode-core-1.0.0-incubating.M2-SNAPSHOT.pom
>
>
> This JIRA is a followup to [GEODE-23] to note the additional issues that are
> considered
> ["out-of-scope"|http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201505.mbox/ajax/%3CCA%2BULb%2Btfm4LyjwMaB_B7j8WaBNoAYj1%2BkeZSW-pqv0Gdbq2T8g%40mail.gmail.com%3E]
> for [GEODE-23], yet need to be fixed, none-the-less.
> Specifically, the changes include...
> 1. The {{}} declarations need to be cleaned up (reduced).
> Technically, _Apache Geode_ should only require...
> {code:xml}
>
>
> gemstone-release
> GemStone Maven RELEASE Repository
> http://dist.gemstone.com/maven/release
>
> true
> always
>
>
>
> libs-release
> Spring Maven libs-release Repository
> http://repo.spring.io/libs-release
>
>
> {code}
> For instance, the "obscure" *jline-1.0.S2-B.jar* dependency is "resolvable"
> from, for instance...
> http://repo.spring.io/libs-release/net/sourceforge/jline/jline/1.0.S2-B/jline-1.0.S2-B.jar
> NOTE: by default, and unlike Gradle, Maven searches "Maven Central".
> 2. Add proper "scopes", "optional" settings and "exclusions" to the
> dependencies declared in the POM.
> 3. Many of the "explicitly" declared dependencies (e.g. spring-beans) need
> to be removed; Maven will resolve dependencies transitively.
> As an example, _Apache Geode's_ Maven POM file should be very similar to the
> {{Pivotal GemFire}} Maven POM file, as recently updated and validated for
> *GemFire 8.2* (see attached {{gemfire-8.2.0.pom}} file for further details
> and reference). This is particularly important where _Apache Geode_ and
> _Pivotal GemFire_ intersect.
> There maybe other issues with the POM file that need to be included within
> the "scope" of this +bug+ as well and should be included as such, otherwise
> this JIRA should *+not+* be marked "complete".
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-905) HLL classes should preserve original source header
[ https://issues.apache.org/jira/browse/GEODE-905?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-905: --- Sprint: 1.0.0-incubating.M3 > HLL classes should preserve original source header > -- > > Key: GEODE-905 > URL: https://issues.apache.org/jira/browse/GEODE-905 > Project: Geode > Issue Type: Bug >Reporter: Anthony Baker >Assignee: Swapnil Bawaskar > Fix For: 1.0.0-incubating.M2 > > > Classes in the > gemfire-core/src/main/java/com/gemstone/gemfire/internal/redis/executor/hll/*.java > package have 2 source headers. We should preserve the original header and > remove the extra. We should also explore if we need to add anything to the > LICENSE or NOTICE for this bundled source dependency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-611) Remove Dependency on LGPL Licensed Findbugs Annoations
[ https://issues.apache.org/jira/browse/GEODE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-611: --- Sprint: (was: 1.0.0-incubating.M2) > Remove Dependency on LGPL Licensed Findbugs Annoations > -- > > Key: GEODE-611 > URL: https://issues.apache.org/jira/browse/GEODE-611 > Project: Geode > Issue Type: Task > Components: core >Affects Versions: 1.0.0-incubating >Reporter: Niall Pemberton >Assignee: Anthony Baker > Fix For: 1.0.0-incubating.M1 > > > FindBugs Annoations (SuppressWarnings & SuppressFBWarnings) have been used in > 27 files in geode-core and the FindBugs LGPL License is not permitted under > ASF policy: > - http://findbugs.sourceforge.net/ > There is an Apache Licensed "clean room" implementation of the findbugs > annotations[1] and I have asked on the legal-discuss list[2] if theres any > reason this can't be used > [1] https://github.com/stephenc/findbugs-annotations > [2] http://markmail.org/message/ieczgjovzhll76yl -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1025) Remove compile dependency on spring data gemfire/geode
[ https://issues.apache.org/jira/browse/GEODE-1025?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-1025: Sprint: (was: 1.0.0-incubating.M2) > Remove compile dependency on spring data gemfire/geode > -- > > Key: GEODE-1025 > URL: https://issues.apache.org/jira/browse/GEODE-1025 > Project: Geode > Issue Type: Improvement > Components: build >Reporter: Dan Smith >Assignee: Dan Smith > Fix For: 1.0.0-incubating.M2 > > > We have a compile dependency on spring data gemfire in the ServerLauncher > class to support launching a server using a spring data gemfire configuration > instead of a cache.xml file. > That's a good feature to have, but it should be part of spring data gemfire, > not geode. Because of this compile dependency on SDG, we currently have a > circular dependency on SDG -> Geode -> SDG. That makes it difficult to do > things like rename packages in geode (GEODE-37) because SDG is still using > the old packages. > Instead of directly depending on spring data gemfire, we should provide an > extension point that SDG can plug into to override the cache server startup > behavior. > The easiest place way to do this is just to use the java ServiceLoader > mechanism. We can provide an interface for a plugin that replaces startup > behavior of the server. SDG can provide an implementation of this interface. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-884) Update README.md to include steps to build without running all tests.
[ https://issues.apache.org/jira/browse/GEODE-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-884: --- Sprint: 1.0.0-incubating.M3 > Update README.md to include steps to build without running all tests. > - > > Key: GEODE-884 > URL: https://issues.apache.org/jira/browse/GEODE-884 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Udo Kohlmeyer > Fix For: 1.0.0-incubating.M2 > > > Add the steps to the README.md to build GEODE without having to run all tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-610) Review Geode's LICENSE & NOTICE File(s)
[ https://issues.apache.org/jira/browse/GEODE-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-610: --- Sprint: (was: 1.0.0-incubating.M2) > Review Geode's LICENSE & NOTICE File(s) > --- > > Key: GEODE-610 > URL: https://issues.apache.org/jira/browse/GEODE-610 > Project: Geode > Issue Type: Task > Components: general >Affects Versions: 1.0.0-incubating >Reporter: Niall Pemberton >Assignee: Anthony Baker > Fix For: 1.0.0-incubating.M1 > > Attachments: Geode-Dependency-License-Review-2015-11-28.csv, > Geode-Source-License-Review-2015-11-28.csv, NOTICE, NOTICE-2, NOTICE-3.txt, > netty-4.0.33.Final-NOTICE.txt, spring-core-3.2.12.RELEASE-notice.txt > > > Need to review Geode's LICENSE & NOTICE File(s). > Guide on these files is available here: > - http://www.apache.org/dev/licensing-howto.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-884) Update README.md to include steps to build without running all tests.
[ https://issues.apache.org/jira/browse/GEODE-884?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-884: --- Sprint: (was: 1.0.0-incubating.M2) > Update README.md to include steps to build without running all tests. > - > > Key: GEODE-884 > URL: https://issues.apache.org/jira/browse/GEODE-884 > Project: Geode > Issue Type: Improvement > Components: docs >Reporter: Udo Kohlmeyer > Fix For: 1.0.0-incubating.M2 > > > Add the steps to the README.md to build GEODE without having to run all tests. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-991) LuceneFunction is not marked as an internal function
[ https://issues.apache.org/jira/browse/GEODE-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-991: --- Sprint: 1.0.0-incubating.M3 > LuceneFunction is not marked as an internal function > > > Key: GEODE-991 > URL: https://issues.apache.org/jira/browse/GEODE-991 > Project: Geode > Issue Type: Bug > Components: extensions >Affects Versions: 1.0.0-incubating.M1 >Reporter: Dan Smith >Assignee: Dan Smith > Fix For: 1.0.0-incubating.M2 > > > LuceneFunction shows up in the output of list functions from gfsh. It should > extend the InternalEntity marker interface. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-33) Create project examples
[ https://issues.apache.org/jira/browse/GEODE-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-33: -- Sprint: 1.0.0-incubating.M3 > Create project examples > --- > > Key: GEODE-33 > URL: https://issues.apache.org/jira/browse/GEODE-33 > Project: Geode > Issue Type: Improvement > Components: docs, general, web-content >Reporter: William Markito Oliveira > Labels: gsoc2016 > Fix For: 1.0.0-incubating.M3 > > > Currently the project doesn't have examples. > Ideally it should be created as a separated project, include tests and be > used as part of build process tests as well. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-903) Update copyright year in website footer
[ https://issues.apache.org/jira/browse/GEODE-903?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-903: --- Sprint: 1.0.0-incubating.M3 > Update copyright year in website footer > --- > > Key: GEODE-903 > URL: https://issues.apache.org/jira/browse/GEODE-903 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Anthony Baker > Fix For: 1.0.0-incubating.M2 > > > The publication year in the copyright notice should be updated to 2016: > gemfire-site/website/layouts/footer.html -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-901) Remove invalid source headers
[
https://issues.apache.org/jira/browse/GEODE-901?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-901:
---
Sprint: (was: 1.0.0-incubating.M2)
> Remove invalid source headers
> -
>
> Key: GEODE-901
> URL: https://issues.apache.org/jira/browse/GEODE-901
> Project: Geode
> Issue Type: Bug
>Reporter: Anthony Baker
>Assignee: Sai Boorlagadda
> Fix For: 1.0.0-incubating.M2
>
>
> ResultsBagJUnitTest contains an invalid header that should be removed.
> {code}
> //
> // ResultsBagJUnitTest.java
> // gemfire
> //
> // Created by Eric Zoerner on 2/13/08.
> // Copyright 2008 __MyCompanyName__. All rights reserved.
> //
> {code}
> Also, QueryFromClauseCanonicalizationJUnitTest.java has this comment which
> should be removed:
> {code}
> /*
>*
>* Copyright (C) GemStone Systems, Inc. 2000-2004. All Rights Reserved.
>*
>*
>*/
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-815) RC Feedback: Fix LICENSE and NOTICE files
[ https://issues.apache.org/jira/browse/GEODE-815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-815: --- Sprint: (was: 1.0.0-incubating.M2) > RC Feedback: Fix LICENSE and NOTICE files > - > > Key: GEODE-815 > URL: https://issues.apache.org/jira/browse/GEODE-815 > Project: Geode > Issue Type: Task >Affects Versions: 1.0.0-incubating.M1 >Reporter: Nitin Lamba >Assignee: Anthony Baker > Fix For: 1.0.0-incubating.M1 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-77) Replace JGroups 2.2.9
[ https://issues.apache.org/jira/browse/GEODE-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-77: -- Sprint: 1.0.0-incubating.M3 > Replace JGroups 2.2.9 > - > > Key: GEODE-77 > URL: https://issues.apache.org/jira/browse/GEODE-77 > Project: Geode > Issue Type: Bug >Reporter: Bruce Schuchardt >Assignee: Bruce Schuchardt >Priority: Blocker > Fix For: 1.0.0-incubating.M1 > > Attachments: > GEODE-MembershipManagerFunctionalSpecification-130715-1604-29054.pdf > > > The JGroups 2.2.9 sources that are currently included in Geode must be > replaced in order for Geode to leave incubation. A wiki document has been > created to investigate alternatives. > https://cwiki.apache.org/confluence/display/GEODE/Replacing+JGroups+2.2.9 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-835) Replace joptsimple source with a binary dependency
[ https://issues.apache.org/jira/browse/GEODE-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-835: --- Sprint: (was: 1.0.0-incubating.M2) > Replace joptsimple source with a binary dependency > -- > > Key: GEODE-835 > URL: https://issues.apache.org/jira/browse/GEODE-835 > Project: Geode > Issue Type: Bug > Components: build, gfsh >Reporter: Anthony Baker >Assignee: Kirk Lund > Fix For: 1.0.0-incubating.M3 > > Attachments: joptsimple.patch > > > The gemfire-jopsimple folder contains modified source code from the > joptsimple library. We should replace this with a binary dependency. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-876) Add a README file to the binary distribution
[ https://issues.apache.org/jira/browse/GEODE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-876: --- Sprint: (was: 1.0.0-incubating.M2) > Add a README file to the binary distribution > > > Key: GEODE-876 > URL: https://issues.apache.org/jira/browse/GEODE-876 > Project: Geode > Issue Type: Bug >Reporter: Swapnil Bawaskar >Assignee: Sai Boorlagadda > Labels: docs > Fix For: 1.0.0-incubating.M2 > > > The binary distribution is missing README and RUNNING.txt files which are > present in src distribution. > These files should be added to the binary distribution to provide a starting > point for the users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-874) v1.0.0-incubating.M1.RC2: Text file errors in the source distribution
[ https://issues.apache.org/jira/browse/GEODE-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-874: --- Sprint: (was: 1.0.0-incubating.M2) > v1.0.0-incubating.M1.RC2: Text file errors in the source distribution > - > > Key: GEODE-874 > URL: https://issues.apache.org/jira/browse/GEODE-874 > Project: Geode > Issue Type: Bug > Components: docs >Reporter: Kenneth Howe >Assignee: Karen Smoler Miller > Fix For: 1.0.0-incubating.M2 > > > gradlew script is not included in the Geode release packages, but it is > called out in command examples in the following text files in the release > source distribution: > COMPILING.txt > RUNNING.txt > docker/Dockerfile > gemfire-spark-connector/doc/1_building.md > The easy fix is to change "gradlew" to "gradle" in affected files and include > a requirement for the user to install gradle from gradle.org. > There was a similar issue with README.md that was fixed for RC2. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-32) Complete wiki page for release process
[ https://issues.apache.org/jira/browse/GEODE-32?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-32: -- Sprint: (was: 1.0.0-incubating.M2) > Complete wiki page for release process > -- > > Key: GEODE-32 > URL: https://issues.apache.org/jira/browse/GEODE-32 > Project: Geode > Issue Type: Task > Components: web-content >Reporter: William Markito Oliveira >Assignee: Nitin Lamba >Priority: Minor > Fix For: 1.0.0-incubating.M1 > > > The release process needs to be finalized and documented in the following > wiki page. > https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=57311453 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-386) Change xsd namespace to apache
[
https://issues.apache.org/jira/browse/GEODE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-386:
---
Sprint: 1.0.0-incubating.M3
> Change xsd namespace to apache
> --
>
> Key: GEODE-386
> URL: https://issues.apache.org/jira/browse/GEODE-386
> Project: Geode
> Issue Type: Improvement
> Components: configuration, docs
>Reporter: Dan Smith
>Assignee: Jens Deppe
> Fix For: 1.0.0-incubating.M2
>
>
> The format cache.xml file for geode is currently specified by a xsd called
> cache-9.0.xsd. This xsd has a pivotal.io namespace. It should have an apache
> namespace and be hosted on apache infastructure.
> {code:xml}
> targetNamespace="http://schema.pivotal.io/gemfire/cache";
> xmlns:gf="http://schema.pivotal.io/gemfire/cache";
> xmlns:xsd="http://www.w3.org/2001/XMLSchema";
> elementFormDefault="qualified"
> attributeFormDefault="unqualified"
> version="9.0">
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-945) Javadoc references to javax.transaction classes are causing build warnings
[
https://issues.apache.org/jira/browse/GEODE-945?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-945:
---
Sprint: (was: 1.0.0-incubating.M2)
> Javadoc references to javax.transaction classes are causing build warnings
> --
>
> Key: GEODE-945
> URL: https://issues.apache.org/jira/browse/GEODE-945
> Project: Geode
> Issue Type: Bug
> Components: build
>Reporter: Kirk Lund
>Assignee: Dan Smith
> Fix For: 1.0.0-incubating.M2
>
>
> Javadoc references to javax.transaction classes are causing build warnings.
> {noformat}
> :pivotalgf-assembly:docsC:\dev\gemfire_CLEAN\open\gemfire-core\src\main\java\com\gemstone\gemfire\cache\FailedSynchronizationException.java:33:
> warning - Tag @see: reference not found:
> javax.transaction.UserTransaction#setRollbackOnly
> C:\dev\gemfire_CLEAN\open\gemfire-core\src\main\java\com\gemstone\gemfire\cache\FailedSynchronizationException.java:33:
> warning - Tag @see: reference not found:
> javax.transaction.Transaction#registerSynchronization
> C:\dev\gemfire_CLEAN\open\gemfire-core\src\main\java\com\gemstone\gemfire\cache\FailedSynchronizationException.java:33:
> warning - Tag @see: reference not found: javax.transaction.Status
> C:\dev\gemfire_CLEAN\open\gemfire-core\src\main\java\com\gemstone\gemfire\cache\SynchronizationCommitConflictException.java:27:
> warning - Tag @see: reference not found:
> javax.transaction.UserTransaction#commit
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (GEODE-876) Add a README file to the binary distribution
[ https://issues.apache.org/jira/browse/GEODE-876?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-876: --- Sprint: 1.0.0-incubating.M3 > Add a README file to the binary distribution > > > Key: GEODE-876 > URL: https://issues.apache.org/jira/browse/GEODE-876 > Project: Geode > Issue Type: Bug >Reporter: Swapnil Bawaskar >Assignee: Sai Boorlagadda > Labels: docs > Fix For: 1.0.0-incubating.M2 > > > The binary distribution is missing README and RUNNING.txt files which are > present in src distribution. > These files should be added to the binary distribution to provide a starting > point for the users. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-72) Remove deprecated APIs from Geode
[ https://issues.apache.org/jira/browse/GEODE-72?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-72: -- Fix Version/s: 2.0.0-incubating > Remove deprecated APIs from Geode > - > > Key: GEODE-72 > URL: https://issues.apache.org/jira/browse/GEODE-72 > Project: Geode > Issue Type: Improvement >Affects Versions: 1.0.0-incubating >Reporter: Bruce Schuchardt > Labels: cleanup, docs > Fix For: 2.0.0-incubating > > > The Geode APIs are riddled with old, deprecated interfaces, methods and > settings inherited from GemFire. Unless there is a good reason to keep them > shouldn't we remove them all before going out of incubation? > Sub-tasks have been added for most items. Here are the remaining items not > yet added: > APIs deprecated in GemFire 5.1: > * DLS.lockInterruptibly(), suspendLockingInterruptibly() > > APIs deprecated in an undocumented version prior to 5.7: > * Use of hostname:port to specify a locator in gemfire.properties > > APIs deprecated after GemFire 5.7 and before 8.0 > * EvictionAlgorithm.LIFO_ENTRY, LIFO_MEMORY: these were deprecated but we > never deprecated EvictionAttributes.createLIFOEntryAttributes > nor EvictionAttributes.createLIFOMemoryAttributes. These algorithms are used > internally by the product when a server create a queue to send subscription > events to a client (see BridgeServerImpl.clientMessagesRegion). I think the > algorithms were deprecated because we didn't intend to expose this internal > feature as an external one. But they are exposed externally via > EvictionAttributes so it is not clear that we can just delete them. > The other consideration is that we do not have xsd support nor gfsh support > for LIFO. > * Region.getCache(): we should consider un-deprecating this. Customers were > supposed to instead call Region.getRegionService but in lots of cases they > would need to down cast that result to "Cache". Only clients that are calling > ClientCache.createAuthenticatedView end up with Regions whose getCache throws > UnsupportedOperationException. Our code call getCache from over 500 places. > * Locator.startLocator(int, File), startLocator(int, File, InetAddress) etc. > * Locator.getLocators(), hasLocators() > APIs deprecated since GemFire 5.7 with no version information mentioned > * DistributedRegionMXBean.getDiskTaskWaiting() > * MemberMXBean.getCurrentHeapSize(), getMaximumHeapSize(), getFreeHeapSize() > * RegionMXBean.getDiskReadsAverageLatency(), getDiskWritesAverageLatency(), > getDiskTaskWaiting() > Things that should be deprecated but are not: > * MembershipAttributes and “required roles”. > * DynamicRegions: if GEODE-215 is implemented then we could deprecate > DynamicRegions and have an alternative to change to. We have some support in > the gfsh/management layer for creating regions remotely which might be good > enough to deprecate DynamicRegions. The question is should we remove > com.gemstone.gemfire.cache.DynamicRegionFactory even though it has not been > deprecated. > Deprecated in 7.0 and not previously in this list: > * UniversalMembershipListenerAdapter > APIs deprecated in 8.0. It would probably be a nice gesture to Pivotal to > keep these for a while to allow people to migrate from their GemFire product > to Geode. > * PutAllOperationContext.setMap() > * FixedPartitionResolver.getPartitionName(EntryOperation, Set) > * ssl-enabled, ssl-protocols, ssl-ciphers, ssl-require-authentication, > jmx-manager-ssl distribution properties > * RegionMXBean.getAvgBucketSize() > The Admin API and packages are also marked as deprecated but there seem to be > some gfsh dependencies on this API, so I'm not sure if it can be removed. > Also consider removing com.gemstone.gemfire.cache.partition.PartitionListener > and com.gemstone.gemfire.cache.partition.PartitionManager. > They have not been deprecated but were never fully supported. Their javadocs > say: > Note : Please contact supp...@gemstone.com before using these APIs -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-37) Package renaming
[ https://issues.apache.org/jira/browse/GEODE-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-37: -- Fix Version/s: 2.0.0-incubating > Package renaming > > > Key: GEODE-37 > URL: https://issues.apache.org/jira/browse/GEODE-37 > Project: Geode > Issue Type: Task > Components: docs, general >Affects Versions: 1.0.0-incubating >Reporter: William Markito Oliveira >Priority: Blocker > Fix For: 2.0.0-incubating > > > Geode packages should be renamed from com.gemstone -> org.apache.geode in > order to allow an easy transition from incubation to become a TLP. > Also, it allow the necessary work that may need to be done at the protocol > level in order to allow serialization/message exchange between nodes before > an actual release using the definitive class/package naming. > The issue was discussed in the following thread at dev@: > http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201505.mbox/ajax/%3C554B38C3.5050500%40pidster.com%3E -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-1331) gfsh.bat on Windows is incorrect
[
https://issues.apache.org/jira/browse/GEODE-1331?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
William Markito Oliveira updated GEODE-1331:
Fix Version/s: (was: 1.0.0-incubating)
1.0.0-incubating.M3
> gfsh.bat on Windows is incorrect
>
>
> Key: GEODE-1331
> URL: https://issues.apache.org/jira/browse/GEODE-1331
> Project: Geode
> Issue Type: Bug
> Components: gfsh
>Reporter: Jens Deppe
> Fix For: 1.0.0-incubating.M3
>
>
> Initial report:
> {quote}
> I am doing testing in windows STS. I am not adding these dependencies jars,
> gfsh.bat is what doing this.
>
> C:\DEV\Pivotal\GemFire_v82014\bin\gfsh.bat has below code, which is setting
> gemfire, antlr, gfsh-dependencies and pulse-dependencies jars in classpath.
> Line 26 to 29
> @set
> GEMFIRE_JARS=%GEMFIRE%\lib\gemfire.jar;%GEMFIRE%\lib\antlr.jar;%GEMFIRE%\lib\gfsh-dependencies.jar;%GEMFIRE%\lib\pulse-dependencies.jar
> @if defined CLASSPATH (
> @set GEMFIRE_JARS=%GEMFIRE_JARS%;%CLASSPATH%
> )
> C:\DEV\Pivotal\GemFire_v82014\lib\gemfire.jar // DUPLICATE
> C:\DEV\Pivotal\GemFire_v82014\lib\antlr.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\gfsh-dependencies.jar // DUPLICATE
> C:\DEV\Pivotal\GemFire_v82014\lib\pulse-dependencies.jar
>
> Unix C:\DEV\Pivotal\GemFire_v82014\bin script, does not set these jars in
> classpath.
>
>
> Another observation is that, if I pass --include-system-classpath to gfsh
> start server command, then it is prepending gemfire.jar and
> gfsh-dependencies.jar to the system classpath and adding that to the server,
> that is what is shown in logs
> Class Path:
> C:\DEV\Pivotal\GemFire_v82014\lib\gemfire.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\gfsh-dependencies.jar
>
> ………..
> C:\Program Files\Java\jdk1.7.0_67\lib\tools.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\server-dependencies.jar
>
> start server \
> --name=${NAME} --server-port=${PORT} \
> --properties-file=${GEMFIRE_PWD}/resources/cache.properties \
> --J=-Dgemfire.distributed-system-id=${DISTRIBUTED_SYSTEM_ID} \
> --J=-Dgemfire.bind-address=${HOST_NAME}
> --J=-Dgemfire.server-bind-address=${HOST_NAME} \
> --J=-Dgemfire.locators=${HOST_NAME}[${LOCATOR_PORT}] \
> --J=-Dgemfire.OSProcess.ENABLE_OUTPUT_REDIRECTION=true \
> --include-system-classpath
>
> If I don’t pass this parameter, then it does not add gfsh-dependencies
> Class Path:
> C:\DEV\Pivotal\GemFire_v82014\lib\gemfire.jar
> C:\DEV\Pivotal\GemFire_v82014\lib\server-dependencies.jar
>
> I am trying to do testing without using –include-system-classpath instead add
> jars in to the start server –classpath as a work around.
> {quote}
> And a subsequent reply from John Blum:
> {quote}
> My apologies. I was not aware that you were launching your GemFire process
> (e.g. Server) using Gfsh, and specifically with gfsh.bat on Windows.
> I just confirmed the line(s) you were looking at in gfsh.bat, and indeed the
> BAT file is wrong! Specifically, the classpath for the GemFire process is
> being constructed from the following lines...
> @set
> GEMFIRE_JARS=%GEMFIRE%\lib\gemfire.jar;%GEMFIRE%\lib\antlr.jar;%GEMFIRE%\lib\gfsh-dependencies.jar;%GEMFIRE%\lib\pulse-dependencies.jar
> ...
> @set GFSH_JARS=;%GEMFIRE%\lib\gfsh-dependencies.jar
> @set CLASSPATH=%GFSH_JARS%;%GEMFIRE_JARS%
> The Windows BAT file is also inconsistent with the Bash shell version (gfsh),
> which rightfully only contains...
> GEMFIRE_JARS=$GEMFIRE/lib/gfsh-dependencies.jar
> if [ "x$CLASSPATH" != "x" ]; then
> GEMFIRE_JARS=$GEMFIRE_JARS:$CLASSPATH
> fi
> CLASSPATH=$GEMFIRE_JARS
> In addition, the Bash shell version launches the Gfsh process using the java
> -classpath option...
> "$GF_JAVA" -Dgfsh=true
> -Dlog4j.configurationFile=/com/gemstone/gemfire/internal/logging/log4j/log4j2-cli.xml
> ${JLINE_TERMINAL} -classpath "${CLASSPATH}" $JAVA_ARGS $LAUNCHER "$@"
> Which does not "export", or rather, set the global System CLASSPATH
> environment variable. Here it is only setting the Java System property to
> the Java process, where as, I believe, the Window BAT file is actually
> setting the System CLASSPATH environment variable, since there is no java
> -classpath option present in the command to launch Gfsh...
> @"%GF_JAVA%" -Dgfsh=true
> -Dlog4j.configurationFile=/com/gemstone/gemfire/internal/logging/log4j/log4j2-cli.xml
> %JAVA_ARGS% %LAUNCHER% %*
> Regarding...
> > I think we need Pivotal Engineering team to look into gfsh.bat and
> > –include-system-classpath behavior.
> Not exactly. --include-system-classpath basically functions such that it
> appends the value of the System CLASSPATH environment variable to the forked
> GemFire process launched from Gfsh if the user has set the global variable
> per environment and wishes to use it.
> In a nutshell, GemFire documentation use to errone
[jira] [Updated] (GEODE-1133) SeparateClassloaderTestRunner has to be re-implemented
[ https://issues.apache.org/jira/browse/GEODE-1133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] William Markito Oliveira updated GEODE-1133: Fix Version/s: 1.0.0-incubating.M3 > SeparateClassloaderTestRunner has to be re-implemented > -- > > Key: GEODE-1133 > URL: https://issues.apache.org/jira/browse/GEODE-1133 > Project: Geode > Issue Type: Improvement > Components: http session >Reporter: Sai Boorlagadda > Fix For: 1.0.0-incubating.M3 > > > While working on GEODE-52, it was found that `SeparateClassloaderTestRunner' > is copied from stackoverflow > (http://stackoverflow.com/questions/42102/using-different-classloaders-for-different-junit-tests) > Either this code has to be re-implemented or find an appropriate code from > another reliable source, so that we can add it to the NOTICE about the > license. > extensions/geode-modules-session/src/test/java/com/gemstone/gemfire/modules/session/junit/SeparateClassloaderTestRunner.java: -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (GEODE-117) gfsh put ignores --skip-if-exists flag
[ https://issues.apache.org/jira/browse/GEODE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279220#comment-15279220 ] Dan Smith commented on GEODE-117: - [~manvsri] We just needed to add you as a contributor. You're now a contributor and I assigned the ticket to you, so have at it. > gfsh put ignores --skip-if-exists flag > -- > > Key: GEODE-117 > URL: https://issues.apache.org/jira/browse/GEODE-117 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Dan Smith >Assignee: Srikanth Manvi > Labels: gfsh, starter > > Someone hit this on a forum post: > https://support.pivotal.io/hc/communities/public/questions/204414098-put-in-gfsh-doesn-t-honor-skip-if-exists-true-flag-?flash_digest=f2441b8a96ac363d6da205c6f90a62035b1a3c21 > I looked into the code, and it looks like the flag gets lost somewhere along > the way. If you look at DataCommandFunction.put, it has a putIfAbsent flag, > but that flag is not used; the function just does a normal put. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (GEODE-117) gfsh put ignores --skip-if-exists flag
[ https://issues.apache.org/jira/browse/GEODE-117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Smith updated GEODE-117: Assignee: Srikanth Manvi > gfsh put ignores --skip-if-exists flag > -- > > Key: GEODE-117 > URL: https://issues.apache.org/jira/browse/GEODE-117 > Project: Geode > Issue Type: Bug > Components: gfsh >Reporter: Dan Smith >Assignee: Srikanth Manvi > Labels: gfsh, starter > > Someone hit this on a forum post: > https://support.pivotal.io/hc/communities/public/questions/204414098-put-in-gfsh-doesn-t-honor-skip-if-exists-true-flag-?flash_digest=f2441b8a96ac363d6da205c6f90a62035b1a3c21 > I looked into the code, and it looks like the flag gets lost somewhere along > the way. If you look at DataCommandFunction.put, it has a putIfAbsent flag, > but that flag is not used; the function just does a normal put. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1289) RegionEntry.getValueInVM result should not be @Retained
[ https://issues.apache.org/jira/browse/GEODE-1289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-1289: --- Assignee: Darrel Schneider > RegionEntry.getValueInVM result should not be @Retained > --- > > Key: GEODE-1289 > URL: https://issues.apache.org/jira/browse/GEODE-1289 > Project: Geode > Issue Type: Bug > Components: offheap >Reporter: Darrel Schneider >Assignee: Darrel Schneider > > The method RegionEntry.getValueInVM has its result marked as @Retained. > However the implementation always copies the result to the heap (see > AbstractRegionEntry.getValueInVM which uses copyAndReleaseIfNeeded). > All the callers of this method need to also be checked because many of them > also say they are @Retained and they even have try/finally code to do a > release that is not needed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (GEODE-1296) OffHeapStoredObject.getRawBytes should assert that it is not called on compressed data
[
https://issues.apache.org/jira/browse/GEODE-1296?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kenneth Howe reassigned GEODE-1296:
---
Assignee: Kenneth Howe
> OffHeapStoredObject.getRawBytes should assert that it is not called on
> compressed data
> --
>
> Key: GEODE-1296
> URL: https://issues.apache.org/jira/browse/GEODE-1296
> Project: Geode
> Issue Type: Bug
> Components: offheap
>Reporter: Darrel Schneider
>Assignee: Kenneth Howe
>
> The current code does this:
> if (isCompressed()) {
> throw new UnsupportedOperationException();
> }
> It would be more clear if it just did this:
> assert !isCompressed();
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Assigned] (GEODE-1379) Documentation should make clear that offheap regions will always clone when deltas are applied
[ https://issues.apache.org/jira/browse/GEODE-1379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Darrel Schneider reassigned GEODE-1379: --- Assignee: Darrel Schneider > Documentation should make clear that offheap regions will always clone when > deltas are applied > -- > > Key: GEODE-1379 > URL: https://issues.apache.org/jira/browse/GEODE-1379 > Project: Geode > Issue Type: Improvement > Components: docs, offheap >Reporter: Darrel Schneider >Assignee: Darrel Schneider > > Regions have a cloning-enabled attribute that when false usually means that a > clone of the object will not be created when a Delta is applied. > But when the region is also offheap the cloning-enabled attribute will be > ignored and the region will behave as if it was set to true. > This is because offheap regions store the value in serialized form. To apply > a Delta to the value requires that the value be deserialized. Doing a > deserialization is the same as making a clone. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
