Remove tagbase usage and use insted mecanism use in update command

what's the mechanism used in the update command? What changes are necessary for the release mojo to support this new approach?

After a discussion with David, we won't remove tagbase. We'll use it if it's specified but by default, we'll consider that user use a standard repository layout (trunk/, tags/, branches)

If user use a standard layout, tags directory is automatically discover.
And the other feature added in update command is the support of standard svn revision specifiers (HEAD, BASE, COMMITTED, PREV) and revision number

The last feature is if tag != null or it isn't a revision number, we use the svn switch command instead of update

Added automatic tag resolution to SvnCheckoutCommand, SvnChangeLogCommand, and SvnTagCommand.

On the SvnChangeLogCommand command, I changed the date format specified in the command line.
The original format looked like: svn log -v -r "

:

"
But this format was not legal in svn version 1.2.3 on cygwin, linux, or windows. I am not sure if a previous version supported this date format, but the current does not.
The new date format looks like: svn log -v -r "

:

"
It is now specifying the time along with the date. The api allows a user to pass a date, so we should probably use the time in the date as well.
I also changed ScmTestCase.getDate() to support passing time values so I could test the changelog command creation.

As far as SvnDiffCommand goes, I didn't add branch/tag resolution to it because the api specifies a "startRevision" and "endRevision". While it might be useful to be able to support tag/branch diffs, the api only specifies revisions. This is something that can always be added at a later date if deemed necessary.

It also seems odd to me that the StatusMojo doesn't actually print anything out. It has a StatusScmResult with a list of changed files, but only checks that the result was successful. Maybe I don't understand the intended use of the action, but it basically throws away the result without ever doing anything with it.

Applied, thanks.

For your two point on status mojo and diff command, you can file an issue for each