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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0007562
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformmajorhave not tried2009-02-13 17:372009-04-22 00:00
ReportermtaalView Statuspublic 
Assigned Tomarvintm 
PriorityhighResolutionfixedFixed in Version2.50beta
StatusclosedFix in branchFixed in SCM revision13307
ProjectionnoneETAnoneTarget Versionpi
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionpiSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0007562: Update of module status fails resulting in difficult to understand issues later in the build process

DescriptionThe status of modules is updated in the beginning of the buildprocess:
in the database.postupdate step. If this fails (see below [1]) then this results in the following unpredictable behavior:
- the status of the core module is not set to P
- in the apply module step later in the build the referencedata of the module is not imported (this is the referencedata/standard/Masterdata.xml) because the core module does not have the correct status
- the import of sample data fails because it misses data, the error message of the import.sample.data is:
[importsampledata] org.openbravo.base.exception.OBException: org.hibernate.PropertyValueException: not-null property references a null or transient value: Currency.iSOCode

[1]
      [sql] Failed to execute: UPDATE AD_MODULE SET ISINDEVELOPMENT='N', ISDEFAULT='N', SEQNO=NULL, STATUS='P', UPDATE_AVAILABLE=NULL, ISREGISTERED='N' WHERE STATUS IS NULL OR STATUS='I'
      [sql] org.postgresql.util.PSQLException: ERROR: The version has to be formatted like x.y.z where x, y and z are integers.
      [sql] 9 of 10 SQL statements executed successfully


Proposed SolutionProposed solution:
- perform the update statement for each module separately
- let the build fail if the update statements do not finish correctly
TagsModularity
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
(0013637)
svnbot (reporter)
2009-02-18 12:45

Repository: openbravo
Revision: 13307
Author: marvintm
Date: 2009-02-18 12:45:42 +0100 (Wed, 18 Feb 2009)

Fixed issue 7562. Now build will fail if postcreate or postupdate tasks fail. This will ensure that import of masterdata and sampledata do not fail later on in the process.

---
U trunk/src-db/database/build-create.xml
U trunk/src-db/database/build.xml
---

https://dev.openbravo.com/websvn/openbravo/?rev=13307&sc=1 [^]

- Issue History
Date Modified Username Field Change
2009-02-13 17:37 mtaal New Issue
2009-02-13 17:37 mtaal Assigned To => rafaroda
2009-02-13 17:37 mtaal Regression testing => No
2009-02-13 17:39 mtaal Assigned To rafaroda => marvintm
2009-02-17 18:23 rafaroda Priority normal => high
2009-02-17 18:23 rafaroda Status new => scheduled
2009-02-17 18:33 rafaroda Tag Attached: Modularity
2009-02-18 12:45 svnbot Checkin
2009-02-18 12:45 svnbot Note Added: 0013637
2009-02-18 12:45 svnbot Status scheduled => resolved
2009-02-18 12:45 svnbot Resolution open => fixed
2009-02-18 12:45 svnbot svn_revision => 13307
2009-04-21 10:33 psarobe Status resolved => closed
2009-04-22 00:00 anonymous sf_bug_id 0 => 2777939


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker