Bug 118617

Summary:	[Viewers] no structure compare on .java and java-content-type file
Product:	[Eclipse Project] Platform	Reporter:	Martin Aeschlimann <martinae>
Component:	Compare	Assignee:	Platform-Compare-Inbox <platform-compare-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	tomasz.zarna
Version:	3.2
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:
Bug Depends on:
Bug Blocks:	89977

Description Martin Aeschlimann

2005-11-30 06:53:03 EST

20050930

Soon it will be possible to have files with extensions different than .java as a Java source files.

When org.eclipse.jdt.internal.core.util.Util.ENABLE_JAVA_LIKE_EXTENSIONS is set to true, new file associations can be added to the Java source content type.

Comparing 2 .java files automatically opens the Java structure compare view.
This doesn't work yet with new file extensions: Comparing a A.java with a B.foo file does only show the Java Source Compare.

Comment 1 Michael Valenta

2006-07-10 14:46:56 EDT

Excuse my lack of knowledge about JDT support for java-like files. Could you outline how you would expect this to work (i.e. are you only concernwed about the specific case of two differnet file types that both have a java content type or is there a more general problem).

Comment 2 Martin Aeschlimann

2006-07-11 04:03:19 EDT

See bug 89977 for the details.

Comment 3 Michael Valenta

2006-07-11 08:30:56 EDT

I see now. I was interpretting the original comment as meaning that the Java Source Compare was being used but shouldn't be. But what it is saying is that only the source compare appears and the strucuture compare is missing.

Comment 4 Tomasz Zarna

2008-10-14 05:50:19 EDT

Martin is this still an issue?

Comment 5 Martin Aeschlimann

2008-10-14 12:52:09 EDT

I don't know, I would have to test it again, but I'm out of the loop (not using Eclipse these times)

Comment 6 Eclipse Webmaster

2019-09-06 16:19:11 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.