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 30432

Summary:	Incorrect target directory property value for newly added content items
Product:	obsolete	Reporter:	David Kaspar <dkaspar>
Component:	jarpackager	Assignee:	issues@obsolete <issues>
Status:	VERIFIED FIXED
Severity:	blocker	Keywords:	T9Y
Priority:	P3
Version:	3.x
Hardware:	PC
OS:	All
Issue Type:	DEFECT	Exception Reporter:

Description David Kaspar 2003-01-28 16:04:42 UTC

How to reproduce:
1) Invoke New From Template wizard
2) Select JAR Archives|JAR Recipe and press Next
3) Select some 2. level directory (for example:
sampledir/examples/imageviewer directory), press
Add button (one with right arrow)
4) Press Finish
5) See value of "Target Directory" and "Target
Name" property for added "imageviewer" item
6) ERROR - There is "<root>" resp. "imageviewer"
instead of "examples/imageviewer" resp. ""

This problem occurs for items that are added using
Contents Editor (in both cases: NewWizard and
Property editor).

This problem does not occur for items that are
added using Copy&Paste actions.

Comment 1 David Kaspar 2003-01-28 16:13:36 UTC

Raising priority because of T9Y keyword

Comment 2 Ondrej Rypacek 2003-01-28 16:54:57 UTC

fixed.
Changed org/netbeans/modules/jarpackager/ContentMemberListEditor.java

Comment 3 David Kaspar 2003-01-29 10:01:31 UTC

Reopening issue

Problem:
1) Try to create JAR Recipe and add some subdirectories of directories
in root of FS. Use older builds for this step (tested on #200301130100).
2) Start build #200301290100. Open Contents editor for created JAR Recipe.
3) ERROR - See table: there is "<root>" string in the second column of
the table
4) Press OK and try to compile - ERROR - Probably compiling error
occurs because of duplicated entries

Comment 4 Ondrej Rypacek 2003-01-29 10:56:31 UTC

fixed. Checked in org/netbeans/modules/jarpackager/ContentMember.java

Comment 5 David Kaspar 2003-02-12 14:51:49 UTC

Verified
In one case there is still problem - new bug has been filled so
setting this issue as verified.