1
Vote

New project types

description

I am getting an error when I try and import a solution with a Database project type. It says "The given key is not present in the dictionary". A better error would be nice, took me a while to figure out what that meant.
 
Also I was wondering if it would be possible to say that the project, give the name, is not supported and skip it and import the other projects.
 
In this example the DB project type should be skipped by nPanday as there is nothing for it to compile. MSBuild skips this project type when it compiles. But if it would tell you that Project A is not supported by the importer, but import Project B and C, then I could go and write the pom for Project A by hand and modify the parent pom as needed as well.
 
I think that would be a really flexible option.
 
The GUID for the db project type is 4F174C21-8C12-11D0-8340-0000F80270F8.

comments

wsmoak wrote Feb 19, 2009 at 11:16 PM

Also I was wondering if it would be possible to say that the project, give the name, is not supported and skip it and import the other projects.
This is actually one of the points on the wiki page over at NMaven...

http://docs.codehaus.org/display/MAVENUSER/NMaven+Project+Importer

The NMaven Visual Studio Addin has the ability to import Visual Studio solutions and generate NMaven POM files.
...

The Project Importer should skip modules it doesn't understand and print a warning message, rather than stopping.

Wendy