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

Tags

No tags attached.

Attached Files

Relationships [ Relation Graph ] [ Dependency Graph ]

related to

defect

0015870

2.50MP28

closed

alostale

Having a module include in a package two times, the package module task gives an error, but packages the module

Notes
(0039907) alostale (manager) 2011-08-05 12:21	Working fine now

Issue History
Date Modified	Username	Field	Change
2011-03-29 16:39	mirurita	New Issue
2011-03-29 16:39	mirurita	Assigned To	=> alostale
2011-03-29 16:39	mirurita	Modules	=> Core
2011-03-30 13:00	alostale	Relationship added	related to 0015870
2011-03-30 13:01	alostale	Status	new => scheduled
2011-03-30 13:01	alostale	fix_in_branch	=> pi
2011-08-05 12:21	alostale	Note Added: 0039907
2011-08-05 12:21	alostale	Status	scheduled => closed
2011-08-05 12:21	alostale	Resolution	open => out of date