[#IDEA-16529] Files are considered unversioned when modified

IDEA: Feedback

Files are considered unversioned when modified

Created: 27 Nov 07 18:48 Updated: 03 Jan 08 12:23

Component/s:

Version Control Integration. ClearCase

Environment:

Windows 2000

Build:	7,361
Severity:	Medium

Description

« Hide

When a file under ClearCase version control is modified inside IDEA, it is considered unversioned by the ClearCase integration module and will have to be added again. This is in a snapshot view and a large multi-module project.

This is a rather annoying bug because it breaks the change lists.

All

Comments

Work Log

Change History

Sort Order:

[ Permlink | « Hide ]

Manne Fagerlind - 28 Nov 07 10:02

I just discovered that it's impossible to add the files a second time when the IDEA has mistakenly labeled them as unversioned, which makes the ClearCase integration almost useless for me - I have to use the ClearCase explorer to manage files.

If other people have the same problem the severity should probably be 'High', but I leave that for Jetbrains to decide.

[ Permlink | « Hide ]

Wim Deblauwe - 18 Dec 07 18:02

I have the same problem with check out of a (unit) test file from IDEA itself. It seems IntelliJ does not do a checkout on those files (although it works perfectly for my normal production source files) but a hijack. Then IDEA thinks it is unversioned and I have the same problem defined here.

[ Permlink | « Hide ]

Gunnar Gunnarsson - 03 Jan 08 12:23

I see the same problem, and I think it is serious. When it occurs, the affected developer often does not notice immediately, so a multi-file change is checked in partially, which causes strange and time-consuming problems for other designers.