Jacques, I'm really sorry, but your are speaking about P4, and I don't recognize the problem. I've asked for this support earlier (since it something that you'll do by hand otherwise). From your reasoning it sounds like you create caos if you move (integrate/remove) a file in P4. Sorry, but I can't seem to recognize the problem. Care to elaborate about why this works if you do it by hand, but not automagically?
Cheers, /Niclas Jacques Morel wrote: > I agree on the simple, few days VCM open api. It would be so great! > However I disagree on how to handle move and rename refactorings. > Clearcase, Subversion and some others have directory versioning. This > means that when something is moved or renamed IDEA should have a "move" > API entry point. For VCMs like CVS/Perforce? that do not support > directory versioning the move action would default to a remove and an > add like you said. You are just playing on our worse nightmare where to > change the name of a class or worse the name of a package/directory, all > development has to stop to avoid difficult merging problem (you change > the name of a class as somebody changes its content. Without directory > versioning, on merge the second person gets a conflict delete/change and > doesn't know where the class went. With directory versioning the VCM is > like a regular file system: the name of a file is part of its parent > directory. It would know that the merge is on the same file content and > do a regular automatic merge). > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of Vlad Kinik > Sent: Tuesday, March 19, 2002 2:51 PM > To: [EMAIL PROTECTED] > Subject: Re: [Eap-features] Perforce refactoring support > > > +5, but I'd rather ask for generic integration of refactoring and source > > control system. For example if I move a class it would be nice if > refactoring tool called assigned external tool to check out the > original > file, then tool to add the resulting file and finally call to remove the > > original file. If one day we will have Open API I would like to have > similar > listeners there as well. > > >>From: Ga�l Marziou <[EMAIL PROTECTED]> >>Reply-To: [EMAIL PROTECTED] >>To: <[EMAIL PROTECTED]> >>Subject: [Eap-features] Perforce refactoring support >>Date: Sun, 17 Mar 2002 19:37:15 +0100 >> >>The feature we're missing the most is full support of refactoring with >>Perforce. >>Both Perforce and Idea are best tools in their category, it's too bad > > they > >>do not integrate fully. >>We have migrated recently from VSS to Perforce and did not regret our >>choice >>except for Idea insufficient support. >> >>Thanks, >> >>Gael >> >> >>_______________________________________________ >>Eap-features mailing list >>[EMAIL PROTECTED] >>http://www.intellij.com/mailman/listinfo/eap-features > > > > > > _________________________________________________________________ > Join the world?s largest e-mail service with MSN Hotmail. > http://www.hotmail.com > > > _______________________________________________ > Eap-features mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-features > > > _______________________________________________ > Eap-features mailing list > [EMAIL PROTECTED] > http://www.intellij.com/mailman/listinfo/eap-features -- Niclas Olofsson - http://www.ismobile.com Product Development, isMobile, Aurorum 2, S-977 75 Lule�, Sweden Phone: +46(0)920-75550 Mobile: +46(0)70-3726404 _______________________________________________ Eap-features mailing list [EMAIL PROTECTED] http://www.intellij.com/mailman/listinfo/eap-features
