Is it normal to get a dump for invalid char in manifest.mf? [message #1007443] |
Tue, 05 February 2013 16:18  |
Eclipse User |
|
|
|
Our platform is using Virgo 3.0.3 and our users are developers building extensions as plugin bundles. They often discover the hard-way that their bundle's MANIFEST.MF is very sensitive to bad syntax (our doc explains how to use a tool like bundlor to generate it but some of them still edit the manifest manually to add package names).
I just ran into a case where an extra tab at the end of a package name in "Import-Package" got Virgo to generate a huge dump file instead of giving the parsing error directly in the log. This is bad because our users will not necessarily know where to look for the actual error. So I have a couple questions:
1) Is it normal for Virgo to generate a dump file instead of a parsing error in the log?
2) Is Virgo 3.6.x more robust and forgiving than 3.0.x regarding the Manifest.mf syntax?
Thanks!
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03815 seconds