[Registry-dev] [jira] Updated: (REGISTRY-289) modules/core/target/classes/database-scripts/mysql-registry.sql file is empty (mvn install executed against r16629 checkout)

[Krishantha Samaraweera (JIRA)]

     [ https://wso2.org/jira/browse/REGISTRY-289?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Krishantha Samaraweera updated REGISTRY-289:
--------------------------------------------

    Priority: Blocker  (was: Minor)

same .sql file is empty in registry 1.1 RC1 also. And hsql script file refers to older database design. Please do the required updates to sql script files. If not better to remove those files from db-scripts directory.

Issue state will be update to blocker since we are closer to next release. 

> modules/core/target/classes/database-scripts/mysql-registry.sql file is empty (mvn install executed against r16629 checkout)
> ----------------------------------------------------------------------------------------------------------------------------
>
>                 Key: REGISTRY-289
>                 URL: https://wso2.org/jira/browse/REGISTRY-289
>             Project: WSO2 Registry
>          Issue Type: Bug
>          Components: core
>    Affects Versions: SNAPSHOT
>         Environment: Windows XP, Eclipse 3.3.2, Maven 2.0.7
>            Reporter: Kelvin Meeks
>            Assignee: Chathura Ekanayake
>            Priority: Blocker
>
> I did a checkout of the latest revision from the Subversion repository (r16629) - and executed a "mvn install"
> It appeared that the bulid and all tests executed ok, however, it appears that the mysql-registry.sql file is empty - the other database files (derby-complete.sql, derby-registry.sql, hsql-registry.sql) appear to have been correctly generated.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira