Todd Thiessen wrote:
4. Understand how multi-module projects are structured and how they
work. I made a dummy project for this before I even
considered porting
over the actual production code.
Yup, this is where I want to wind up. I am supposing that the
right thing is to get the individual projects buildable this
way, then build a multi-module architecture around it. If
that is wrong, please let me know now before I get too far into this.
If the project can be built individually, then yes that makes sense. But
if you have any depencencies between projects then of course the picture
is a bit more complex.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
Okay, so this is going to be the rub, it looks like. I have multiple
projects and they DO depend on one another, but in a well defined
fashion, not cyclically. I guess my question is, what, in Maven, takes
the place of (or supplements) the Eclipse action of putting one project
on the build path of another?
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
