Spliting Fron-end from Back-office on Maven
I've a java ecommerce web-based app.
It is written using Spring Roo, so it follows the Domain Driven Design paradigm.
The application has two UI.
The first is front-end, based on plain jsp/jstl/tiles, it is stable, changes rarely and HAVE to STAY UP and RUNNING.
The second is built on Vaadin/GWT, it changes frequently (on Custemer requerements).

My question is how to best structure Maven project such as:
- Allow deploy (on tomcat) only back-office or front-end UI;
- Do not duplicate Domain Logic


Thanks

Spliting Fron-end from Back-office on Maven
===

I've a java ecommerce web-based app.
It is written using Spring Roo, so it follows the Domain Driven Design paradigm.
The application has two UI.
The first is front-end, based on plain jsp/jstl/tiles, it is stable, changes rarely and HAVE to STAY UP and RUNNING.
The second is built on Vaadin/GWT, it changes frequently (on Custemer requerements).

My question is how to best structure Maven project such as:
- Allow deploy (on tomcat) only back-office or front-end UI;
- Do not duplicate Domain Logic


Thanks
