Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0017785Openbravo ERPA. Platformpublic2011-06-27 12:462011-07-06 02:41
Reporterpsarobe 
Assigned Tomarvintm 
PriorityimmediateSeveritymajorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Versionpi 
Target Version3.0MP0Fixed in Version3.0MP0 
Merge Request Status
Review Assigned To
OBNetwork customerNo
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0017785: Maturity level configuration is lost after updating to next MP
DescriptionDuring the test phase we have detected that the maturity level configuration is lost after updating to next MP
Steps To Reproduce1. Install mp30
2. Go to module management console. Change the maturity level for core to QA
3. Scan for updates and install MP31
4. Rebuild

After rebuilding login again and notice that the maturity level for that specific module "Core" has been removed
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
depends on backport 00177912.50MP31 closed alostale Maturity level configuration is lost after updating to 2.50MP31 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-06-27 12:46psarobeNew Issue
2011-06-27 12:46psarobeAssigned To => alostale
2011-06-27 12:46psarobeModules => Core
2011-06-27 12:46psarobeOBNetwork customer => No
2011-06-27 16:11alostaleStatusnew => scheduled
2011-06-27 16:11alostaleAssigned Toalostale => marvintm
2011-06-27 16:11alostalefix_in_branch => pi
2011-06-27 16:51psarobePrioritynormal => immediate
2011-06-27 16:51psarobeTarget Version2.50MP31 => 3.0MP0
2011-06-27 16:51psarobefix_in_branchpi =>
2011-06-27 16:55psarobeSteps to Reproduce Updatedbug_revision_view_page.php?rev_id=2297#r2297
2011-06-27 19:01gorka_gilIssue Monitored: gorka_gil
2011-06-28 09:43hgbotCheckin
2011-06-28 09:43hgbotNote Added: 0038547
2011-06-28 09:43hgbotStatusscheduled => resolved
2011-06-28 09:43hgbotResolutionopen => fixed
2011-06-28 09:43hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/0c217e73cca3fe9b80f831f52a513cca46dd6be8 [^]
2011-06-28 12:11hgbotCheckin
2011-06-28 12:11hgbotNote Added: 0038559
2011-06-28 12:11hgbotFixed in SCM revisionhttp://code.openbravo.com/erp/devel/pi/rev/0c217e73cca3fe9b80f831f52a513cca46dd6be8 [^] => http://code.openbravo.com/erp/devel/dbsm-main/rev/be196a74e449ef1c1831f1cf077f54117c4a0864 [^]
2011-06-29 09:38psarobeStatusresolved => closed
2011-06-29 09:38psarobeFixed in Version => 3.0MP0
2011-06-29 17:43gorka_gilSummaryMaturity level configuration is lost after updating to 2.50MP31 => Maturity level configuration is lost after updating to next MP
2011-06-29 17:43gorka_gilDescription Updatedbug_revision_view_page.php?rev_id=2315#r2315
2011-07-06 02:41hudsonbotCheckin
2011-07-06 02:41hudsonbotNote Added: 0038811

Notes
(0038547)
hgbot   
2011-06-28 09:43   
Repository: erp/devel/pi
Changeset: 0c217e73cca3fe9b80f831f52a513cca46dd6be8
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Tue Jun 28 09:42:45 2011 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/0c217e73cca3fe9b80f831f52a513cca46dd6be8 [^]

Fixed issue 17785. Maturity level on modules will not be deleted on update.database

---
M src-db/database/lib/dbsourcemanager.jar
---
(0038559)
hgbot   
2011-06-28 12:11   
Repository: erp/devel/dbsm-main
Changeset: be196a74e449ef1c1831f1cf077f54117c4a0864
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Tue Jun 28 12:10:51 2011 +0200
URL: http://code.openbravo.com/erp/devel/dbsm-main/rev/be196a74e449ef1c1831f1cf077f54117c4a0864 [^]

Fixed issue 17785. Maturity level on modules will not be deleted on update.database.
- A second resetDynaClass method has been added. This new one resets the DynaClass properties, but only adds the ones which have a corresponding column in the old table. Therefore, if an updateinsert or update is executed, only the columns which exist both in the old table and the new one will be modified.
- This means that when copying the module_install data into the module table, the columns which do not exist in the module_install table will not be touched (thus preserving data such as the maturity level, and any other column which is not written into the module_install when installing or updating the module)

---
M src/org/apache/ddlutils/dynabean/SqlDynaClass.java
M src/org/openbravo/ddlutils/util/DBSMOBUtil.java
---
(0038811)
hudsonbot   
2011-07-06 02:41   
A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: https://code.openbravo.com/erp/devel/main/rev/f1c481b1a146 [^]

Maturity status: Test