0030059: Not possible to force the update to a concrete release by using a custom module with specific dependencies

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0030059

Openbravo ERP

A. Platform

public

2015-06-01 11:21

2022-02-01 08:09

Reporter

egoitz

Assigned To

Triage Platform Base

Priority

immediate

Severity

major

Reproducibility

have not tried

Status

new

Resolution

open

Platform

OS Version

Product Version

Target Version

Fixed in Version

Merge Request Status

Review Assigned To

OBNetwork customer

Web browser

Modules

Core

Support ticket

Regression level

Regression date

Regression introduced in release

Regression introduced by commit

Triggers an Emergency Pack

Summary

0030059: Not possible to force the update to a concrete release by using a custom module with specific dependencies

Description

As described on the following link, it is possible to make a module compatible with concrete releases.

http://wiki.openbravo.com/wiki/Modularity_Concepts#Dependency_types [^]

Minor Version: In case both First Version and Last Version are defined, the compatibility is from the minor version in First Version to the minor version in Last Version (even they belong to the same major version). If Last Version is blank, the only compatible version will be the one defined by the First Version.

Having a module with a dependency with core defining and start version and end version, you should be able to update core from the starting version defined to the last version by using the module management console

Steps To Reproduce

-Start on PR14Q3.2 release: 3.0.24034

-Define a new module depending on core with start version 3.0.24034
and end version 3.0.24112 (PR1Q3.8) with minor enforcement.

-Go to module managemente window and scan for updates.
*No updates are shown but you should be able to update to 3.0.24112 (PR14Q3.8)

Proposed Solution

Additional Information