On Fri, 2005-05-06 at 01:17 +1000, Brett Porter wrote: > I've not received one good reason why this is actually useful. "It
OK, I will (hopefully) give you some below. > I also don't agree with your overkill statement. More than it should > be perhaps, and Maven's mutliple project handling could be better, but > at the end of the day you are moving 1 or 2 directories and creating > two small files for the new subproject. That's not a lot for proper > separation of code and presentation. What about documentation? Where goes the xdoc stuff like changes.xml, index.xml and navigation.xml? Should they go in the master project, in the sub-projects or in both? And what if I have more than one of such projects (i.e., projects that had to be broken in multi-projects) in an hierarchy and then I need to run these now-multiprojects using multi-projects (i.e., I would have two levels of multiprojects). What about Eclipse? I can't have one project in one directory (the multi-project) and then 2 other projects in sub-directories. So, I understand your reasoning against this issue, but I think that if weight the pros and cons, there are more scenarios that would benefit from the change than the opposite. -- Felipe --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
