VMware Cloud Community
vdebaere
Contributor
Contributor
Jump to solution

Trunk build issue (db-upgrade.xml:28 Schema version not found)

Hi

I would like to start exploring the code in the trunk, especially because I would like to try out some ideas (eg: automatic groups based upon resource type & pattern matching in the resource name) which could relate to the database. Since 3.0 changes the access to the db to hibernate, I'd like to base my tries on trunk.

when I do an ant dbsetup, I get the following error:

installer/data/db-upgrade.xml:28: Schema version not found!

I specified in my build.properties:
hq.schema.target.version=LATEST but that didn't make any difference. Can anybody point me in the "good direction"?

Thanks in advance!
0 Kudos
1 Solution

Accepted Solutions
jtravis_hyperic
Hot Shot
Hot Shot
Jump to solution

Hey Vincent,

Update your tree and try again. The build.properties file needed
the JDBC version to be explicitly set to 2.

-- Jon


On Oct 19, 2006, at 6:07 AM, Vincent De Baere wrote:

> Hi
>
> I would like to start exploring the code in the trunk, especially
> because I would like to try out some ideas (eg: automatic groups
> based upon resource type & pattern matching in the resource name)
> which could relate to the database. Since 3.0 changes the access to
> the db to hibernate, I'd like to base my tries on trunk.
>
> when I do an ant dbsetup, I get the following error:
>
> installer/data/db-upgrade.xml:28: Schema version not found!
>
> I specified in my build.properties:
> hq.schema.target.version=LATEST but that didn't make any
> difference. Can anybody point me in the "good direction"?
>
> Thanks in advance!


View solution in original post

0 Kudos
7 Replies
admin
Immortal
Immortal
Jump to solution

Hi Vincent:

Thank u for trying to build HQ from the trunk.

can u provide the following info for us so that we can review our build
process.

1. The version of ant on your system where the build is failing
2. jdk version
3. OS and version

Thanx.


Vincent De Baere wrote:
> Hi
>
> I would like to start exploring the code in the trunk, especially because I would like to try out some ideas (eg: automatic groups based upon resource type & pattern matching in the resource name) which could relate to the database. Since 3.0 changes the access to the db to hibernate, I'd like to base my tries on trunk.
>
> when I do an ant dbsetup, I get the following error:
>
> installer/data/db-upgrade.xml:28: Schema version not found!
>
> I specified in my build.properties:
> hq.schema.target.version=LATEST but that didn't make any difference. Can anybody point me in the "good direction"?
>
> Thanks in advance!
>

0 Kudos
vdebaere
Contributor
Contributor
Jump to solution

Hi

I'm building on a Gentoo Linux (testing), using ant 1.6.5 and JDK 1.5.0_08. Hope this helps...
0 Kudos
admin
Immortal
Immortal
Jump to solution

ok,

can u try with jdk 1.4?


Vincent De Baere wrote:
> Hi
>
> I'm building on a Gentoo Linux (testing), using ant 1.6.5 and JDK 1.5.0_08. Hope this helps...
>

0 Kudos
jtravis_hyperic
Hot Shot
Hot Shot
Jump to solution

Hey Vincent,

Update your tree and try again. The build.properties file needed
the JDBC version to be explicitly set to 2.

-- Jon


On Oct 19, 2006, at 6:07 AM, Vincent De Baere wrote:

> Hi
>
> I would like to start exploring the code in the trunk, especially
> because I would like to try out some ideas (eg: automatic groups
> based upon resource type & pattern matching in the resource name)
> which could relate to the database. Since 3.0 changes the access to
> the db to hibernate, I'd like to base my tries on trunk.
>
> when I do an ant dbsetup, I get the following error:
>
> installer/data/db-upgrade.xml:28: Schema version not found!
>
> I specified in my build.properties:
> hq.schema.target.version=LATEST but that didn't make any
> difference. Can anybody point me in the "good direction"?
>
> Thanks in advance!


0 Kudos
admin
Immortal
Immortal
Jump to solution

Of course, HEAD is in massive flux right now as we migrate to
Hibernate. So expect most things to be broken at the moment. Can't
make an omelet without breaking some eggs :-).

Charles


0 Kudos
vdebaere
Contributor
Contributor
Jump to solution

Thanks for the help...

Just in case someone else with the same problem is reading this: make sure you update your ~/.hq/build.properties as well 🙂

BTW: works OK with both JDK 1.4.X && 1.5.X

Message was edited by: vdebaere
0 Kudos
admin
Immortal
Immortal
Jump to solution

Yes, that's right. Any properties defined ~/.hq/build.properties
will trump the ones in etc/build.properties. Thanks, Vincent.

Charles


0 Kudos