I've got a sprawling and unpleasant source tree that I'm moving into a Maven-based build, using the reactor to call each of the many sub-projects. I just want to clarify exactly how the reactor finds sub-projects - does it only look in the first level of subdirectories below the basedir or will it look in the second, third, etc? If it doesn't look into the deeper levels, can I make it do so somehow? Here's a quick glance at our directory structure:
\ \somedir1 \somedir1\projectA \somedir1\projectB \somedir1\somedir2\projectC \somedir1\somedir2\projectD \projectE
It's actually far more complex and ugly than that, with about another 30 to 40 projects at various levels, but that should give a sense of what I'm working with. Rearranging the source tree is a worst-case option at best, but if nothing else will work, I'll look into that option. Any suggestions/pointers?
A.
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
