188242 – Plug-in Dependencies missing project reference after loading pre-defined target

Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 188242 - Plug-in Dependencies missing project reference after loading pre-defined target

Summary: Plug-in Dependencies missing project reference after loading pre-defined target

Status:	RESOLVED DUPLICATE of bug 183260

Alias:	None

Product:	PDE
Classification:	Eclipse Project
Component:	UI (show other bugs)
Version:	3.3
Hardware:	PC Windows XP

Importance:	P2 normal (vote)
Target Milestone:	---
Assignee:	PDE-UI-Inbox
QA Contact:

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Reported:	2007-05-22 04:36 EDT by Jerome Lanneluc
Modified:	2007-05-22 16:28 EDT (History)
CC List:	2 users (show)

See Also:

Attachments
Manifest for com.ibm.x.y.fragment.win32 (553 bytes, application/octet-stream) 2007-05-22 04:37 EDT, Jerome Lanneluc	no flags	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Jerome Lanneluc

2007-05-22 04:36:33 EDT

3.3 M6

1. Plug-in com.ibm.z requires com.ibm.x.y
2. com.ibm.x.y has a fragment com.ibm.x.y.fragment.win32
3. The Plug-in Dependencies in the Package explorer correctly shows 2 project references (1 reference to com.ibm.x.y, 1 reference to com.ibm.x.y.fragment.win32)
4. When loading a pre-defined target (Preferences > Plug-in Development > Target Platform), the reference to com.ibm.x.y.fragment.win32 is removed from the Plug-in Dependencies. This results in compile errors in com.ibm.z.

Comment 1 Jerome Lanneluc

2007-05-22 04:37:15 EDT

Created attachment 68078 [details]
Manifest for com.ibm.x.y.fragment.win32

Comment 2 Wassim Melhem

2007-05-22 08:25:36 EDT

Jerome, what is this "pre-defined target"?

Comment 3 Wassim Melhem

2007-05-22 08:26:35 EDT

to clarify comment 2:

does the pre-defined target contain such a fragment?
after loading that target, is the *.win32 fragment checked on the Target Platform preference page?

Comment 4 Philipe Mulet

2007-05-22 09:30:20 EDT

Raising priority so it doesn't get lost. This is an important scenario.

Comment 5 Philipe Mulet

2007-05-22 09:30:46 EDT

Can we fix it for 3.3 ?

Comment 6 Jerome Lanneluc

2007-05-22 09:51:54 EDT

(In reply to comment #3)
> to clarify comment 2:
> 
> does the pre-defined target contain such a fragment?
> after loading that target, is the *.win32 fragment checked on the Target
> Platform preference page?
> 
Indeed com.ibm.x.y.fragment.win32 is not listed. However com.ibm.x.y is not listed either and it is still referenced in the Plug-in Dependencies.

Comment 7 Wassim Melhem

2007-05-22 10:01:32 EDT

oh I see.  They are not listed on the Target Platform pref page, but they are both in your workspace.  Fine then.

I suspect it's a general target switching thing (bug 183260), which is already fixed.

I will confirm though.

Comment 8 Wassim Melhem

2007-05-22 16:28:18 EDT

Yes, I verified that the problem is already fixed in M7 (bug 183260).

For reference, here is a scenario that fails on M6 but passes on M7:

1. Fresh workspace
2. Create a fragment (com.example.fragment) project.  Set its host to org.eclipse.swt 3.3.0
3. Create a new Hello world (com.example.abc) plug-in project.  Note how com.example.fragment is on its classpath.  Good.

4. Go to the Target Platform preference page and change the location to that of another Eclipse installation.  Press OK.

On M6, com.example.abc loses its reference to com.example.fragment
On M7, com.example.abc retains its reference to com.example.fragment

*** This bug has been marked as a duplicate of bug 183260 ***