Openbravo Issue Tracking System - Modules
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014522ModulesCentral Repositorypublic2010-09-13 10:002014-04-01 21:46
Reporteralostale 
Assigned Toalostale 
PriorityurgentSeveritymajorReproducibilityN/A
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version 
Target VersionFixed in Version 
Merge Request Status
Regression date
Regression introduced by commit
Regression level
Review Assigned To
Support ticket
OBNetwork customer
Regression introduced in release
Summary0014522: Check dependencies maturity status when setting a new one
DescriptionWhen a new module is published, or its maturity status is changed, it should be verified all its dependencies (direct or indirect) have at least the same maturity status that is about to be set, other case this module wouldn't be accepted in ERP instances setting the defined maturity status.

In case there's dependencies with a lower maturity status this should be reported to the user, and the new maturity status wouldn't be settable.
Steps To Reproduce
Proposed Solution
Additional Information
TagsNo tags attached.
Relationships
related to feature request 0014520 scheduled alostale Validate module depends in core on publication 
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-09-13 10:00alostaleNew Issue
2010-09-13 10:00alostaleAssigned To => alostale
2010-09-13 10:00alostaleStatusnew => scheduled
2010-09-13 10:00alostalefix_in_branch => pi
2010-09-13 10:01alostaleRelationship addedrelated to 0014520
2010-09-21 13:01alostaleNote Added: 0031271
2010-09-21 13:03hgbotCheckin
2010-09-21 13:03hgbotNote Added: 0031272
2010-09-21 13:03hgbotStatusscheduled => resolved
2010-09-21 13:03hgbotResolutionopen => fixed
2010-09-21 13:03hgbotFixed in SCM revision => http://code.openbravo.com/erp/pmods/org.openbravo.utility.centralrepository/rev/e82c40744998c632d11aae637aa0bc1af41ce2b7 [^]
2014-04-01 21:46plujanNote Added: 0065720
2014-04-01 21:46plujanStatusresolved => closed

Notes
(0031271)
alostale   
2010-09-21 13:01   
Indirect dependencies needn't be checked as they were checked when publishing. When canceling a module it is checked (including indirect dependencies) there is no dependencies broken so there's no case where it is needed more than 1 level depth.
(0031272)
hgbot   
2010-09-21 13:03   
Repository: erp/pmods/org.openbravo.utility.centralrepository
Changeset: e82c40744998c632d11aae637aa0bc1af41ce2b7
Author: Asier Lostalé <asier.lostale <at> openbravo.com>
Date: Tue Sep 21 13:02:08 2010 +0200
URL: http://code.openbravo.com/erp/pmods/org.openbravo.utility.centralrepository/rev/e82c40744998c632d11aae637aa0bc1af41ce2b7 [^]

fixed issue 14522: Check dependencies maturity status when publishing

---
M src/org/openbravo/utility/centralrepository/process/PublishModule.java
---
(0065720)
plujan   
2014-04-01 21:46   
Closed as marked as Resolved for too long