Hello,
I has been evaluating Maven to start using it to replace our existing Ant
build scripts. To give you a background:
- My work is such that I have multiple projects that I do for multiple
customers but the nature of the project is mostly the same. I basically
customize a base product of a particular company and integrate or modify the
base code.
- The folder structure is such that I have a project lets say:
---PROJECT1
|
----Module1
|
---- New Java/EJB classes
|
---- New JSPs and war components
|
-----Module2 (similar structure)
|
-----MAIN MODULE
|
----- Modifications to the base product Java classes
|
----- Modifications to the base product JSPs
|
------Promoted JSPs and Java classes from modules
above.
- Currently, my ant build scripts, promote the JSPs and compiled java
classes from ALL the modules in to the MAIN MODULE where everything
(including the JSPs and Java classes of the MAIN Module and the promoted
ones) are packaged into One EAR file.
- I would like to get a suggestion or a best way to migrate to the Maven
structure so that there are minimal changes to the folder structure and I am
able to accomplish my task of creating one customized EAR file.
Can you please guide me for the best practise to follow to help me migrate
to Maven 2.
Thanks
Shilpa
--
View this message in context:
http://www.nabble.com/Design-suggestion-needed-to-restructure-the-build-process-with-Maven-tp18607238p18607238.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
