Mark Phippard wrote:
>>I had to tag several projects in Eclipse and tried to just select
>>them in a package explorer, but apparently there are no tag menu
>>available for multiple selected projects (imho this is a huge regression
>>comparing to cvs plugin).
>>
>>
>I do not think you are being fair (to Subclipse) hear. This stuff comes up
>on the Subversion users@ list on a daily basis. There are a lot of people
>that do not like how Subversion does tagging. Even using the command line,
>which is the ultimate in flexibility, people cannot easily get the results
>they want.
>
Don't get me wrong. I actually like how tagging is working. I just
wish that we'd have more convenience in the IDE.
>What can we realistically do?
>
Make it more convenient for the IDE user for example. :-)
>I think our support for the feature is consistent with the design of the feature in Subversion. Unless they make significant changes I do not see any solutions. If you want to propose something realistic, that at least acknowledges what we have to
>work with, I am willing to listen.
>
>
I don't know why are you using this excuse all the time. It is always
possible to make things easier to use... For example, on windows copy
command can be used like "copy * /some/target/folder . So, since tagging
is just a copy to the target directory you can verify if all selected
projects are mapped from the same parent and then ask for the target
folder, then use project's folder names to complete the target path. Is
it difficult to implement?
>>created in the repository (nothing reported on SVN console either). So,
>>I had to go into repository view and tag project from there.
>>
>>
>The fact that nothing shows in the Console tells me there must have been a
>NPE or something. Did you check the error logs?
>
>
Unfortunately this idea didn't crossed my mind and now all logs are gone.
>Be aware that Subversion implements tags by doing a "copy" in the virtual
>file system. The semantics of the copy behave identically to the Unix cp
>command. I point this out because the behavior changes based on whether
>the target of the copy already exists or not. With Subversion, you
>generally want the target to not exist so that the copy operation creates
>it. If not, then the copy usually succeeds, but not in a manner that you
>were expecting.
>
>
Right. It would be very useful to see a warning if local copy does not
match the remote copy.
>>may happend? My guess that I may'd have local project copy not updated
>>up to last revision at the project root level.
>>
>>
>Copies will not fail for this. In most cases, you are doing the copy
>purely within the repository. If you do perform the copy based on your WC,
>Subversion will do a mixed-revision copy if necessary. Personally, I would
>not do a copy from the WC, unless you first did an update at the root level
>so that all items are at the same revision.
>
That makes sense. So, can I just use Repositories view to create
folder /trunk/someTag and then copy/paste projects from /trunk/* to that
new folder ?
regards,
Eugene
Received on Sat Jan 21 22:07:04 2006