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 7460 - Only way to remove unwanted previously generated attribute in manifest is to delete it manually.
Summary: Only way to remove unwanted previously generated attribute in manifest is to ...
Status: CLOSED WONTFIX
Alias: None
Product: obsolete
Classification: Unclassified
Component: jarpackager (show other bugs)
Version: 3.x
Hardware: Other Other
: P4 normal (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2000-08-22 16:22 UTC by vnemec
Modified: 2003-07-02 17:17 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
empty attachment (2 bytes, text/plain)
2001-04-13 18:17 UTC, Mike Schilling
Details

Note You need to log in before you can comment on or make changes to this bug.
Description vnemec 2000-08-22 16:22:26 UTC
[main trunk]
UI of JarPackager 'manifest part' has changed - two CheckBoxes ('Generate Main
Attributes' and 'Generate File List' were replaced with one ComboBox
and 'Generate' button. Due to this change the only way to remove unwanted
generated attribute is to delete it manually. This is a bit annoying....
Comment 1 Mike Schilling 2001-04-13 18:17:12 UTC
Created attachment 1114 [details]
empty attachment
Comment 2 Milos Kleint 2002-04-25 11:28:22 UTC
I don't understand the point of the bug. Even though it might appear
"a bit annoying", it's just a different workflow.
If you don't want to use some of the attributes (there are 3 or 4
generated so it's definitely a minor problem to delete the unwanted
one), just create a manifest (or manifest template) of your own which
you then load when creating the jar recipe.

I think it's is not a bug at all, but rather a side effect of changed
workflow/design that appears strange to someone who was used to the
old design/workflow...
Comment 3 vnemec 2002-05-03 13:59:49 UTC
I hope you don't think it too seriously - this bug is almost two years
old... In the last century, when the bug was submitted, there were only
ONE existing workflow - good old JarPackager dialog with tvo tabs...
and somebody made minor change in UI design that brought more problems
and annoyances than improvement...  

so this bug is obsolete for almost one year, but not because anybody
is used to the old wokflow... :-)
Comment 4 Milos Kleint 2002-05-03 14:04:28 UTC
Bummer. You're still around ;)

I agree with you. The UI changed so the issue is obsolete.. anyway I'm
currently working on some changes that will make the current behaviour
obsolete as well.
Comment 5 David Kaspar 2002-10-30 10:22:23 UTC
Verified
Comment 6 Quality Engineering 2003-07-02 17:17:55 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.