You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@roller.apache.org by "Glen Mazza (JIRA)" <ji...@apache.org> on 2013/01/06 02:08:12 UTC

[jira] [Closed] (ROL-1564) Roller 3.1 to 4.0 oracle db scripts partitialy failed

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

Glen Mazza closed ROL-1564.
---------------------------

    Resolution: Unresolved

Sorry we could not get to this in time, and neither 3.1 nor 4.0 are supported.  Please upgrade to Roller 5.0.
                
> Roller 3.1 to 4.0 oracle db scripts partitialy failed
> -----------------------------------------------------
>
>                 Key: ROL-1564
>                 URL: https://issues.apache.org/jira/browse/ROL-1564
>             Project: Roller
>          Issue Type: Bug
>          Components: Installation
>    Affects Versions: 4.0
>         Environment: Tomcat 5.5, Windows XP, Roller 4.0, Oracle 10g
>            Reporter: Boris
>            Assignee: Roller Unassigned
>         Attachments: ASF.LICENSE.NOT.GRANTED--310-to-400-migration.sql
>
>
> Apache Roller 4.0 createdb.sql for oracle partitialy failed.
> Lines with errors are commented as following:
> -- error ..
> Boris
> ps.:  Are there any Junit test to test db scripts?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira