Done. MNG-359 has been closed. On 5/26/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > > Brett, > > IMHO, the "../" path in <modules> would really be helpful. I imagine that > it does not add a big implementation problem, and it would solve the issue > of the flat layout of Eclipse. > > My problem is that the company I'm working for only uses WSAD. I'm > currently working on spreading Maven all over hundreds of Java projects, > and I want it to be as simple as possible. And having the root POM outside > of the workspace is not an acceptable solution: people will want to edit it > in WSAD, they will need to have it in CVS and handled like any other source > file, ...etc. > I agree that the issue for Eclipse project organization is interesting. But > before anything gets changed in WSAD, it will take a lot of time. For the > time being, Eclipse forces us to have 1 project = 1 CVS module, and > therefore, the root POM must be in a separate project. > > If m2 can't handle flat layout for multiprojects, I won't be able to spread > it over the hundreds of teams, and that'd be sad because it looks great... > :o| > We see that Eclipse is not flexible enough. Maven should prove more > flexiblility than Eclipse and not force a special layout for multiprojects > (m1 used to be that flexible!). > > I do hope something can be done this way... or I will need to find another > company to use m2 ;o) > > Thanks & best regards, > Fabrice >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
