[
https://issues.apache.org/jira/browse/HBASE-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Smith updated HBASE-2348:
------------------------------
Attachment: HBASE-2348-stargatetweaks2.patch
ok, I'm not sure I'd necessarily _trust_ this patch given I attempted to fix up
a local clone of a bad github clone with a fresh asf-git clone, and then
remerge my patch from another local checkout. (*bang* - the sound of my head
exploding)
honestly, if this doesn't work, it may just be simpler to send you the 3 new
pom files (stargate/pom.xml, stargate/core/pom.xml and stargate/war/pom.xml,
they're in the ptach) plus the set of commands I used to do the directory
shuffling. I had hoped Git would be the silver bullet I'd been looking for...
but it still looks like these sorts of hairy bait and switches can cause some
pain.
> 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-2348-stargatetweaks2.patch,
> 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.
