incubator-graffito-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christophe Lombart (JIRA)" <>
Subject [jira] Created: (GRFT-27) PROPOSAL : Graffito Modules
Date Thu, 02 Jun 2005 10:15:57 GMT
PROPOSAL : Graffito Modules

         Key: GRFT-27
     Project: Graffito
        Type: New Feature
    Versions: 1.0-a1-dev    
    Reporter: Christophe Lombart
 Assigned to: Christophe Lombart 
     Fix For: 1.0-a1-dev

I would like to add the Graffito module concept in the project. This can help to add new extersions
into Graffito and gives some facilities to contribute to the Graffito project. This is also
a great help to customize the Graffito services.

What is a Graffito module ?
A module is composed of some java codes, resources and deployment scripts. It is mainly used
to add more features in Graffito. Eg. we can plan to add modules for document management,
asset management, scheduler application, forum, news management,  ... 
The Graffito core object model & services are the foundation for all Graffito modules.
It should be also possible to customise a existing module. 

The deployment artifact is composed only of a set of jars and one assembly script.

New project structure
We have to review the project structure in order to support the Graffito modules. A proposal
will be made in another Jira issue. 

Graffito Maven plugin
I'm not the Maven expert but we can imagine to build a plugin used for the module management.

We can start with simple maven goals like initialise a subproject module with some default
deployment scripts, replace a deployed module, ....

The more important issue for building new module is the modification of the DB schema (content
repository structure). This issue is quite limited if we are using JCR by default. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message