Bug 215253

Summary:	[Change Sets] Got an error in the .log file using change sets
Product:	[Eclipse Project] Platform	Reporter:	Olivier Thomann <Olivier_Thomann>
Component:	Team	Assignee:	Platform Team Inbox <platform-team-inbox>
Status:	NEW ---	QA Contact:
Severity:	normal
Priority:	P3	CC:	darin.eclipse
Version:	3.4
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Olivier Thomann

2008-01-14 15:08:47 EST

Using eclipse.buildId=I20080108-1320
java.fullversion=J2RE 1.6.0 IBM J9 2.4 Windows XP x86-32 jvmwi3260-20071121_15015 (JIT enabled)
J9VM - 20071121_015015_lHdSMR
JIT  - r9_20071121_1330
GC   - 20071031_AA
BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=fr_CA
Framework arguments:  -showlocation
Command-line arguments:  -os win32 -ws win32 -arch x86 -consolelog -console -showlocation,

I got this error four times in the .log file.
I think I wanted to open the popup menu. Not sure about this.

No property tester contributes a property projectNature to type class org.eclipse.team.internal.ccvs.core.mapping.UnassignedDiffChangeSet

Comment 1 Olivier Thomann

2008-01-14 15:13:26 EST

This happens when I have the synchronize view open with an unassigned changed set and I try to open the debug menu.
Could be a problem in debug as well.

Comment 2 Olivier Thomann

2008-01-14 15:15:01 EST

It doesn't occur anymore as soon as I assign the change set.

Comment 3 Olivier Thomann

2008-01-14 15:16:23 EST

I was wrong. When the change set is assigned, I get:
No property tester contributes a property projectNature to type class org.eclipse.team.internal.ccvs.core.mapping.CVSActiveChangeSet

Comment 4 Tomasz Zarna

2008-01-15 06:59:32 EST

Olivier, I've tried couple of times to reproduce the error you got, with no luck so far. Can you think of anything specific about your configuration? Eg. Could you attach your Configuration Details?

Comment 5 Eclipse Webmaster

2019-09-06 16:11:04 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.