[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Improving the Branch/Tag Process

From: Eugene Kuleshov <eu_at_md.pp.ru>
Date: 2006-03-15 21:21:09 CET

Mark Phippard wrote:

>> 1) check that all selected elements are projects (done in plugin.xml)
>> 2) select same target folder for all of them
>> 3) for each selected project:
>> -- update tag property file for each of them (considering above
> comment
>> about revisions)
>> -- commit tag property
>> -- create copy of project in selected target folder
>>
>> It is an IDE and the main purpose of IDE is to make common operations
>> simple. Otherwise I can go to command line and run script that will do
> all of that.
>
> Let me rephrase this to see if I understand:
>
> 1) Select more than one project in say the Navigator view or Package
> Explorer --- Eclipse view. I think we can do this conditioning right in
> the option contribution to the menu.
>
> 2) Find common parent URL of selections. If none exists probably issue
> an error message.

   I don't think you need parent here. Copy is created for selected
projects and not for their parents.

> I am going to change your script at this point to reflect what I would
> actually consider doing.
>
> 3) Bring up Create tag dialog based on this common parent URL.

   However here we are choosing parent target folder where all copies
will be created.

> 4) If tag is created, for each of the selected projects update the
> subclipse:tags property if it is present.
>
> I will not even consider doing any "commits" as part of this process, so I
> left that out. User would have to commit any subclipse:tags property
> changes after the tag is created.

   And why exactly you won't even consider that? If tag property won't
have revision information it would be quite reasonable to commit it
before hand if user choose to tag with head revision.

> Setting aside the parts we disagree on, would you say that this is what
> you are suggesting? Essentially creating a tag based on the common parent
> of the selections?

   Not really. I wasn't suggesting parent, especially because such
parent may have more stuff then user actually want to tag. Unless I am
missing something.

   I also think it is important that one way or the other tag property
will go into the copy. Because the only way to make it go to the target
copy is to actually commit it, it need to be committed automatically.

   regards,
   Eugene

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Wed Mar 15 21:21:36 2006

This is an archived mail posted to the Subclipse Users mailing list.