> I'll see if recommitting the property fixes things. I've added the svn:tags property to the core projects, but there seems to be some weirdness with updates that consist solely of top level directory properties not propogating correctly, so you may need to wait for another commit in the effected projects to see the update.
For anyone who needs to do this for other projects (like the plugins), what I did in Eclipse was: 1. Create a correctly formed subclipse:tags property using Team->Configure Branches/Tags to add the various branches and tags (some of them in the release directory, not the tags directory). 2. Use Team->Show Properties, then Modify Property to copy the correctly formatted value 3. Use Team->Set Property for each of the other projects to add the subclipse:tags property and paste the correct value I didn't copy all tags, but rather just the terminal tags of each release cycle (ie VERSION_0_18_1, but not _0_18 or any of the _0_17_* tags). Note that any projects which are split off in their own repository (e.g. plugin modules) have independent revision numbers, so you'll need to using Configure Branches/Tags for them rather than just copying the value from the core projects. Tom --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
