Notes |
|
(0026750)
|
hgbot
|
2010-04-28 11:41
|
|
Repository: erp/devel/pi
Changeset: 20b5be2ffe26b079c09b1c1439f44ce298fc5cb7
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Wed Apr 28 11:41:05 2010 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/20b5be2ffe26b079c09b1c1439f44ce298fc5cb7 [^]
Fixed issue 13030.
Build will be stopped in several cases in which even if there were errors, it didn't stop.
Fixed issue 13134.
Log will now only output the word error when there is indeed an error in the execution.
Fixed issue 11019
Messages similar to 'Executed 0 statements with 0 errors' will no longer be generated.
---
M src-db/database/lib/dbsourcemanager.jar
---
|
|
|
|
From reading dbsm-main commit history. The changes done to fix this issue have all been reverted to fix the regression tracked in 13191.
Please confirm and reschedule this issue as needed. |
|
|
(0027224)
|
hgbot
|
2010-05-14 10:41
|
|
Repository: erp/devel/dbsm-main
Changeset: 84b97399a1015055814ce16f8ce895b9b90e9a45
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Fri May 14 10:41:40 2010 +0200
URL: http://code.openbravo.com/erp/devel/dbsm-main/rev/84b97399a1015055814ce16f8ce895b9b90e9a45 [^]
Fixed issue 13030. The process will continue, but now an error (a log4j error) will be raised, thus, if the process was launched from the rebuild popup, the rebuild will end in error. The process will not be stopped, because even if an error happened, it's better for the user that the update.database process finishes.
---
M src/org/apache/ddlutils/platform/PlatformImplBase.java
---
|
|
|
(0027226)
|
hgbot
|
2010-05-14 10:53
|
|
Repository: erp/devel/pi
Changeset: c5d6492aad01501818339726d1b02e27b450f02e
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Fri May 14 10:42:50 2010 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/c5d6492aad01501818339726d1b02e27b450f02e [^]
Fixed issue 13134 (the 'succesfully' tag will be added correctly in case of forced commands). Fixed issue 13030 (The process will not be stopped, but a log4j error will be raised).
---
M src-db/database/lib/dbsourcemanager.jar
---
|
|
|
(0027372)
|
hgbot
|
2010-05-17 16:35
|
|
Repository: erp/devel/dbsm-main
Changeset: 1d8bea44fef6447839755fb5aeec6fdb7e42e518
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Mon May 17 16:34:57 2010 +0200
URL: http://code.openbravo.com/erp/devel/dbsm-main/rev/1d8bea44fef6447839755fb5aeec6fdb7e42e518 [^]
Reverted fix for issue 13030. To avoid any kind of raising false positive errors in the build, we will fix this in a different manner. A separate issue for this has been created with id=13340
---
M src/org/apache/ddlutils/platform/PlatformImplBase.java
---
|
|
|
(0027373)
|
hgbot
|
2010-05-17 16:36
|
|
Repository: erp/devel/pi
Changeset: d0bd5c606ec9695bc2fd42fd119ce1b3df48698b
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Mon May 17 16:35:30 2010 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/d0bd5c606ec9695bc2fd42fd119ce1b3df48698b [^]
Reverted fix for issue 13030. To avoid any kind of raising false positive errors in the build, we will fix this in a different manner. A separate issue for this has been created with id=13340
---
M src-db/database/lib/dbsourcemanager.jar
---
|
|
|
|
It has been decided that update.database will not be stopped even if errors happen in the process, because this would leave the database in a worse state than if we instead choose to continue until it ends.
Two fixes related to this issue have/will be made:
* The log of the update.database process has been improved so that it can be parsed easily, to figure out if there were indeed any kind of errors in the build:
https://issues.openbravo.com/view.php?id=13134 [^]
* The process itself needs to log errors which happened in critical parts of update.database as log4j errors, so that the build indeed fails from the user point of view:
https://issues.openbravo.com/view.php?id=13340 [^] |
|
|
|
|
|
|
|
|
|
|