The build really took soma time, but the problem isn't that, but the result:

[INFO] Creating ../../../../dev-container/rhq-server/bin/rhq-storage.properties
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] 
[INFO] RHQ Enterprise Server Application Server Container  FAILURE [43.065s]
[INFO] RHQ Server JAR Integration Tests .................. SKIPPED
[INFO] RHQ Code Coverage ................................. SKIPPED
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 49.295s
[INFO] Finished at: Fri Nov 08 13:47:07 CET 2013
[INFO] Final Memory: 66M/247M
[INFO] ------------------------------------------------------------------------
[WARNING] The requested profile "enterprise" could not be activated because it does not exist.
[ERROR] Failed to execute goal org.codehaus.gmaven:groovy-maven-plugin:2.0-SNAPSHOT:execute (storage-setup) on project rhq-enterprise-server-appserver: Execution storage-setup of goal org.codehaus.gmaven:groovy-maven-plugin:2.0-SNAPSHOT:execute failed: java.io.FileNotFoundException: ../../../../dev-container/rhq-server/bin/rhq-storage.properties (No such file or directory) -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.codehaus.gmaven:groovy-maven-plugin:2.0-SNAPSHOT:execute (storage-setup) on project rhq-enterprise-server-appserver: Execution storage-setup of goal org.codehaus.gmaven:groovy-maven-plugin:2.0-SNAPSHOT:execute failed: java.io.FileNotFoundException: ../../../../dev-container/rhq-server/bin/rhq-storage.properties (No such file or directory)


While:
root@rhq-test:~/projects/rhq# ls -l dev-container/rhq-server/bin/rhq-storage.properties
-rw-r--r-- 1 root root 5429 Nov  8 13:47 dev-container/rhq-server/bin/rhq-storage.properties

Attila



2013/11/8 Thomas Segismont <tsegismo@redhat.com>
Le 08/11/2013 09:55, Attila Heidrich a écrit :

The problem is not caused by pg 9.2, but rhq 4.9.

It could be something we rely on which has changed between 9.1 and 9.2. It's unlikely but possible. If you can dump your data and re-import it in a 9.1 server you'll know tomorrow if Postgres version has something to do with your problem.


Is it possible to downgrade RHQ with the same database content? I try to

No, it isn't.


build a new version, but if I fail to finish today, it seems easier to
downgrade, but I do not really want to loose sll the measurements
collected until now.


Everything you need to know to build RHQ is in the wiki:
https://docs.jboss.org/author/display/RHQ/Building+RHQ

If anything is missing, feel free to ask, here or in #rhq@freenode


Attila



_______________________________________________
rhq-users mailing list
rhq-users@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-users


Cheers

_______________________________________________
rhq-users mailing list
rhq-users@lists.fedorahosted.org
https://lists.fedorahosted.org/mailman/listinfo/rhq-users