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 darren.s.shepherd@gmail.com
 designates 209.85.160.45 as permitted sender)
Message-ID: <5230A145.7080204@gmail.com>
Date: Wed, 11 Sep 2013 09:58:45 -0700
From: Darren Shepherd <darren.s.shepherd@gmail.com>
User-Agent: Mozilla/5.0 (X11; Linux x86_64;
 rv:17.0) Gecko/20130803 Thunderbird/17.0.8
MIME-Version: 1.0
To: "dev@cloudstack.apache.org" <dev@cloudstack.apache.org>
Subject: DatabaseUpgradeChecker and running from eclipse
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

So I run ACS from eclipse for development, but DatabaseUpgradeChecker 
does the following

String currentVersion = 
this.getClass().getPackage().getImplementationVersion();
                 if (currentVersion == null) {
                     currentVersion = 
this.getClass().getSuperclass().getPackage().getImplementationVersion();
                 }

Which results in currentVersion = "1.6.0_45" which is the package 
version of java because the super class is java.lang.Object.  So upgrade 
fails.  So I always comment out the DatabaseUpgradeChecker.  Changing 
the super class to ManagerBase also works around the problem sorta 
(currentVersion == null, so it just does nothing).

What are others doing?  In general I want to get rid of any use of 
getImplementationVersion() as it makes development annoying.

Darren