Anonymous | Login
Project:
RSS
  
News | My View | View Issues | Roadmap | Summary

View Revisions: Issue #56050 Back to Issue ]
Summary 0056050: Improve error information when there is a cyclical dependency between modules
Revision 2024-07-18 07:35 by caristu
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.
Revision 2024-07-18 07:35 by caristu
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)
...
Revision 2024-07-18 07:30 by caristu
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.
Revision 2024-07-18 07:30 by caristu
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
Revision 2024-07-18 07:30 by caristu
Steps To Reproduce Set Retail API as a Retail Discounts dependency


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker