On Wed, May 21, 2008 at 5:27 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On Tue, May 20, 2008 at 8:09 PM, Shane Isbell <[EMAIL PROTECTED]> wrote: > >> You can have flat directory structures, with a parent pom one level up. > > That's not flat. :) The parent pom would be a sibling of the modules > rather than above it. > > The problem I see with the existing project I was talking about is > that those sibling modules directly contain the .csproj file, some .cs > files, and a directory with more code beneath. There's nowhere to put > the pom.xml file. > > -- > Wendy >
>From the 0.15 examples/archetypes I've looked at it seems that the pom.xml can go in the same directory as the code and project file. I personally don't like this (coming from Java/Maven conventions) but it appears to work (with the 0.15 version at least) and seems in line with the VS conventions mentioned in this thread. Another question is where to put test code using a structure like this (with main artifact code in the root directory)? What is the mainstream .NET/VS convention for this? E.g. will it work with sources in "." and tests in "src/test" (or whatever)? The .NET team I'm working with tends to create separate projects for tests since, using their old style environment, test code in the same project would become part of the main artifact - which should not be the case when using a tool like NMaven. -- - Jan Fredrik Wedén
