It occurred to me after *Charlie* shared the link to installing *Pulse* in a standalone Servlet Container (e.g. Apache Tomcat) that we don't properly describe how to handle the Geode dependencies (e.g. geode-core). Again, this is not bundled as part of the Geode WAR files.
-1 to publishing a GWAR file. These are still valid WAR files regardless of the dependencies they provide or don't provide (which is a documentation concern in my mind). On Wed, Sep 25, 2019 at 10:53 AM Anthony Baker <aba...@pivotal.io> wrote: > Thanks for the reminder. If these files are required to start a geode > member, I agree they should be published artifacts. Perhaps there’s a > better way to pull them in…but this seems like the best option for now. > > Anthony > > > > On Sep 25, 2019, at 10:22 AM, Udo Kohlmeyer <ukohlme...@pivotal.io> > wrote: > > > > @Anthony. Ticket was updated.. In a nutshell, to run integration tests, > using the REST endpoints, requires the starting of the server with and > embedded web-server. > > > > As all tests run on dependency management only and don't have access to > a downloaded product, the HTTP endpoints are not part of the dependency. > These are added in by including the WAR files from mavenCentral. > > > > As @Dan pointed out, GEODE-5660 enabled this behavior. > > > > I think this approach might actually even help with the testing of the > REST Controller in the Geode codebase itself. > > > > --Udo > > -- -John john.blum10101 (skype)
