[
https://issues.apache.org/jira/browse/CLOUDSTACK-6157?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Kinsella resolved CLOUDSTACK-6157.
---------------------------------------
Resolution: Fixed
Hugo fixed this in the following commits on master:
e883877c7a6f9df04b572afd4ee5f10d265bcc3a
afc188cb5c72e316975799c95529e8692ddcb94b
> devcloud setup db functionality broken by mysql dependency cleanup
> ------------------------------------------------------------------
>
> Key: CLOUDSTACK-6157
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6157
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: DevCloud
> Reporter: John Kinsella
> Priority: Blocker
> Fix For: 4.3.0
>
>
> With the removal of mysql compile-time dependencies, maven is no longer able
> to manipulate the devcloud database without developer supplying the mysql
> JDBC connector and configuring classpath appropriately.
> Need to either update documentation, or come up with a legally acceptable
> technical solution.
> Expected result:
> Successfully deployed devcloud db
> Actual result:
> mvn -P developer -pl developer,tools/devcloud -Ddeploydb
> ...
> ============> Running query: drop database if exists `cloud`
> SQL exception in trying initDB: java.sql.SQLException: No suitable driver
> found for jdbc:mysql://localhost:3306/
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
