On 4/24/07, Howard Lewis Ship <[EMAIL PROTECTED]> wrote:
Eclipse doesn't do nested projects, otherwise I would structure it that way. And it is important to me to allow everything to be built seperately and in layers (I expect tapestry-ioc to be used outside of Tapestry, for example).
Eclipse works nicely with netsted maven2 projects with m2eclipse plugin, i use it day to day. You can define your mvn modules (and submodules) as beeing mvn projects (pom.xml), checkout the correct directory(subdirectory) and Eclipse will work out smoothly. There's nothing to do about that. Mule has that structure and is very nice to work within Eclipse, even with that number of modules/submodules. Another bonus is that with that structure the realase procedure is neat. It's obviously true that if you plan to release tapestry-ioc as a separate project and not directly tighted to tapestry-core it's better to have it on a separate dir structure. Regards -- Massimo http://meridio.blogspot.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
