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.

Bug 40550 - Request visual and/or syntax-checked manifest editor
Summary: Request visual and/or syntax-checked manifest editor
Status: NEW
Alias: None
Product: java
Classification: Unclassified
Component: Project (show other bugs)
Version: 3.x
Hardware: All All
: P3 blocker (vote)
Assignee: Tomas Zezula
URL:
Keywords:
: 52874 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-02-27 09:34 UTC by Ondrej Rypacek
Modified: 2011-08-31 14:05 UTC (History)
4 users (show)

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ondrej Rypacek 2004-02-27 09:34:13 UTC
The current manifest editor is confusing and
doesn't help much in the creation of a valid
manifest. In particullar, the presence of
automatically generated attributes suggests that
the editor is smarter than it is, that it is not
just a plain text editor. 

It would be nice to have an editor that does not
require a precise knowledge of Manifest grammar.
The editor should prevent creating syntactically
invalid manifest , not just disable the OK button.

One possible approach would be to present a
structured table (similar to the properties
editor) with separated main section and per-entry
sections, an extensive list of available
attributes (including all attributes listed in the
documentation) with some sort of automatic value
generation where possible (e.g. the Main-Class can
be generated by searching for static main method
in the sources).
Comment 1 Ondrej Rypacek 2004-02-27 09:35:28 UTC
See this thread for a relevant discussion
http://thread.gmane.org/gmane.comp.java.netbeans.cat36/406
Comment 2 Jesse Glick 2004-03-19 15:03:56 UTC
At least basic syntax validation and r/o display of attrs and sections
should not be hard. apisupport already does something like this. (It
does r/w manifests, actually, but does not preserve formatting on writes.)
Comment 3 Jesse Glick 2005-05-27 20:27:21 UTC
Should not have any open issues in jarpackager component.
Comment 4 Marian Mirilovic 2006-02-08 11:04:52 UTC
*** Issue 52874 has been marked as a duplicate of this issue. ***
Comment 5 Jesse Glick 2006-02-08 18:37:36 UTC
Update: apisupport/project now contains EditableManifest which (I hope) complies
with the spec but (unlike java.util.jar.Manifest) preserves formatting upon
structural edits.
Comment 6 Peter Pis 2008-08-19 12:12:15 UTC
Reassigning to "java".