[
https://issues.apache.org/jira/browse/HBASE-2542?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12867629#action_12867629
]
Andrew Purtell commented on HBASE-2542:
---------------------------------------
bq. Could you please point out, why you don't want to support standalone Jetty
anymore?
Sorry if not clear. I am saying standalone Jetty (Stargate running as a daemon
embedded in Jetty) is the only supported configuration going forward; i.e. we
drop the WAR target.
bq. I've a very hard time trying to package all stargate dependencies. So I'm
happy, if stargate would remain a contrib for a longer while until I manage to
get the dependencies into Debian.
We are getting rid of the notion of contrib and moving Stargate into core. So
then the question is really should HBase temporarily drop any RESTful interface
while Debian is sorting out Jersey dependencies.
> Fold Stargate into core
> -----------------------
>
> Key: HBASE-2542
> URL: https://issues.apache.org/jira/browse/HBASE-2542
> Project: Hadoop HBase
> Issue Type: Task
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 0.21.0
>
>
> Freeze o.a.h.h.stargate and move to github for some transitional period.
> Replace o.a.h.h.rest with Stargate:
> - Remove o.a.h.h.rest and related artifacts
> - Remove Stargate WAR target (leaving only daemonized/embedded Jetty
> launch option)
> - Move o.a.h.h.stargate into place as o.a.h.h.rest and pull related
> dependencies into core
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
