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 16500 - Import of 3.2.1 project
Summary: Import of 3.2.1 project
Status: CLOSED FIXED
Alias: None
Product: platform
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 3.x
Hardware: PC Linux
: P1 blocker (vote)
Assignee: Jaroslav Tulach
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-10-12 11:33 UTC by Marek Grummich
Modified: 2008-12-22 16:17 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
ide.log (228.41 KB, text/plain)
2001-10-12 13:28 UTC, Jan Zajicek
Details
AutomountSupport rev. 1.28 seems to fix the problem (12.37 KB, application/octet-stream)
2001-10-17 16:04 UTC, Jaroslav Tulach
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Marek Grummich 2001-10-12 11:33:02 UTC
Build 200110120100
Jdk1.3.1
I have mounted following 3 filesystems in 3.2.1 project called "321_I":
/space/builds/userdir/321131/sampledir
/home/mg105252
src.jar

In  NB3.3 I have created project "NewProject_I" with these following mounted
filesystem:
/space/skladiste
/space/work

When I import and open project 321_I to NB3.3 then following filesystems are
mounted:
/space/builds/userdir/dev131/sampeldir
/home/mg105252
src.jar
ISSUE 1: WHERE IS THE /space/builds/userdir/321131/sampledir FILESYSTEM???
ISSUE 2: WHY THE /space/builds/userdir/dev131/sampeldir FILESYSTEM IS MOUNTED???
*****************************************
When I open/switch to an another project say "NewProject_I" these following
filesystems are mounted:
/space/skladiste
/space/work
/home/mg105252
src.jar
ISSUE 3: COMPARE WHICH FILESYSTEMS WERE MOUNTED IN PROJECT CALLED "NewProject_I"
AND NOW.
********************************************
ISSUE 4: WHEN I RESTARTED IDE THEN FILESYSTEMS WERE MOUNTED CORRECTLY
(/space/skladiste, /space/work), BUT SOME TAB WERE DUPLICATED IN THE EXPLORER.
THESE TABS WERE PRESENTED: FileSystems, Project NewProject_I, JavaDoc, Runtime,
FileSystems, JavaDoc, Runtime.
Comment 1 Vitezslav Stejskal 2001-10-12 12:54:41 UTC
It seems like a problem in automount. Jan Zajicek has more comments ...
Comment 2 Jan Zajicek 2001-10-12 12:58:31 UTC
I am able to reproduce the problem after import 3.2 project and then
switch back to 3.3 project too. Will attach log with debug output from
automount.
Comment 3 Jan Zajicek 2001-10-12 13:28:42 UTC
Created attachment 2987 [details]
ide.log
Comment 4 Jan Zajicek 2001-10-12 13:32:48 UTC
In the attached log are loged following steps:

1. start 3.3
2. mount - jar
3. mount - localfilesystem - note that it is placed before - reorder
problem - see issue #16513
4. import 3.2 project with all kinds of fss mounted
5. open this project - again note the reorder (fss are grouped
according to their types)
6. open 3.3 default project - note the fss merge

I checked the mounts folders on the disk in the projects directories -
there is everything ok.
Comment 5 Jaroslav Tulach 2001-10-12 14:05:32 UTC
Vita, I guess the problem with missing sampledir is not related to
automount support. You are just not importing the old sampledir and
also deleting the new sampledir, right?
Comment 6 Jan Zajicek 2001-10-12 14:12:20 UTC
There is filed separate issue #16501 against projects describing
general problems of sample filesystem.

Comment 7 Jaroslav Tulach 2001-10-15 19:14:32 UTC
FileSystems mounted via Repository.addFileSystem should disappear
after project switch. AutomountSupport rev. 1.26 Rest of the issue is
covered somewhere else.
Comment 8 Jan Zajicek 2001-10-16 11:05:33 UTC
Seems to me fixed in dev#20011016, do you agree Marek? If not, then
reopen. The problems with reorder still persist but this is another
issue which is already addressed.
Comment 9 Jaroslav Tulach 2001-10-17 16:04:41 UTC
Created attachment 3048 [details]
AutomountSupport rev. 1.28 seems to fix the problem
Comment 10 Quality Engineering 2003-07-01 16:49:58 UTC
Resolved for 3.4.x or earlier, no new info since then -> closing.