On Thu, Jun 26, 2008 at 8:00 PM, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On Thu, Jun 26, 2008 at 3:56 AM, Wendy Smoak <[EMAIL PROTECTED]> wrote: > > > Not sure about the implementation, just that I end up with two .csproj > > files after importing. It probably uses JavaBinding behind the > > scenes. > > Sorry. I'm getting the pom generation and solution generation all > mixed up. JavaBinding and Project Import don't seem to trigger the > right definition for me... > > If the project already has poms, and we are generating the solution, > then I think we should assume it's primarily going to be built with > NMaven and _not_ generate a second .csproj file for the tests. If the > person wants a separate project for the tests, they should write a > separate pom before generating the solution. > > If we have solution/project files and are generating poms, then it's > 1:1 for ..csproj/.vbproj to pom.xml, plus one pom.xml for the .sln > unless it is combined with a .csproj/.vbproj. > > WDYT? I think that should be ok. > > > -- > Wendy >
