hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andrew Purtell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (HBASE-2348) Stargate needs both JAR and WAR artifacts
Date Sat, 27 Mar 2010 01:26:27 GMT

    [ https://issues.apache.org/jira/browse/HBASE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12850444#action_12850444

Andrew Purtell commented on HBASE-2348:

Yikes! That is quite a patch. Let me apply it and try it out.

SUBTLE BUT IMPORTANT: no longer have a separate lib directory under stargate, but bundle up
stargate specific dependencies into the top level artifact lib directory. This actually means
a faster assembly because there's no longer duplicate copy dependencies that suffer from the
maven-fork-per-dependency problem we had recently, but it may not be what you want, because
now the lib directory contains super-set of the dependencies for all modules now (maybe that
is what you want anyway..)


I typically deploy Stargate by copying its dependencies in contrib/stargate/lib/ up into lib/,
and the Stargate jar up to toplevel, then invoke stargate with the ./bin/hbase script. If
I read you correctly, your proposal is what I end up with anyway.

> Stargate needs both JAR and WAR artifacts
> -----------------------------------------
>                 Key: HBASE-2348
>                 URL: https://issues.apache.org/jira/browse/HBASE-2348
>             Project: Hadoop HBase
>          Issue Type: Improvement
>          Components: contrib
>    Affects Versions: 0.21.0
>            Reporter: Paul Smith
>            Assignee: Andrew Purtell
>         Attachments: hbase-stargatetweaks.diffstat, hbase-stargatetweaks.patch
> Since the move to Maven we have lost the ability to have Stargate bundled as both a JAR
and a WAR file (currently just the latter).
> I'm proposing to split the current stargate module further into 2 sub-modules 'stargate-war'
and 'stargate-core' (totally up for discussion on naming).  
> Basically moving existing sources down to 'stargate-core' and relocating the conf section
into the war sub-module.
> I'll be doing this via a github fork to make the review and merge process easier.  However
I suspect I'll do the Maven side ok but totally hose the Git part, so strap yourselves in..

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message