To give a little background, I have a svn repository shared by several projects.
I remember the advise listed in this post.
http://unfuddle.com/blog/2007/7/26/powerful-subversion-commit-messages

I’ve noticed that putting the # sign and ticket number in the commit no longer links the ticket and revision like it used to. I’m guessing I need to specify which project the ticket is in. Is there syntax to accomplish this via the command line?

I suppose I should also ask about projects that have multiple repositories. Is there new syntax for specifying which repository to use when making a comment using square brackets [] and a revision number.

Java,

Thanks for your message.

Currently, if you associate a repository with multiple projects, there is no syntactic way to disambiguate the project to which the commit message actions apply. As such, we simply disable powerful commit messages for repositories with multiple projects.

We may eventually develop a more robust syntax, but for now, having multiple projects associated with a single repository simply means that the powerful commit messages will simply not work.

Thanks Josh.

Hi Josh,
I see the latest post on this topic is a year or so old. Any chance you have developed the more robust syntax you spoke of? We are sharing a single repos among several projects, and running into an issue with the powerful commit messages updating the wrong tickets. I’d like to avoid reorg-ing the projects into milestones, but my developers really like the easy of updating tickets with the power commits.

Thanks,
-tom

Tom,

No, this syntax has not yet been added to the powerful commit messages. Still on the todo list, just lower in priority than a number of other things.