Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||||||
| ID | ||||||||||||
| 0056050 | ||||||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||||||
| defect | [Openbravo ERP] Y. DBSourceManager | minor | always | 2024-07-17 14:16 | 2024-07-18 07:35 | |||||||
| Reporter | jgalarza | View Status | public | |||||||||
| Assigned To | Triage Platform Base | |||||||||||
| Priority | normal | 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 | 0056050: Improve error information when there is a cyclical dependency between modules | |||||||||||
| Description | We should improve this code to detect cycles and produce a more readable error for the steps. It's acceptable for it to fail, but it would be beneficial if it showed more information about what causes the cycle. Currently only the following line appears repeatedly before failing: ... [java] at org.openbravo.ddlutils.util.DBSMOBUtil.isDependant(DBSMOBUtil.java:401) [java] at org.openbravo.ddlutils.util.DBSMOBUtil.isDependant(DBSMOBUtil.java:401) [java] at org.openbravo.ddlutils.util.DBSMOBUtil.isDependant(DBSMOBUtil.java:401) ... | |||||||||||
| Steps To Reproduce | 1- Set Retail API as a Retail Discounts dependency 2- Run ant export.database 3- Run ant update.database -> the task fails. This is correct because after step 1, there is a cyclic dependency between modules. But note that the output is not informing about the reason of the failure. | |||||||||||
| 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 |
| 2024-07-17 14:16 | jgalarza | New Issue | |
| 2024-07-17 14:16 | jgalarza | Assigned To | => caristu |
| 2024-07-17 14:16 | jgalarza | Modules | => Core |
| 2024-07-17 14:16 | jgalarza | Triggers an Emergency Pack | => No |
| 2024-07-17 14:16 | jgalarza | Reproducibility | sometimes => always |
| 2024-07-18 07:30 | caristu | Assigned To | caristu => Triage Platform Base |
| 2024-07-18 07:30 | caristu | Steps to Reproduce Updated | View Revisions |
| 2024-07-18 07:35 | caristu | Description Updated | View Revisions |
| 2024-07-18 07:35 | caristu | Steps to Reproduce Updated | View Revisions |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |