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

Re: [Subclipse-users] What is Tags column on Resource History used for?

From: Mark Phippard <markp_at_softlanding.com>
Date: 2006-03-15 21:00:10 CET

Eugene Kuleshov <eu@md.pp.ru> wrote on 03/15/2006 02:46:24 PM:

> > No, you are already wrong. If you are working locally, and the item
> > selected contains this property, then AFTER the branch/tag is made,
> > local property is updated. It would then still need to be committed.
> Does that described in documentation? I don't think there are many
> users yet that can read your mind. :-)

I think it is. This is what the docs say:

Updating the Property

In addition to the Configures Branches and Tags option that was discussed
earlier, there is also support for automatically updating the
subclipse:tags property when you create a Branch/Tag using Subclipse. When
you take this option, if we detect the subclipse:tags property on the item
you selected, then we pop-up a dialog that lets you confirm that you want
to add this new information to the subclipse:tags property. You then just
have to commit that property change after creating the Branch/Tag. This
feature does not exist when creating the Branch/Tag from the repository
browser as it is only possible to modify a property value in a working

> The thing is that this property would go into the next tag "based on
> rules of a Subvesion copy", but not into the tag it is describing. Don't
> find that confusing?

Honestly, I don't. This feature exists for one main reason, so that when
browsing the history for an item we can decorate it with tags. Why would
the tag itself need informatiom about itself? That would already show in
the history of the tag. However, when creating a branch having this old
information flow into the branch is very handy. When browsing the history
of a branch as it traces back into its source you can still see the

I guess that is why we need the community to help more on things like

> What constraints you are talking about? How hard it to write few
lines of code like:

Constraints such as that Subversion does not allow you to set a property
directly in the repository. It has to be set on a working copy and then
committed. Constraints such as that Subversion does not let you perform
"atomic" operations on "disjointed" working copies. In the typical
Eclipse workspace, each checked out project is its own working copy
island. You cannot create one tag from all of these islands.

> 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
> 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.

I am going to start a new thread to respond to this one. It seems useful
and I do not want it lost in this other discussion.


Scanned for SoftLanding Systems, Inc. and SoftLanding Europe Plc by IBM Email Security Management Services powered by MessageLabs.

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:00:33 2006

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.