Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0017350Openbravo ERPA. Platformpublic2011-05-25 12:162011-06-10 13:01
Reportereduardo_Argal 
Assigned Tomarvintm 
PriorityimmediateSeveritymajorReproducibilitysometimes
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionpiFixed in Version 
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
Summary0017350: Problems with build validation when installing a module
DescriptionWhen installing a module through module management console, just validations of the modules being installed are executed. This is a problem when a validation of an already installed module tries to manage dependent modules version (Ex. APRM needs to be in a particular version or higher for it to properly run on top of a core MP. Core does an API change that forces APRM to be updated as well and that prevents previous versions to be installed)
Steps To Reproduce1) Install 2.50 MP 30
2) Install APRM 1.0.14
3) Rebuild


Mind that core validations are not executed resulting in a failure of rebuild process with no message to end user.
Proposed SolutionForce build validations to be executed whatever module is being installed. All buildvalidations should be executed in rebuild process.
Additional Information
TagsNo tags attached.
Relationships
depends on backport 0017351pi closed marvintm Problems with build validation when installing a module 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2011-05-25 12:16eduardo_ArgalNew Issue
2011-05-25 12:16eduardo_ArgalAssigned To => marvintm
2011-05-25 12:16eduardo_ArgalModules => Core
2011-05-25 12:16eduardo_ArgalOBNetwork customer => No
2011-05-25 12:16eduardo_ArgalStatusnew => scheduled
2011-05-25 12:16eduardo_Argalfix_in_branch => pi
2011-05-25 12:20hgbotCheckin
2011-05-25 12:20hgbotNote Added: 0037420
2011-05-25 12:20hgbotStatusscheduled => resolved
2011-05-25 12:20hgbotResolutionopen => fixed
2011-05-25 12:20hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/pi/rev/9eac8c7e50a5b4aa51aa56af8d9b6bda99132476 [^]
2011-05-26 07:47hudsonbotCheckin
2011-05-26 07:47hudsonbotNote Added: 0037554
2011-06-10 13:01shuehnerNote Added: 0038228
2011-06-10 13:01shuehnerStatusresolved => closed

Notes
(0037420)
hgbot   
2011-05-25 12:20   
Repository: erp/devel/pi
Changeset: 9eac8c7e50a5b4aa51aa56af8d9b6bda99132476
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Wed May 25 12:19:36 2011 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/9eac8c7e50a5b4aa51aa56af8d9b6bda99132476 [^]

Fixed issue 17350. All the BuildValidations will always be executed on update.database

---
M src-core/src/org/openbravo/buildvalidation/BuildValidationHandler.java
---
(0037554)
hudsonbot   
2011-05-26 07:47   
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/728387046be6 [^]

Maturity status: Test
(0038228)
shuehner   
2011-06-10 13:01   
Reviewed+tested in pi-mp0 (rev: 3006ebd37390). Now update.database will run all buildvalidation for all currently unpacked modules always and not just the ones for modules being installed/updated right now.

Note: tested on different testcase created for this (install random-module, check list of buildvalidation executed if they include all) and not on testcase as specified in the issue as that one is 2.50 specific.