Engage directory structure

Colin Clark colinbdclark at gmail.com
Tue Sep 22 21:22:42 UTC 2009

Hi Michelle and everyone else,

On 21-Sep-09, at 3:44 PM, Michelle D'Souza wrote:

> Hi everyone,
> As we approach the 0.1 release of Engage we need to decide on the  
> directory structure of the engage trunk. Here is a suggestion which  
> is based on the Infusion structure. Please comment and suggest  
> alternatives. One question I have - should there be a services  
> directory? What would go in there?
> fluid
> 	engage
> 		trunk
> 			src
> 				webapp
> 					components
> 					demos
> 					kettle
> 					lib
> 					tests

How does this sit with the standard directory structure expected by  
Maven 2?

I'd love to hear from Antranig and Yura about this proposed directory  
structure and if it will suit our needs.

In the end, our goal is to make building Engage as simple as possible.  
Since it's currently based on Kettle's JVM-based approach, Maven is  
probably the way this will be built. If we need to add an Ant script  
for other build-related tasks, we can look at that, too.


Colin Clark
Technical Lead, Fluid Project

More information about the fluid-work mailing list