[
https://issues.apache.org/jira/browse/NPANDAY-77?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated NPANDAY-77:
--------------------------------
Fix Version/s: (was: Backlog)
1.4.1-incubating
need to double check this. The key problem would mean that it is recognised by
the digester, but not the converter.
> New project types (support Database Projects?)
> ----------------------------------------------
>
> Key: NPANDAY-77
> URL: https://issues.apache.org/jira/browse/NPANDAY-77
> Project: NPanday
> Issue Type: Bug
> Reporter: cbown75
> Priority: Minor
> Fix For: 1.4.1-incubating
>
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
