Hi Santonian,
I don't think using project inheritance for the core module and the
customer specific modules is the right way.
What I suggest is you can have the core module as a separate project and
have each of the customer-specific modules as separate projects as well.
Then just set the core module as a dependency of these customer-specific
projects.
Hope this helps! :-)
Thanks,
Deng
Santonian wrote:
Hello there,
I am working with maven some time now but have not the most experince with
the configuartion of it.
I have the following problem to solve and I dont know exactly how to do it.
I read about project inheritance, but I am not sure if thats the right thing
for me.
This is what I am trying to achive:
We have an application that mainly uses Spring MVC and Freemarker. Rigth now
for each customer we have a seperate project because the requirements of
each customer are quite diffrent.
Now we want to refactor our application, so that we can have a core module
and an individual module for each customer. The individual modules must be
able to inherith classes of the core module. Changed made to the core module
should be reflected by all customer specific modules.
How can I do that? Is Project Inheritance the right thing for me? Can I have
the core part and the customer parts all in the same project or do I have to
have a seperate project for all customers?
Any tips and links are greatly apreciated.
cheers
Santo
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
