Hi all,

I have inherited two projects which I will be managing using Maven 2.0.  Both 
are Java EE-based, the first one sometimes talking to the second one using 
stateless session beans.  Both also should be sharing a large code base but 
currently are not, so there's a lot of duplication.

I'm wondering how I should distribute these projects into M2 projects and 
modules.  Right now I'm leaning towards having 4 projects: system1, system2, 
system2-api and core.  The first two are self-explanatory, system2-api would 
contain the EJB interfaces required by system1 and implemented by system2, and 
core would eventually contain the result of refactoring the duplicated code.  
The first two projects would depend on the last two, and system2-api would 
depend on core.

Is this a correct approach or is there a better approach that I'm not seeing?

Cheers,
GB

PS: To the person who answered me last time: thanks!  My problem was solved, 
but I couldn't find back the original message to confirm that and thank you.

Reply via email to