Mailing-List: contact dev-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Received-SPF: pass (nike.apache.org: domain of
 vijayendra.bhamidipati@citrix.com designates 66.165.176.63 as permitted
 sender)
From: Vijayendra Bhamidipati <vijayendra.bhamidipati@citrix.com>
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Subject: RE: deploydb jdbc/mysql connector error?
Thread-Topic: deploydb jdbc/mysql connector error?
Thread-Index: Ac6Mka23TUFPnArHRQ+jn+bKlsvo/gAAygyA
Date: Mon, 29 Jul 2013 19:53:09 +0000
Message-ID: <E7693D06CA988246859053593CE40B8D112F0A@SJCPEX01CL03.citrite.net>
References: <E7693D06CA988246859053593CE40B8D112E83@SJCPEX01CL03.citrite.net>
In-Reply-To: <E7693D06CA988246859053593CE40B8D112E83@SJCPEX01CL03.citrite.net>
Accept-Language: en-US
Content-Language: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

Prachi and I had a look at this, I should have pasted the entire output of =
the deploydb command - in Prachi's env we see that the mysql-connector.jar =
is getting copied over to the deps/ directory, but I see this warning in th=
e beginning when I run deploydb:


[WARNING] Some problems were encountered while building the effective model=
 for org.apache.cloudstack:cloud-api:jar:4.2.0-SNAPSHOT
[WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId=
:type:classifier)' must be unique: mysql:mysql-connector-java:jar -> duplic=
ate declaration of version ${cs.mysql.version} @ org.apache.cloudstack:clou=
dstack:4.2.0-SNAPSHOT, /root/mywork/cloudstack/asf/latest/cloudstack/pom.xm=
l, line 278, column 19
[WARNING]
[WARNING] Some problems were encountered while building the effective model=
 for org.apache.cloudstack:cloudstack:pom:4.2.0-SNAPSHOT
[WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId=
:type:classifier)' must be unique: mysql:mysql-connector-java:jar -> duplic=
ate declaration of version ${cs.mysql.version} @ line 278, column 19
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threa=
ten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support bu=
ilding such malformed projects.
[WARNING]


Any idea why this is happening?


The complete output is pasted below:

[root@vijay-vm1 cloudstack]# mvn -e -P developer -pl developer -Ddeploydb
Listening for transport dt_socket at address: 8787
[INFO] Error stacktraces are turned on.
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model=
 for org.apache.cloudstack:cloud-api:jar:4.2.0-SNAPSHOT
[WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId=
:type:classifier)' must be unique: mysql:mysql-connector-java:jar -> duplic=
ate declaration of version ${cs.mysql.version} @ org.apache.cloudstack:clou=
dstack:4.2.0-SNAPSHOT, /root/mywork/cloudstack/asf/latest/cloudstack/pom.xm=
l, line 278, column 19
[WARNING]
[WARNING] Some problems were encountered while building the effective model=
 for org.apache.cloudstack:cloudstack:pom:4.2.0-SNAPSHOT
[WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId=
:type:classifier)' must be unique: mysql:mysql-connector-java:jar -> duplic=
ate declaration of version ${cs.mysql.version} @ line 278, column 19
[WARNING]
[WARNING] It is highly recommended to fix these problems because they threa=
ten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support bu=
ilding such malformed projects.
[WARNING]
[INFO]
[INFO] --------------------------------------------------------------------=
----
[INFO] Building Apache CloudStack Developer Mode 4.2.0-SNAPSHOT
[INFO] --------------------------------------------------------------------=
----
[INFO]
[INFO] --- properties-maven-plugin:1.0-alpha-2:read-project-properties (def=
ault) @ cloud-developer ---
[INFO]
[INFO] --- maven-remote-resources-plugin:1.3:process (default) @ cloud-deve=
loper ---
[INFO]
[INFO] --- maven-antrun-plugin:1.7:run (default) @ cloud-developer ---
[INFO] Executing tasks

main:
[INFO] Executed tasks
[INFO]
[INFO] >>> exec-maven-plugin:1.2.1:java (create-schema) @ cloud-developer >=
>>
[INFO]
[INFO] <<< exec-maven-plugin:1.2.1:java (create-schema) @ cloud-developer <=
<<
[INFO]
[INFO] --- exec-maven-plugin:1.2.1:java (create-schema) @ cloud-developer -=
--
log4j:WARN No appenders could be found for logger (org.springframework.core=
.env.StandardEnvironment).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for mo=
re info.
=3D=3D=3D=3D=3D=3D=3D=3D> WARNING: Provided file does not exist: /root/mywo=
rk/cloudstack/asf/latest/cloudstack/developer/developer-prefill.sql.overrid=
e
=3D=3D=3D=3D=3D=3D=3D=3D> Initializing database=3Dcloud with host=3Dlocalho=
st port=3D3306 username=3Dcloud password=3Dcloud
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D> Running query: drop database if exist=
s `cloud`
SQL exception in trying initDB: java.sql.SQLException: No suitable driver f=
ound for jdbc:mysql://localhost:3306/
[root@vijay-vm1 cloudstack]#


Regards,
Vijay


-----Original Message-----
From: Vijayendra Bhamidipati [mailto:vijayendra.bhamidipati@citrix.com]=20
Sent: Monday, July 29, 2013 12:32 PM
To: dev@cloudstack.apache.org
Subject: deploydb jdbc/mysql connector error?

After rebasing my code against the latest master/4.2, I'm running into this=
 error when doing a " mvn -e -P developer -pl developer -Ddeploydb " across=
 master and 4.2 :

=3D=3D=3D=3D=3D=3D=3D=3D> WARNING: Provided file does not exist: /root/mywo=
rk/cloudstack/asf/latest/cloudstack/developer/developer-prefill.sql.overrid=
e
=3D=3D=3D=3D=3D=3D=3D=3D> Initializing database=3Dcloud with host=3Dlocalho=
st port=3D3306 username=3Dcloud password=3Dcloud =3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D> Running query: drop database if exists `cloud` SQL exception =
in trying initDB: java.sql.SQLException: No suitable driver found for jdbc:=
mysql://localhost:3306/
[root@vijay-vm1 cloudstack]#


Is anyone else also seeing this? If not, has anyone seen this and can sugge=
st a resolution??

I tried the operation on a clean new workspace and still see this error. I =
don't think it has anything to do with any recent checkin - something must'=
ve changed in my setup, but again I didn't do anything out of the ordinary.

Thanks!
Regards,
Vijay