Bug 6760 - package names truncated in compilation dialog
Summary: package names truncated in compilation dialog
Status: RESOLVED FIXED
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows 2000
: P3 normal (vote)
Target Milestone: 2.0 M2   Edit
Assignee: Kent Johnson CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-10 14:43 EST by David Buttler CLA
Modified: 2002-01-11 08:57 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Buttler CLA 2001-12-10 14:43:20 EST
When creating a new project from  sources in a pre-existing source folder, I
have seen the package names prefix-truncated: the first one or more letters are
removed.
For instance, compling the JTidy package gives a message like:
compiling idy...
Compiling my own packages removes the first few qualifications
(edu.gatech.disl.djb.log becomes disl.djb.log)
Comment 1 Philipe Mulet CLA 2001-12-10 17:31:59 EST
Which build was this ? Do you notice this in all progress dialogs or just the 
one during compilation ?
Comment 2 David Buttler CLA 2001-12-10 20:16:21 EST
This was with build 
20011206 stable
(win2k, jdk1.3.1_01)

I only noticed this in the compilation dialog, but I didn't look at many others
Comment 3 David Buttler CLA 2001-12-10 20:55:18 EST
I did not see this problem in refresh from local (on my home machine -- Win98)
It seems to only crop up when creating a new project and pointing the source
folder to a pre-existing project (Something I do fairly frequently since I have
set up eclipse on several machines, and I have been trying to follow the stable
builds)
Comment 4 Kent Johnson CLA 2001-12-11 11:19:38 EST
Was the project external to the workspace?

If so then this problem was fixed a few days ago.
Comment 5 David Buttler CLA 2001-12-11 11:26:35 EST
Yes, all of my projects are external to the workspace.  Keeping the projects
under the workspace is limiting; it seems especially bad for running eclipse
over a network drive (if the network is not running at optimal efficiency,
eclipse really really slows down when the metadata is not local)
Comment 6 Kent Johnson CLA 2001-12-11 12:03:14 EST
Closed, fixed last Friday, Dec. 7th.