Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0030059 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| design defect | [Openbravo ERP] A. Platform | major | have not tried | 2015-06-01 11:21 | 2022-02-01 08:09 | |||||||
| Reporter | egoitz | View Status | public | |||||||||
| Assigned To | Triage Platform Base | |||||||||||
| Priority | immediate | Resolution | open | Fixed in Version | ||||||||
| Status | new | Fix in branch | Fixed in SCM revision | |||||||||
| Projection | none | ETA | none | Target Version | ||||||||
| OS | Any | Database | Any | Java version | ||||||||
| OS Version | Database version | Ant version | ||||||||||
| Product Version | SCM revision | |||||||||||
| Review Assigned To | ||||||||||||
| Web browser | ||||||||||||
| Modules | Core | |||||||||||
| Regression level | ||||||||||||
| Regression date | ||||||||||||
| Regression introduced in release | ||||||||||||
| Regression introduced by commit | ||||||||||||
| Triggers an Emergency Pack | No | |||||||||||
| 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) | |||||||||||
| Tags | No tags attached. | |||||||||||
| Attached Files | ||||||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
||||||||
|
||||||||
 Relationships |
|
Notes |
|
| There are no notes attached to this issue. |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2015-06-01 11:21 | egoitz | New Issue | |
| 2015-06-01 11:21 | egoitz | Assigned To | => platform |
| 2015-06-01 11:21 | egoitz | Modules | => Core |
| 2015-06-01 11:21 | egoitz | Triggers an Emergency Pack | => No |
| 2015-06-01 11:21 | egoitz | Issue generated from | 0029950 |
| 2015-06-03 17:03 | alostale | Relationship added | related to 0029950 |
| 2015-07-08 16:53 | ngarcia | Issue Monitored: ngarcia | |
| 2022-02-01 08:09 | alostale | Assigned To | platform => Triage Platform Base |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |