Hi,
I have a general design question on mvn2's project (directory) structure.
I'm starting on a project which involves creating a software product to be
used by a few clients, with each client having particular customizations on
top of the product. I'm thinking of a structure design where I separate the
generic/reusable product in its own project, and any client-specific
customizations in their own root-level projects... something like this:
------------------------------------------------------------------
> product (uses mvn2 subprojects)
> pom.xml
> product-core
> pom.xml
> product-service
> pom.xml
...
> client1 (which has classes that depend on the product project)
> pom.xml
> product-core
> pom.xml
...
> client2 (which has classes that depend on the product project)
...
> clientN.....
...
---------------------------------------------------------------------------
I know I can set this structure up physically. Not sure how mvn2 will work
with this. Basically if I'm building/deploying this product to client 1, I
would like to just do invoke the mvn command, with maybe a profile attribute
or similar specifying that its for client1, that will build the product
project and then just the client1 project. If there is another better
option that will facilitate this product/customization package scenario, I
would appreciate any suggestions. Thanks in advance!
-los
--
View this message in context:
http://www.nabble.com/mvn2-structure-design-for-a-software-product-tf4474879s177.html#a12758764
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
