I have never used the sub-project structure and as nearly as I can tell
have suffered no ill-affects for the past 8 + years.
Ron
On 20/03/2016 12:52 PM, Jason Franklin wrote:
I decided to just go with the inelegant solution of building a new
project and adding submodules into which I clicked and dragged the
source code I needed. So the problem is solved.
It looks like this in IDEA now:
-- parent
-- sub-module 1
-- sub-module 2
-- etc.
Perhaps I'm not using Maven in the spirit it was intended... I noticed
in the POM reference that you can declare a parent project and, in the
<module /> element, specify its aggregated projects with a relative
pathname (meaning the modules don't need to be subdirectories of the
parent). Similarly, I saw that an inheriting pom.xml can use relative
pathnames in its <parent /> element.
So, it is possible to "relate" projects strongly without unifying them
into a directory hierarchy of IDEA project files. Then, the user can
import multiple projects that are then shown as a list in the project
explorer. I was hoping that the IDEA Maven plugin would unify all of my
projects for me when I declared the relationship. However, given the
observation in the previous paragraph, there must be situations in which
this behavior is undesirable. And, there are probably very few
situations where this is really required given Maven's ability to relate
projects with such flexibility.
Maven by Example makes it seem as though the directory hierarchy for
parent/submodule projects is highly desirable (if not required).
Correct analysis?
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
