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 20712 - Target not supported in readers
Summary: Target not supported in readers
Status: CLOSED FIXED
Alias: None
Product: obsolete
Classification: Unclassified
Component: jarpackager (show other bugs)
Version: -FFJ-
Hardware: All All
: P1 blocker (vote)
Assignee: issues@obsolete
URL:
Keywords:
Depends on:
Blocks: 20387
  Show dependency tree
 
Reported: 2002-02-20 14:15 UTC by Petr Jiricka
Modified: 2003-07-01 10:02 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Jiricka 2002-02-20 14:15:43 UTC
This was originally submitted as issue 20387.

in recent revisions to the jar packager, support for
ContentMember.{s,g}etTargetName was added. The tag library 
jar creation functionality relies on this feature, since it
must place a tag library jar into both META-INF/<filename>.tld and
META-INF/taglib.tld, so it must set the target name on the 
content member. 

However, ContentMember's saveDataObject and restoreDataObject
methods do not do anything with the target name. They will need
to save and restore the target name as well.
Comment 1 brinkley 2002-02-21 13:49:12 UTC
JarCreater creates a member set from the jar content's content list.
It loops through the content member set, and sees if the members are
data folders and recurses to add the children. It wasn't allowing
multiple names to be created because of a hash map. Now it is allowed. 

Need to test and verify that this is now working correctly.
Comment 2 David Kaspar 2002-02-21 16:22:26 UTC
Verified in main trunk
Comment 3 David Kaspar 2002-04-08 11:59:27 UTC
Verified in orion_fcs
Comment 4 Quality Engineering 2003-07-01 10:01:31 UTC
Resolved for 3.4 or earlier, no new info since then -> closing.
Comment 5 Quality Engineering 2003-07-01 10:02:30 UTC
Resolved for 3.4 or earlier, no new info since then -> closing.