mirror of https://github.com/apache/archiva.git
[MRM-1373] Archiva fails when default charset in database is UTF 8
submitted by Gwen Harold Autencio o added documentation for the workaround, which is to set the character encoding to UTF-8 after the database has been created git-svn-id: https://svn.apache.org/repos/asf/archiva/branches/archiva-1.3.x@953209 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
parent
f4626ad8a5
commit
4e63f6923a
|
@ -32,6 +32,9 @@ Apache Archiva Databases
|
||||||
By default the archiva and users databases are stored in the <<<databases>>> directory where Archiva is installed. To change the
|
By default the archiva and users databases are stored in the <<<databases>>> directory where Archiva is installed. To change the
|
||||||
path, just edit all instances of the "DatabaseName" property in <<<conf/jetty.xml>>> (see below).
|
path, just edit all instances of the "DatabaseName" property in <<<conf/jetty.xml>>> (see below).
|
||||||
|
|
||||||
|
<<Note:>> If you are using MySQL as your database, Archiva fails when the users database created is initially set to UTF-8 for the character encoding.
|
||||||
|
As a workaround, set the database to UTF-8 encoding after it has been populated. See {{{http://jira.codehaus.org/browse/MRM-1373} MRM-1373}} for more details.
|
||||||
|
|
||||||
+------+
|
+------+
|
||||||
...
|
...
|
||||||
<New id="archiva" class="org.mortbay.jetty.plus.naming.Resource">
|
<New id="archiva" class="org.mortbay.jetty.plus.naming.Resource">
|
||||||
|
|
Loading…
Reference in New Issue