In Project.translateN32Drools(), no exception handling and recovery is done.
So the method completely exits on error.
It is probably a brutal solution.
A better alternative is to try to parse the other N3Sources, and just highlight the fact that
a given set of N3Sources have failed.
It is probably the correct behaviour when dealing with N3Sources for a project.
But how to handle the N3 parsing problems when loading the .n3p in the ApplicationKB?
May be we should try to load as many N3Sources as possible. And then rethrow one Exception
containing all the N3Sources that have failed.