When the VS project files are created, we need to be able to specify the default namespace for new classes. This must be inferred either through the groupId or the artifactId.
Typically, for .NET projects, the artifact name is something like: <Company>.<Project> or <Company>.<Department>.<Project> or most commonly <Project>.<Module> If this artifactId convention matches what you want for a namespace, you can give whatever groupId you want. Personally I prefer the standard maven group id, like we did for NUnit. Since we are signing and releasing the artifact, we use our own groupId. http://people.apache.org/repo/m2-snapshot-repository/org/apache/maven/dotnet/NUnit.Framework/ This is cleaner organization for those projects that have both Java and .NET artifacts, otherwise we end up with the same group ids, one capitalized and one not. Shane On Fri, May 30, 2008 at 5:56 AM, Brian E. Fox <[EMAIL PROTECTED]> wrote: > > >So... does Microsoft.NET.Framework sound okay for a groupId? > I would prefer com.microsoft.dotnet.framework > >
