There's an example in Chapter 6 of "Maven: The Definitive Guide" that
shows how to set up and use a multi-module project. It's structured
like this:
\- Simple Parent Project
+- Simple Weather API
+- Simple Web Application Project
With this setup, you can do "mvn install" on the parent project, and
any out-of-date source code in any child project will automatically be
compiled. So instead of running "mvn install" on each child, you can
do it just once on the parent. Nice!
However... What if you now want to create a new web application
project? Let's say this new web application is completely independent
of the old one, but it still uses Simple Weather API.
I guess one approach is to create a new multi-module project like this:
\- Simple Parent Project 2
+- Simple Web Application Project 2
Then simply add a dependency on Simple Weather API. But the problem
here is that if you change the source code in Simple Weather API,
running "mvn install" on Simple Parent Project 2 won't compile the
change! You have to switch to Simple Weather API, run "mvn install",
and then return to Simple Parent Project 2. This is really annoying,
especially if you have more than one shared module.
Is there any way to set up multi-module projects so that they can
share a module, and both projects can detect when that module's source
code is out-of-date? Thanks,
Trevor
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
