I work on a project that has .NET and Java components and Maven and NMaven seem like a great way to combine the automated build process.
However, the biggest issue I face is that most of the .NET developers use Visual Studio to write code and run builds on their machines. A lot of our build steps are built into the csproj files. We use Visual Studio plugins to generate some of our code. These issues need to be addressed in NMaven. The dynamic code generation can be worked around by checking in generated files but the post build steps and other aspects of the .NET project have to be manually sync'ed. My first feature request would be being able to support csproj files in some way without requiring someone to maintain the POM. This could be done by parsing the csproj and generating a POM that provides the same functionality or any other means that is appropriate. I am aware of the feature whereby we can generate the csproj based on the POM but that is not the normal use case for a developer who starts with a csproj and wants a POM to reflect it. Amol On 8/27/07, Evan Worley <[EMAIL PROTECTED]> wrote: > I think the mailing list is slow in general because there is really only one > core developer, and I don't see the benefit in you having design discussions > with yourself :). If we can get more contributors involved, I think the > discussions will flow naturally. I continue to try to find time to get > acquainted, but I find I can rarely keep up. Now that things are becoming > more stable...?, it might be temping for people to get involved. > > I am personally very interested in seeing how the maven core can supports > .NET components. One great starting point would be implementing a surefire > provider for nunit, a task that his been proven difficult or at least > non-intuitive given the current surefire implementation. > > My 2 cents, > Evan > > On 8/26/07, Shane Isbell <[EMAIL PROTECTED]> wrote: > > > > I noticed the discussion on the mailing list has been a bit slow lately, > > even with the prospect of doing a release. Initially I had hopes to get to > > graduation within 12 months, but I realize from a community perspective we > > have a long way to go. So I wanted to get some feedback from everybody in > > terms of what they think we can do to improve the situation. > > > > I'm perfectly open to going back to the drawing board on any major issues. > > I had hoped that the architecture for doing .NET plugins would bring in > > .NET > > developers, but I don't see this happening. The platform matching is a > > pretty big chunk of code that the community may not find interesting, so I > > need to find out whether this should still be supported. RDF has, at best, > > gotten lukewarm acceptance. Finally, we have the big issue of how to bring > > .NET support into Maven itself. > > > > Should we just start compiling a list of features and decide whether we > > need > > them and then open up the design? > > > > Shane > > >
