Ömer Faruk Almalı
Ömer Faruk Almalı

Reputation: 3822

ClearCase not working via Intellij Idea

Intellij Idea 12.1.4, Windows 7 Professional.

It seems bundled ClearCase Intellij Idea plugin not working at all. When I try to checkout(or type sth. in a file which is not checked out or hijacked) Idea says:

Cannot edit file(s): cleartool: Error: Not an object in a vob: {File path}

Actually this is an error that I am expecting because I couldn't find any ClearCase configuration that I can type my user name and password in Intellij Idea:

enter image description here

That's why it doesn't know where to connect and retrieve data. So question is, where are the correct configurations? Should I prepare a script for SCR text file or is Intellij Idea plugin useless?

Upvotes: 1

Views: 905

Answers (3)

user1396544
user1396544

Reputation: 21

Go to Settings, click on "Version Control". In the right-hand pane you need to add a Directory/VCS configuration tuple. Do this by pressing the green PLUS (+) icon.

Select "Project" and select "Clearcase" as Source Control tool. You should now have a context menu item "Clearcase" in your IDE and can check out files by right-clicking on the file. One small disadvantage in my Intellij 12.1.6 is that he only sees the change sets (Activities) that were created using Clearcase Explorer... (only loaded at startup time of Intellij). So you cannot add new change sets that will be propagated to Clearcase.

Upvotes: 0

vikingsteve
vikingsteve

Reputation: 40388

I know this is a contrite answer but the best advice really is: Don't use ClearCase.

Save your organization the headache and make the effort to switch over.

Anything will do, even svn.

Upvotes: 1

VonC
VonC

Reputation: 1324505

Try first to fall back to cleartool (the ClearCase CLI -- command Line Interface), and check if your view is correctly configured.

cd /path/to/your/file
cleartool ls

That will allow you to see the config spec selection rule for that file.
And that will give you a clue for that "Not an object in a vob" error message: maybe the issue isn't in the plugin, but in your current view.

Upvotes: 1

Related Questions