[ 
https://issues.apache.org/jira/browse/HBASE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Smith updated HBASE-2348:
------------------------------

    Attachment: hbase-stargatetweaks.patch
                hbase-stargatetweaks.diffstat

patch of the changes for relocation, I think I did this right... I hope so, 
attached a diffstat output as well for reference.

in summary:

* relocate majority from stargate/src -> stargate/core/src
* relocate the 2 .xml files in conf -> stargate/web
* add a new stargate parent pom (original pom now moves down to core), add a 
simple one for the new war sub-module
* tweak the assembly 'bin.xml' file in the top-level hbase area that ensures 
these 2 new artifacts turn up
* *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..)

please excuse my git newbie ness., I'm using this sort of changeset as a way to 
gain real world experience with git! :)

> 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: Paul Smith
>         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.

Reply via email to