This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
| Summary: | java.io.IOException: Duplicated attributes in a section: OpenIDE-Module-Specification-Version | ||
|---|---|---|---|
| Product: | apisupport | Reporter: | Michel Graciano <hmichel> |
| Component: | Project | Assignee: | Martin Kozeny <mkozeny> |
| Status: | RESOLVED WONTFIX | ||
| Severity: | blocker | CC: | jglick |
| Priority: | P4 | ||
| Version: | 6.x | ||
| Hardware: | All | ||
| OS: | All | ||
| URL: | http://statistics.netbeans.org/exceptions/detail.do?id=33583 | ||
| Issue Type: | DEFECT | Exception Reporter: | 33583 |
So, do you in fact have that attribute duplicated? Any way to reproduce? *** Issue 129200 has been marked as a duplicate of this issue. *** To reproduce it just edit the file by hand. IMHO, IMHO, it should show a message instead a exception. Edit it to say what? Can you tell me what it is you did? Steps to reproduce: 1-Open a manifest.mf file which already have a 'OpenIDE-Module-Specification-Version' entry; 2-Add another one 'OpenIDE-Module-Specification-Version'; 3-The exception is thrown. Regards. I see. It's true that we do not go to lengths to fix up malformed metadata files. Generally the GUI customizers assume they are starting with well-formed data. Not into 7.0 or next release. Feel free to reopen if more important than it seems. IMO, the point here is not if it is really important or not from my point of view, but if this kind of behaviour is expected from a professional tool or not. I believe that, since we have a way to know that there is a error and we can inform the user about the problem and a way to solve it, why not do it? I believe we, developers, never should expect the correct data from users always they could corrupt it. Validations always must be done in this cases to make the tool as robust as possible. Probably it could be a enhancement instead a issue, since we know that UI will always generate valid artifacts, but never believe that user will give valid data. Regards I absolutely agree that no application should throw exceptions on corrupted input file and issues closed as LATER are meant to be reopened in the future, e.g. as part of larger development in that particular area. At present this is merely a matter of priorities, there is simply not enough people to tackle all problems at once. Last but not least we are always grateful for patches for such issues, NetBeans are free software after all. NetBeans.org Migration: changing resolution from LATER to WONTFIX Closed spuriously, still valid. WONTFIX simirarly as here https://netbeans.org/bugzilla/show_bug.cgi?id=167540. |
Build: NetBeans IDE Dev (Build 200803021202) VM: Java HotSpot(TM) Client VM, 1.6.0_03-b05 OS: Linux, 2.6.22-14-generic, i386 User comments: STACKTRACE: (first 10 lines) java.io.IOException: Duplicated attributes in a section: OpenIDE-Module-Specification-Version at org.netbeans.modules.apisupport.project.EditableManifest$Section.<init>(EditableManifest.java:372) at org.netbeans.modules.apisupport.project.EditableManifest.<init>(EditableManifest.java:110) at org.netbeans.modules.apisupport.project.Util.loadManifest(Util.java:558) at org.netbeans.modules.apisupport.project.ui.customizer.SingleModuleProperties.storeManifestChanges(SingleModuleProperties.java:771) at org.netbeans.modules.apisupport.project.ui.customizer.SingleModuleProperties.storeProperties(SingleModuleProperties.java:687) at org.netbeans.modules.apisupport.project.ui.customizer.CustomizerProviderImpl.storeProperties(CustomizerProviderImpl.java:87) at org.netbeans.modules.apisupport.project.ui.customizer.BasicCustomizer$1.run(BasicCustomizer.java:152) at org.netbeans.modules.apisupport.project.ui.customizer.BasicCustomizer$1.run(BasicCustomizer.java:151) at org.openide.util.Mutex.writeAccess(Mutex.java:433) at org.openide.util.Mutex$1R.run(Mutex.java:1305)