Bug 105131 - [refactoring] moving classes with linked resources corrupts Java source
Summary: [refactoring] moving classes with linked resources corrupts Java source
Status: RESOLVED INVALID
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.1   Edit
Hardware: PC Windows XP
: P3 major (vote)
Target Milestone: ---   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: needinfo
Depends on:
Blocks:
 
Reported: 2005-07-26 05:55 EDT by Andreas Kinzler CLA
Modified: 2009-08-30 02:08 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andreas Kinzler CLA 2005-07-26 05:55:20 EDT
I'm using linked resources in a workspace to share certain Java source files in
many projects. When I refactor (move) classes that are references by shared
resources, the Java source code of these shared resources is corrupted (garbage,
syntax error).
Comment 1 Olivier Thomann CLA 2005-07-26 08:17:47 EDT
Would you have a specific test case to provide?
Comment 2 Andreas Kinzler CLA 2005-07-26 08:35:46 EDT
(In reply to comment #1)
> Would you have a specific test case to provide?

To reproduce a project like this should do:

ProjBase:
  src
    "some stuff1" (in my case: utility classes)
  linked folder to ProjEJB:"some stuff2" (filtered: only remote interfaces)
ProjEJB:
  src
    "some stuff2" (in my case: EJB 2.0 classes)
ProjServer:
  src
    "some stuff3" (does not matter)
  linked folder to ProjEJB:"some stuff2" (filtered: only local interfaces)

Then refactor (move) a class from "some stuff1" to some other package. Then
you'll experience corruptions in the import area of the interface classes like:

import a.b.c.SomeException;tion;tion;
Comment 3 Frederic Fusier CLA 2005-08-01 09:41:36 EDT
I cannot reproduce the problem, but strongly doubt I do the right thing...
There's something unclear in comment 0 and your sample in comment 2 is not
enough detailed to clarify it:
"When I refactor (move) classes that are references by shared resources..."
means that you have shared resources which are referencing resources in specific
project? In your example, this would mean that resources in "some stuff2"
reference resources in "some stuff1" and "some stuff3".

Would it be possible to create a simple example in a new workspace without any
specific pre-req configuration and attach it to this bug? This would help us to
find what exactly happen there, Thanks
Comment 4 Frederic Fusier CLA 2006-08-11 06:50:00 EDT
Please reopen if you still experience this issue and provide requested test case,
thanks
Comment 5 Denis Roy CLA 2009-08-30 02:08:21 EDT
As of now 'LATER' and 'REMIND' resolutions are no longer supported.
Please reopen this bug if it is still valid for you.