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 64325 - remains after remove/move ejb project
Summary: remains after remove/move ejb project
Status: RESOLVED FIXED
Alias: None
Product: javaee
Classification: Unclassified
Component: EJB Project (show other bugs)
Version: 5.x
Hardware: All All
: P3 blocker (vote)
Assignee: Andrei Badea
URL:
Keywords:
Depends on: 65141
Blocks:
  Show dependency tree
 
Reported: 2005-09-14 11:09 UTC by L Martinek
Modified: 2005-10-03 14:39 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 L Martinek 2005-09-14 11:09:11 UTC
Rename EJB Project or move it to another directory. Project on new location is
created, but nbproject and build.xml remains in old location.
Comment 1 L Martinek 2005-09-14 12:50:51 UTC
Same for renaming of EJB project from existing sources. If project folder
resides in the same directory as sources then nbproject and build.xml isn't
deleted. If project folder is in another directory then only build.xml isn't
deleted.
Comment 2 Andrei Badea 2005-09-14 16:15:43 UTC
I experience similar issues in the web project. They seem caused by the project
listening to javac.classpath in order to set the library locations to
private.properties. 
Comment 3 Andrei Badea 2005-09-15 15:25:55 UTC
Fixed by Radko while fixing issue 64315.
Comment 4 L Martinek 2005-09-23 16:09:29 UTC
Rename/move of standard EJB Module is working properly. 

When I tried to rename EJB Module with existing sources where project folder
resides in the same directory as sources then sources was copied to new project
location, but old sources wasn't deleted and even more they were used. There is
a question whether sources should be actually moved, but current solution where
sources are copied, but never used is not correct.

Comment 5 Andrei Badea 2005-09-26 16:41:56 UTC
This has two causes:

- the existing source folder is referenced using an absolute path, although it
is in the project directory and a relative path would be enough. Not sure this
is as designed.

- when the original project is deleted, the source folder cannot be deleted
because it is now owned by the copy of the project

Will investigate more, jlahoda is helping with this.
Comment 6 Andrei Badea 2005-09-26 17:33:49 UTC
This must be fixed in projects, filed issue 65141.
Comment 7 Andrei Badea 2005-10-03 14:39:34 UTC
Fixed by the fix of issue 65141. Note that while verifying you may experience
issue 65406, which may have been revealed by the fix of issue 65141 (I've never
seen it before).