You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openmeetings.apache.org by "Maxim Solodovnik (JIRA)" <ji...@apache.org> on 2013/11/16 15:53:21 UTC

[jira] [Resolved] (OPENMEETINGS-835) no proper db-type option for postgresql db (Command Line Admin)

     [ https://issues.apache.org/jira/browse/OPENMEETINGS-835?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Maxim Solodovnik resolved OPENMEETINGS-835.
-------------------------------------------

       Resolution: Fixed
    Fix Version/s: 2.2.0 Apache Release
                   3.0.0 Apache Release

Committed revision 1542517.

Thanks for the detailed report

> no proper db-type option for postgresql db (Command Line Admin)
> ---------------------------------------------------------------
>
>                 Key: OPENMEETINGS-835
>                 URL: https://issues.apache.org/jira/browse/OPENMEETINGS-835
>             Project: Openmeetings
>          Issue Type: Bug
>          Components: Import/Export
>    Affects Versions: 2.2.0 Apache Release
>            Reporter: Peter Dähn
>            Assignee: Maxim Solodovnik
>            Priority: Minor
>             Fix For: 3.0.0 Apache Release, 2.2.0 Apache Release
>
>
> db-type enum in src/org/apache/openmeetings/cli/ConnectionProperties.java   ("postgersql") doesn't fit to call of persistence.xml in src/org/apache/openmeetings/cli/Admin.java  (line 250)
> I needed to change enum entry in ConnectionProperties.java (line 27) and case entry in ConnectionPropertiesPatcher.java (line 58) to "postgres"
> Probably it is enough to change "postgres_persistence.xml" to "postgresql_persistence.xml" in red5/webapps/openmeetings/WEB-INF/classes/META-INF/



--
This message was sent by Atlassian JIRA
(v6.1#6144)