On 03/22/2012 10:34 PM, Matt Franklin (Created) (JIRA) wrote:
Move Rave-shindig
-----------------
Key: RAVE-524
URL: https://issues.apache.org/jira/browse/RAVE-524
Project: Rave
Issue Type: Technical task
Reporter: Matt Franklin
Create the following structure:
rave-opensocial-provider
|__rave-opensocial-core
|__rave-opensocial-client
|__rave-opensocial-server
|_ rave-shindig
This new structure works and technically there is nothing wrong with it either,
but it isn't clear to me why we need rave-opensocial-server and rave-shindig,
nested under rave-opensocial-provider?
At least right now I see no added value (yet) nor a logical/functional reason as
neither the rave-opensocial-provider nor the rave-opensocial-server bring any
(maven/pom) added value.
Maybe I'm missing something obvious here but can't we keep rave-shindig and
rave-portal as sibling root modules? Both are very similar IMO, as pom only war
modules, aggregating everything else in and only needed in the last build phase.
And when overriding/extending rave for custom builds, typically neither
rave-portal nor rave-shindig will be used anymore but replaced with custom war
modules, so from that perspective these are kind of 'example' modules.
Ate
