Forgot to mention that a layout like this:
hbase/
contrib/
stargate/
src/
embedded/
main/
servlet/
would only be for 0.20.4, assuming we have one. In 0.21, Stargate is
getting merged back into core.
So this is why I haven't done something like the above. Is it worth
the time?
- Andy
----- Original Message ----
> From: Andrew Purtell <[email protected]>
> To: [email protected]
> Sent: Tue, February 9, 2010 9:27:12 AM
> Subject: Re: Stargate War - jetty.xml and dependencies
>
> > What I propose is then a directory structure change to stargate
> >
> > hbase/
> > contrib/
> > stargate/
> > web
> > service (or something)
>
> I'm not opposed to that if someone produces the appropriate patch...
>
> I think there would only need to be two targets. May I recommend as names
> "servlet", which produces a war, and and "embedded", which produces a jar?
> Much of the source is shared so there would be a layout something like
> this I expect:
>
> hbase/
> contrib/
> stargate/
> src/
> embedded/
> main/
> servlet/
>
> and then some ant-fu.
>
> There's no need for that jetty.xml for embedded. Have a look at
> o.a.h.h.stargate.Main. Jetty is started and configured in the Main
> class.
>
> > Although the confusion from my newbie HBase side is one AndrewP
> > mentioned about running the stargate bit through the hbase daemons.sh
> > script.
>
> This:
>
> ./bin/hbase-daemon.sh start org.apache.hadoop.hbase.stargate.Main
>
> starts up Stargate via embedded Jetty in the background with logger
> redirection, like how the Master and RegionServers are typically
> started.
>
> This:
>
> ./bin/hbase-daemons.sh start org.apache.hadoop.hbase.stargate.Main
>
> (note daemon versions daemon_s_)
>
> would start Stargate in the background ... like how the Master and
> RegionServers are typically started ... on all the hosts listed in
> conf/regionservers. Although you can do that, that was not what I
> was suggesting.
>
> - Andy
>
>
>
> ----- Original Message ----
> > From: Paul Smith
> > To: [email protected]
> > Sent: Mon, February 8, 2010 6:05:38 PM
> > Subject: Re: Stargate War - jetty.xml and dependencies
> >
> >
> > On 09/02/2010, at 11:56 AM, Stack wrote:
> >
> > > The WAR has everything under WEB-INF (class files, etc.). The jar has
> > > it all at top-level. It looks like a WAR can't be used as a JAR as I
> > > suggested in my previous mail so, yeah, stargate contrib would seem to
> > > have WAR and JAR targets (unless someone knows better).
> > >
> >
> > What I propose is then a directory structure change to stargate
> >
> > hbase/
> > contrib/
> > stargate/
> > web
> > service (or something)
> >
> > and move the WEB-INF related stuff into the 'web' area, and move the java
> > side
>
> > under 'service'.
> >
> > that way we can have 2 artifacts produced, one a jar file (service), and
> > one a
>
> > war file (web) automatically.
> >
> > There's also no reason we can't also have a 3rd artifact, say, 'standalone'
> that
> > is a bundled up version of jetty, with a Main class that just launches
> > Jetty
> > with the jetty.xml (simple using the appassembler Maven plugin). Although
> > the
> > confusion from my newbie HBase side is one AndrewP mentioned about running
> > the
>
> > stargate bit through the hbase daemons.sh script. I'm not really sure what
> that
> > means, does that farm the stargate stuff out to all datanodes or something?
> >
> >
> > cheers,
> >
> > Paul
