Quinn, forget :)
Thankx for your answer.
--
The Future Begins Today
Em 21/04/2009, às 12:18, Quinn Taylor escreveu:
>
> On Apr 20, 2009, at 4:55 PM, CodeWarrior wrote:
>
>>>> What we are doing now:
>>>>
>>>> 1 - Suppose that exist normal.java in a svn
>>>> 2 - you check out it using Versions and create a new Java project
>>>> to
>>>> work on it (Close the Versions)
>>>> 3 - You discover that normal.java need to be normal1.java
>>>> 4 - Open the Versions, go to the svn and rename (manually).
>>>> 5 - Go to the trunk that was checked out and update
>>>> 6 - normal.java is now normal1.java
>>>> 7 - Inside the eclipse refresh the project, now, normal.java is
>>>> normal1.java
>>>> 8 - open normal1.java and correct the type name
>>>> 9 - everything is not alright
>>>>
>>>> Now, i just need to know if Versions do the same of Subeclipse, i
>>>> need
>>>> a smart svn tool that reduce clicks and accelerate the job of my
>>>> team.
>>>
>>> This is where you've lost me. In step 4, I assume you're right-
>>> clicking on the file in Versions and selecting "Rename", then
>>> typing the new name. Yes, Versions does this correctly. If you're
>>> renaming the file in the working copy (which is recommended, so
>>> the developer can resolve any build errors before committing) and
>>> you run svn status (in Terminal) at this point, you'll see the
>>> following:
>>
>>
>> The problem in Versions is not a software problem like a Bug, but
>> that i need to do much think more than just use the Subeclipse,
>> that i just rename inside the Eclipse and the SubEclipse plug-in do
>> the remove normal.java and add the new file (normal1.java). Do u
>> understand now? More work. I just want rename a file inside a
>> eclipse and when open the Versions they automactic remove
>> normal.java and add normal1.java How can Version do it, i don't
>> know. What i'm say? That this is a very good feature that speed up
>> our work, just it, not a Bug report or a Version software problem.
>
> You've still lost me. From what you've described in the thread, if
> people have Subclipse or Subversive installed, renaming inside
> Eclipse should work. With Eclipse by itself (no SVN plugins) it
> probably won't. This is totally normal behavior, not a bug in
> Subversion, Versions, or Eclipse. When you manipulate Subversion
> working copies, somehow you have to tell Subversion that you're
> making changes, it can't (and shouldn't) just guess what changes
> were made. It can be very tricky to tell if a file was moved to a
> different directory, renamed, or just deleted and a very similar
> file was added.
>
> With no offense intended, if your developers do the right thing,
> everything will just work. If they want to rename resources that are
> in Subversion from within Eclipse, they must install a Subversion
> plugin. (Why Eclipse comes with a CVS plugin by default, but not one
> for SVN yet is beyond me. It would make life easier for a lot of
> people.) In my experience, when you have the proper plugin installed
> and rename in Eclipse, there aren't any problems. I'm not sure
> exactly what symptom you're seeing in step 9 ("everything is not
> alright") back in Eclipse, but it sounds like renaming in Eclipse
> avoids the problem.
>
> If your developers are using Versions (which they had to download,
> install, and configure), what's keeping them from taking 5 minutes
> to install Subclipse/Subversive? If that solves the problems you're
> having, it seems like a no-brainer. I think this is the "feature"
> you're looking for to speed up your work. :-)
>
> - Quinn
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Versions" group.
To post to this group, send email to versions@googlegroups.com
To unsubscribe from this group, send email to
versions+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/versions?hl=en
-~----------~----~----~----~------~----~------~--~---
