0016542: ant package.module does not create the obx file if the dependencies are not exactly satisfied

Openbravo Issue Tracking System - Openbravo ERP

View Issue Details

Project

Category

View Status

Date Submitted

Last Update

0016542

Openbravo ERP

A. Platform

public

2011-03-29 16:39

2011-08-05 12:21

Reporter

mirurita

Assigned To

alostale

Priority

normal

Severity

minor

Reproducibility

always

Status

closed

Resolution

out of date

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

0016542: ant package.module does not create the obx file if the dependencies are not exactly satisfied

Description

The following scenario:
Module A - version 1.0.0 depends (major dependency) on Module B 1.0.0 - 3.0.0

If an issue is solved in Module A not affecting the dependency (so it still depends on Module B 1.0.0), when trying to package the version 1.0.1 of Module A and in your environment you have the version 3.0.2 of Module B the ant package.module throws an error:

[validateModules] +++++++++++++++++++++++++++++++++++++++++++++++++++
[validateModules] Errors for Validation type: MODULE_ERROR
[validateModules] +++++++++++++++++++++++++++++++++++++++++++++++++++
[validateModules] Module A defines dependency on Module B end version 3.0.0, but actual version in DB is 3.0.2
[validateModules] 53602 [main] ERROR org.openbravo.base.exception.OBException

I think this should be possible because is a common scenario.

It appeared after this changeset
https://code.openbravo.com/erp/devel/pi/rev/fc7ec1644bf0 [^]

Steps To Reproduce

1) Create module A 1.0.0
2) Create module B 1.0.2
3) Define dependency: module A --> module B <1.0.0, 3.0.0> major
4) run ant package.module -Dmodule=moduleA

Proposed Solution

Additional Information