On Tue, May 20, 2008 at 8:09 PM, Brett Porter <[EMAIL PROTECTED]> wrote:
> ISTR that's what we agreed on, since it's pretty much the existing > convention in .NET projects due to the way the IDE tends to generate things. > Is that right? After working with this for a while, here's what I've come up with: http://docs.codehaus.org/display/MAVENUSER/NMaven+Project+Directory+Structure PROPOSAL: The following directory structures should be supported by NMaven command-line builds as well as the Visual Studio Addin. 1. Typical Maven single-module structure, single pom with separate source trees for code and tests. (Visual Studio seems to see the two source trees as separate "projects" each with a .csproj or .vbproj file.) 2. Typical Maven multi-module structure, parent pom with modules, subdirectories for modules, each module containing source and tests as in 1. 3. Visual Studio flat structure with .sln, .csproj (or .vbproj) and source code all in the same directory. 4. Visual Studio multi-module project with a parent pom containing modules, then a subdirectory for each module which equates to a VS "project". The .sln file sits beside the parent pom, and each subdirectory contains a .csproj, pom.xml and source code. Source code is not typically put in a subdirectory under the module, but it might be. (Still to come... ADO .NET and ASP .NET project structures.) Thoughts? In particular, is it reasonable for the VS Addin to support (1) and (2)? Thanks, -- Wendy
