Openbravo Issue Tracking System - Openbravo ERP
View Issue Details
IDProjectCategoryView StatusDate SubmittedLast Update
0014512Openbravo ERPA. Platformpublic2010-09-10 10:232010-09-14 00:00
Reportergorka_gil 
Assigned Tomarvintm 
PriorityhighSeverityminorReproducibilityalways
StatusclosedResolutionfixed 
PlatformOS5OS Version
Product Version3.0RC2 
Target VersionFixed in Version 
Merge Request Status
Review Assigned To
OBNetwork customer
Web browser
ModulesCore
Support ticket
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary0014512: ant export.config.script gives a java.io.FileNotFoundException: src-db/database/formalChangesScript.xml
DescriptionTrying to export the config script of a template gives this error:

java.io.FileNotFoundException: src-db/database/formalChangesScript.xml

The modules have been installed by uncompressing the obx in modules directory and doing a install.source.
Steps To Reproduce1) Uncompress all the obx for 3.0 RC2 in modules directory
2) ant install.source
3) put the template for 3.0 rc2 in development
4) Edit a preference (this should be added to the config script)
5) ant export.database (finish ok)
6) ant export.config.script --> FAILS with the above error.
Proposed SolutionNot a solution, but a workaround:

After do the install.source, do an ant update.database.

This will generate this file and all the process will work.
Additional Information
TagsNo tags attached.
Relationships
Attached Files
Issue History
Date ModifiedUsernameFieldChange
2010-09-10 10:23gorka_gilNew Issue
2010-09-10 10:23gorka_gilAssigned To => marvintm
2010-09-10 10:25shuehnerIssue Monitored: shuehner
2010-09-10 18:18hgbotCheckin
2010-09-10 18:18hgbotNote Added: 0030945
2010-09-10 18:18hgbotStatusnew => resolved
2010-09-10 18:18hgbotResolutionopen => fixed
2010-09-10 18:18hgbotFixed in SCM revision => http://code.openbravo.com/erp/devel/dbsm-main/rev/02c8ada1a547892ed16a14a5065360700396c531 [^]
2010-09-10 18:21hgbotCheckin
2010-09-10 18:21hgbotNote Added: 0030947
2010-09-10 18:21hgbotFixed in SCM revisionhttp://code.openbravo.com/erp/devel/dbsm-main/rev/02c8ada1a547892ed16a14a5065360700396c531 [^] => http://code.openbravo.com/erp/devel/pi/rev/63f0d75306d065ee0cffb01fbef7868ba4878499 [^]
2010-09-11 07:19hudsonbotCheckin
2010-09-11 07:19hudsonbotNote Added: 0030957
2010-09-13 13:42shuehnerNote Added: 0030991
2010-09-13 13:42shuehnerStatusresolved => closed
2010-09-14 00:00anonymoussf_bug_id0 => 3065585

Notes
(0030945)
hgbot   
2010-09-10 18:18   
Repository: erp/devel/dbsm-main
Changeset: 02c8ada1a547892ed16a14a5065360700396c531
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Fri Sep 10 10:40:21 2010 +0200
URL: http://code.openbravo.com/erp/devel/dbsm-main/rev/02c8ada1a547892ed16a14a5065360700396c531 [^]

Fixed issue 14512. Export.config.script will no longer fail if formalChangesScript.xml doesn't exist

---
M src/org/openbravo/ddlutils/task/ExportConfigScript.java
---
(0030947)
hgbot   
2010-09-10 18:21   
Repository: erp/devel/pi
Changeset: 63f0d75306d065ee0cffb01fbef7868ba4878499
Author: Antonio Moreno <antonio.moreno <at> openbravo.com>
Date: Fri Sep 10 10:40:34 2010 +0200
URL: http://code.openbravo.com/erp/devel/pi/rev/63f0d75306d065ee0cffb01fbef7868ba4878499 [^]

Fixed issue 14512. Export.config.script will no longer fail if formalChangesScript.xml doesn't exist

---
M src-db/database/lib/dbsourcemanager.jar
---
(0030957)
hudsonbot   
2010-09-11 07:19   
A changeset related to this issue has been promoted to main after passing a series of tests and an OBX has been generated:

Changeset: http://code.openbravo.com/erp/devel/main/rev/63f0d75306d0 [^]
Merge Changeset: http://code.openbravo.com/erp/devel/main/rev/06ead0b24d2d [^]
Tests: http://builds.openbravo.com/view/int/ [^]
OBX: http://builds.openbravo.com/erp/core/obx/OpenbravoERP-2.50CI.18370.obx [^]
(0030991)
shuehner   
2010-09-13 13:42   
Reviewed/Tested on pi/pgsql. Now export.configscript does run if the formalChangesScript does not exist (i.e. directly after an install.source, without ever doing an update.database). This makes it possible to use export.config.script immediately after an install.source, however the feature to not export formal changes to an configScript is still only when using export.config.script after at least one update.database. -> Closing