+1
When I have to justify Maven's defaults I say it's consistency that
matters, not the actual choice of location. So it makes sense to start
out with a choice that works for most people.
The only downside is that it will be less familiar with Java Maven
users - but I don't think that's an overriding concern.
How do you specify this default though? Just what is in the Archetype,
or are there pieces of plugin configuration that will take these
paths? I would have assumed most was coded into the POM <build>
section which unfortunately takes the Java settings from the super POM
- perhaps those defaults really need to be mixed in by Maven based on
packaging type.
- Brett
On 13/12/2007, at 8:30 AM, Shane Isbell wrote:
Unless there are any objections, I'm going to make the flat directory
structure layout the default layout. This will make it much easier for
current .NET developers to just drop in a pom into their existing
projects
and have NMaven work.
Shane
On Nov 15, 2007 12:14 PM, Shane Isbell <[EMAIL PROTECTED]> wrote:
Could I get a quick poll of what is the preferred directory layout
for
NMaven projects? Currently, we have both the typical Maven style
project
layout src/main/csharp and src/test/csharp and so on and also the
VS2005
format, which is flat, with just a single Test directory at the
same level
as the module's classes. Currently, we support both, but the
typical Maven
layout is troublesome when dealing with Visual Studio (or
SharpDevelop).
Does anyone see any problems with moving to a single, flat directory
structure for our standard? We could still support the typical
Maven style
layout for command line, it would just be that anything that
requires IDE
support would be required to have a flat project structure.
Thanks,
Shane
