[
https://issues.apache.org/jira/browse/RAVE-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13106832#comment-13106832
]
Ate Douma commented on RAVE-171:
--------------------------------
Concerning the customization use-cases from Marlon: I too think all those can
or should be supported by the restructuring.
For use-case 2) I think the developer then would only need to override the
rave-portal-resources (war), not the rave-portal-web (jar) as long as it only
concerns client side resources and not server side objects (Java).
> Reorganize project to support better extension
> ----------------------------------------------
>
> Key: RAVE-171
> URL: https://issues.apache.org/jira/browse/RAVE-171
> Project: Rave
> Issue Type: Sub-task
> Reporter: Marlon Pierce
> Fix For: 0.4-INCUBATING
>
>
> Extension codes not in rave-portal src tree will need to be able to compile
> against that code. This can be done by modifying rave-portal/pom.xml so that
> it makes both a war and a jar and installs both in the local repository. The
> extension code should then have the appropriate dependency in its pom.xml
> Re-organize rave project in the following manner to support simpler extension
> by downstream integrators:
> Rave Project:
> |
> |__rave- components
> | |
> | |__rave-commons (Generic & common code that is usable in many
> different contexts, modules and projects)
> | |
> | |__rave-core (Core Model, Service& Repository classes that are used
> by multiple applications) [Widget, Person& related Classes]
> | |
> | |__rave-security (Security related classes) [User extends Person,
> Security Utilities, etc]
> |
> |__rave-providers
> | |
> | |__rave-opensocial (OpenSocial provider classes)
> | |
> | |__rave-w3c (W3C provider classes)
> |
> |__rave-portal (Core portal& webapp related features) [Regions, Pages,
> controllers, etc]
> |
> |__rave-shindig
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
