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 11638 - jarpackager template iterator does not recognize existing manifests
Summary: jarpackager template iterator does not recognize existing manifests
Status: CLOSED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: jarpackager (show other bugs)
Version: 3.x
Hardware: PC Linux
: P4 blocker (vote)
Assignee: issues@obsolete
URL: http://www.netbeans.org/source/browse...
Keywords:
Depends on:
Blocks:
 
Reported: 2001-04-22 10:17 UTC by Jesse Glick
Modified: 2003-07-01 10:00 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Jesse Glick 2001-04-22 10:17:51 UTC 
[release32 apr 20] When providing a custom .jarContent as a template,
the jarpackager's wizard iterator does not work well--it initializes
e.g. the manifest to a blank manifest even though a nonblank one was
provided in the template. Prevents this iterator from being used in
apisupport.
Comment 1 Mike Schilling 2001-04-23 18:18:16 UTC 
How do you get the custom wizard panels to be used for a non-starndard template?  
I tried saving a jarcontent as a template and creating a new one from it, but 
the standard wizard (select package and name only) came up, not the customized 
one.
Comment 2 Jesse Glick 2001-04-24 17:29:10 UTC 
See attached URL, look for attr on Templates/Modules_API/Module.jarContent.
Comment 3 Mike Schilling 2001-05-01 23:32:01 UTC 
Contents and manifest from template are now displayed in wizard.  (It makes no 
sense to hardcode a jar file location in the template.)
Comment 4 Jan Chalupa 2001-05-05 23:11:39 UTC 
Target milestone -> 3.3
Removing the OPEN_IN_3.2 keyword.
Comment 5 Jesse Glick 2001-09-29 10:30:51 UTC 
Thanks, apisupport now using this template iterator for the Module JAR
and it seems to work.
Comment 6 Quality Engineering 2003-07-01 09:59:06 UTC 
Resolved for 3.4 or earlier, no new info since then -> closing.
Comment 7 Quality Engineering 2003-07-01 10:00:17 UTC 
Resolved for 3.4 or earlier, no new info since then -> closing.