Bug 74880

Summary: clearcase integration with Kdevelop should use /vobs path
Product: [Applications] kdevelop Reporter: umesh <umesh>
Component: VCS: ClearcaseAssignee: kdevelop-bugs-null
Status: RESOLVED FIXED    
Severity: normal    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Improvements for ClearCase integration

Description umesh 2004-02-10 22:05:06 UTC
Version:            (using KDE KDE 3.2.0)
Installed from:    Compiled From Sources
Compiler:          Redhat 7.3 
OS:          Linux

We have a pre-existing environment where we havily rely on /vobs directory path for build. Latest kdevelop can checkin and checkout files from the vob however I have to use /view path which does not work in our build environment. Actually bringing up kdevelop from a mounted view gives an error (file protocol died). I am assuming that there is some type of issue between Kioslave and mounted vobs. I and I am sure several other users will love to see this great tool be usable with clearcase.
Comment 1 patrickn 2005-09-28 07:41:45 UTC
Created attachment 12745 [details]
Improvements for ClearCase integration

This patch supports :
* adding new entries in the clearcase menu
* detects the clearcase environment and activates the menu. It does not
check a hard coded path anymore! 
* adds the clearcase VCS file infos
* enables VCS synchronisation when right clicking on a folder...
Comment 2 Daniel Schmitt 2006-03-06 21:40:29 UTC
Yes, the hardcoded path does not work in our enviroment too.
I am desperatly waiting for patrickn's path to be included
kind regards
Daniel
Comment 3 Alexander Dymo 2006-03-14 23:24:41 UTC
SVN commit 518696 by dymo:

Applied patch from Patrick Noffke: use vobs/ paths in clearcase.
BUG: 74880



 M  +2 -1      Makefile.am  
 M  +16 -6     README.dox  
 M  +111 -47   clearcasepart.cpp  
 M  +13 -7     clearcasepart.h  
Comment 4 LuRan 2006-03-16 13:56:51 UTC
it seems some files are still missing, cannot compile
Comment 5 patrickn 2006-03-17 03:58:51 UTC
What version of kdevelop was the patch applied to?  What version did LuRan test with?  I patched 3.2.0 and just did an svn up, and the files above are still showing as modified.  Please let me know the version patched and I will attempt to fix any problems.
Comment 6 Matt Rogers 2006-03-17 04:08:19 UTC
branches/kdevelop/3.4 is where the changes went
Comment 7 LuRan 2006-03-18 03:47:39 UTC
patrick: I'm not refer to your patch, but the svn commit failed to add all the files, after apply the rest of the patch by hand everything is fine.
Comment 8 Alexander Dymo 2006-03-18 11:00:18 UTC
SVN commit 519905 by dymo:

Added missing files.
CCBUG: 74880


 A             clearcasefileinfoprovider.cpp   [License: UNKNOWN]
 A             clearcasefileinfoprovider.h   [License: UNKNOWN]
 A             clearcasemanipulator.cpp   [POSSIBLY UNSAFE: system,popen] [License: UNKNOWN]
 A             clearcasemanipulator.h   [License: UNKNOWN]
Comment 9 patrickn 2006-03-20 01:56:08 UTC
Alexander, thank you for adding the missing files.  I'm aware the method for running the cleartool process is not the best (starts process and blocks until completion in the retrieveFilesInfos function).  I didn't write this bit, but I'm happy to attempt a fix if someone can suggest the "proper" way to do this.  

The problem is when you right click on a file, it takes a while to run cleartool so the context menu takes some time to appear (feels unresponsive).  It would probably be best to grab the vcs state information in the background (or on startup and when something changes -- possibly outside of kdevelop).  But I am not yet familiar enough with the kdevelop architecture to make such a change.  Is there a reference I can peruse to understand the architecture, or could someone suggest a few pointers on how to approach this problem?

Additionally, how does all this fit with the ioslave work on clearcase integration (http://klearcase.sourceforge.net)?  Is it feasible to combine these two efforts, or is kdevelop's architecture not compatible with the ioslave architecture?
Comment 10 Alexander Dymo 2006-03-20 10:16:11 UTC
All API docs we have is at http://www.kdevelop.org/HEAD/doc/platform/html/. Not very much docs though.
I'd say you can use QThread to run background job after the plugin has started which would collect file state. 
But if the ioslave can give you this information, you can certainly use it. Take a look at vcs/subversion. That plugin already uses svn ioslave.