cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Vijayendra Bhamidipati <>
Subject RE: can't deploydb on 4.1 branch, why don't you face it?
Date Sat, 09 Feb 2013 00:21:24 GMT
Hi Frank,

This issue is being tracked in . The
workaround is to comment out the code in that checks whether the
file contains a parameter for encryption. It needs to be fixed - everyone deploying a fresh
db will face the issue as of now. I haven't had the time to look into it yet but will do so
at the first opportunity unless someone fixes it before that.


-----Original Message-----
From: Frank Zhang [] 
Sent: Friday, February 08, 2013 3:52 PM
Subject: can't deploydb on 4.1 branch, why don't you face it?

'mvn -P developer -pl developer -Ddeploydb' greets me below error:

[INFO] --- exec-maven-plugin:1.2.1:java (create-schema) @ cloud-developer --- ========>
WARNING: Provided file does not exist: /home/frank/dev/incubator-cloudstack/utils/conf/
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(
        at java.lang.reflect.Method.invoke(
        at org.codehaus.mojo.exec.ExecJavaMojo$
Caused by: java.lang.ExceptionInInitializerError
        ... 6 more
Caused by: File not found
        ... 7 more
Caused by: file:/home/frank/.m2/repository/org/apache/cloudstack/cloud-utils/4.1.0-SNAPSHOT/cloud-utils-4.1.0-SNAPSHOT-tests.jar!/
(No such file or directory)
        at Method)

after looking into it, I think it's a bug that everyone would encounter, but to my surprise
it seems as if only I suffer it.

The cause is in

    public void check() {
        //Get encryption type from
        final File dbPropsFile = PropertiesUtil.findConfigFile("");
        final Properties dbProps = new Properties();

        ... .... 

PropertiesUtil.findConfigFile will search file in classpath first, and unfortunately cloud-utils-4.1.0-SNAPSHOT-tests.jar
does have packaged in it, then it's returned as the first match. 
As it's a file in JAR it can not be opened as ordinary file that why the exception happens.

I don't know why we have utils/conf/,  can anyone tell me its purpose? And does
anyone else encountered this bug?

View raw message