Bump version

oops ...

I was a bit too trigger-happy with the search/replace in commit
250c079

WebSVN: add 'sc' option to base_url() function ...

The 'sc' (show change) option is obsolete since WebSVN 2.1.0 (r621)
we keep it for Compatibility with oder releases. Refer to discussion on
Github [1].

[1] https://github.com/dregad/source-integration/pull/1#commitcomment-2711137

WebSVN: minor adjustments (coding guidelines, whitespace)

SourceWebSVN plugin: Allow viewing removed files

Plugin SourceWebSVN : fix wrong comparison of SourceChangeset action field ...

Possible values of this field are:
'add' for file added
'rm' for file remove
'mod' for file modified
'mv' for move

Plugin SourceWebSVN : fix typo

WebSVN plugin : Fix wrong method call

Plugin SourceWebSvn : fix 'compare' parameter (has now format 'path'@'rev')

SourceWebSvn plugin : fix typo

SourceWebSVN plugin : Remove 'sc' parameters from generated links (obsolete)

Remove if / else in url_changeset (The 'comp' operator works for both multiview and non-multiview mode)

WebSVN: refactoring using http_build_query

WebSVN: differentiated URLs depending on multiviews option ...

The plugin is now able to handle both types of WebSVN URLs:

- standard URLs, e.g.
  http://example.com/listing.php?repname=MyRepo&path=%2Ftrunk%2F&rev=10&sc=1
- multiview URLs (introduced with 577ff7e) like
  http://example.com/MyRepo/trunk?&rev=10

This commit restores the WebSVN functionality for sites not using the
multiviews functionality (i.e. as thigs were prior to commit
577ff7e).

Fixes #46

WebSVN: added helper methods to retrieve repo info ...

get_websvn_url, get_websvn_name, get_websvn_path

WebSVN: add is_multiviews method

WebSVN : Add option to handle "Multiview" mode ...

WebSVN can be configured to use Apache Multiview link format [1]. This
commit allows users to specify if this option is enabled or not in the
settings page of their WebSVN repositories.

Note that theses changes only make the option visible in the WebSVN
repos config, but does not alter the plugin's behavior. The next step
is to check the value of this option so the plugin can format WebSVN
links as appropriate.

[1] http://httpd.apache.org/docs/current/content-negotiation.html#multiviews

Fixes #46, #47

Original code was modified to use check_checked() function and fix
whitespace, commmit message reworded.

Signed-off-by: Damien Regad <damien.regad@merckgroup.com>

Bumping version numbers ...

Core framework version -> 0.18
Github -> 0.17
Gitweb -> 0.17
WebSVN -> 0.17

Add ChangeSet viewer support

Change WebSVN urls

Support viewing files and diff from deleted branch ...

When trying to see files or view diff between files from a branch that has
been marked as deleted (like a reintegrated feature branch), websvn
displayed an error saying that file does not exist at that specific
revision, even though it actually does. Adding peg=<rev> fixes this.

Reference: ticket http://leetcode.net/mantis/view.php?id=237

Fixes #6

Signed-off-by: Damien Regad <damien.regad@merckgroup.com>

Updated contact url

Updated contact email

Update copyrights

Separate remote import page from user imports ...

Due to complexities of trying to have both user-initiated imports and
remote imports handled in the same page, the import process has been
split into two separate use cases.  pages/import.php is now specifically
for use by the remote import process, while pages/repo_import_latest.php
remains for usage by authenticated MantisBT users.

This will require that all cronjobs or post-commit hooks that triggered
a remote import be updated to point to the new import url.  Framework
version has been bumped accordingly.

Require base SVN plugin for SFSVN/WebSVN ...

Due to the fact that both plugins need to ensure that the base SourceSVN
plugin class is available, and to make sure the base configuration
options are registered, the SourceSVN plugin needs to be installed.

Re-licensed the project under the MIT license

Fix #97: Refacter core SVN into shared codebase ...

Created base SVN plugin with the shared SVN code from WebSVN and SFSVN
plugins, and then modified the previous plugins to inherit from the new
base plugin.  This will end the previous need to constantly replicate
changes between the two SVN plugins.

Currently, the only way to modify shared SVN configuration is to have
the base SVN plugin installed, but this is a task for a different
commit.

Fix #92: Unable to set SVN path on Windows ...

Refactored SVN binary/path validation into a separate function, and use
the new validation routines from the existing API and page code.

Update copyrights for 2010