I agree with you Ed. For 1.0, this is definitely the path of least resistance, and if that class is used to serve up static resource, we'll still need it.
On Sun Jan 04 2015 at 12:51:28 PM Ed Anuff <[email protected]> wrote: > I thought this was for the 1.0.1 release though. Regardless of what we > want to do in 2.0, doesn't the current Launcher in 1.0 fire up an embedded > web server that serves, among other things, a few JSPs, CSS files, etc? I > understand the desire to blow aware the standalone server and launcher in > favor of other mechanisms (although I do think that will result in this > being harder, not easier, for people to run locally), which is fine for > ticket 308, but what about 1.0.x? > > On Sun, Jan 4, 2015 at 11:41 AM, Nate McCall <[email protected]> wrote: > >> > Agreed. The launcher is getting an overhaul in the 2.0 branch, we just >> > haven't decided what that is. >> >> Is there a Jira issue for this yet? I have some ideas (see below) >> >> > We've found the embedded Cassandra to be >> > problematic, so we're open to ideas of ways to create a more usable >> > standalone distro that utilizes the war binary created with our release >> > process. >> >> I don't think this is a realistic goal given the complexity. Running >> this as a "fat jar" application and forking Cassandra to it's own >> process would be the sanest approach. >> >> Them's my $0.02 - let's do discussion on a ticket though. Couldn't >> find one, so I created: >> https://issues.apache.org/jira/browse/USERGRID-308 >> > >
