Openbravo Issue Tracking System - Openbravo ERP |
View Issue Details |
|
ID | Project | Category | View Status | Date Submitted | Last Update |
0005926 | Openbravo ERP | 00. Application dictionary | public | 2008-11-12 05:26 | 2009-02-27 02:54 |
|
Reporter | elopio | |
Assigned To | mtaal | |
Priority | normal | Severity | minor | Reproducibility | always |
Status | closed | Resolution | fixed | |
Platform | | OS | 20 | OS Version | Ubuntu 8.10 |
Product Version | | |
Target Version | | Fixed in Version | | |
Merge Request Status | |
Review Assigned To | |
OBNetwork customer | |
Web browser | |
Modules | Core |
Support ticket | |
Regression level | |
Regression date | |
Regression introduced in release | |
Regression introduced by commit | |
Triggers an Emergency Pack | No |
|
Summary | 0005926: Rebuilds are not logged in Installation History |
Description | When you perform a rebuild, it's not registered on installation history log.
Severity is minor because a file is created everytime you perform a rebuild, but I think it's inconsistent. I would prefer to log every action related to modules. |
Steps To Reproduce | 1. Go to Module Management
2. Go to add modules.
3. Click search and install a module.
4. Go to installed modules.
5. Rebuild. |
Proposed Solution | Log rebuild actions. |
Additional Information | |
Tags | Modularity, platform1_sprint1 |
Relationships | blocks | defect | 0006261 | | closed | mtaal | Properly manage log in rebuild process |
|
Attached Files | |
|
Issue History |
Date Modified | Username | Field | Change |
2008-11-12 05:26 | elopio | New Issue | |
2008-11-12 05:26 | elopio | Assigned To | => rafaroda |
2008-11-12 05:26 | elopio | sf_bug_id | 0 => 2266944 |
2008-11-12 05:26 | elopio | Regression testing | => No |
2008-11-12 05:27 | elopio | Tag Attached: Modularity | |
2008-11-20 10:23 | rafaroda | Status | new => scheduled |
2008-11-20 10:23 | rafaroda | Assigned To | rafaroda => gorka_gil |
2008-11-20 10:23 | rafaroda | fix_in_branch | => trunk |
2008-12-09 12:53 | gorka_gil | Assigned To | gorka_gil => mtaal |
2008-12-15 06:53 | mtaal | Tag Attached: platform1_sprint1 | |
2008-12-20 20:45 | mtaal | Note Added: 0011631 | |
2008-12-22 13:51 | svnbot | Checkin | |
2008-12-22 13:51 | svnbot | Note Added: 0011655 | |
2008-12-22 13:51 | svnbot | Status | scheduled => resolved |
2008-12-22 13:51 | svnbot | Resolution | open => fixed |
2008-12-22 13:51 | svnbot | svn_revision | => 11471 |
2009-01-06 11:17 | mtaal | Relationship added | blocks 0006261 |
2009-02-27 02:54 | elopio | Status | resolved => closed |
Notes |
|
(0011631)
|
mtaal
|
2008-12-20 20:45
|
|
Hi Martin,
it is not "logging" in a file but in a table. All actions related to Module
Management window (Install, Uninstall, Scan for updates, ...) are tracked in
the AD_Module_Log table. This table has a column (Action) about what action
the user has performed. It is a list
(ad_reference_id='7CD9193198B94EF5B174D0F8512B0857'). There is an action for
"Build now" (value = 'B') but the ant task to build the system is not
inserting in this table.
For this action AD_Module_ID, AD_Module_Version_ID and ModuleName should be
null, so only standard columns and Log and Action should be inserted. In
action only the final result (Build Succesful or Build Failure) should be
written (we only have 2000 characters).
Ismael |
|
|
(0011655)
|
svnbot
|
2008-12-22 13:51
|
|
Repository: openbravo
Revision: 11471
Author: mtaal
Date: 2008-12-22 13:51:07 +0100 (Mon, 22 Dec 2008)
Fixes issue 6088, Modularity: compilation errors are not in the log
Fixes issue 5926, Rebuilds are not logged in Installation History
---
U trunk/src/org/openbravo/erpCommon/ad_process/ApplyModules.java
U trunk/src/org/openbravo/erpCommon/utility/AntExecutor.java
U trunk/src-db/database/model/tables/AD_MODULE_LOG.xml
U trunk/src-db/database/sourcedata/AD_COLUMN.xml
U trunk/src-db/database/sourcedata/AD_TABLE.xml
U trunk/src-db/database/sourcedata/AD_TEXTINTERFACES.xml
---
https://dev.openbravo.com/websvn/openbravo/?rev=11471&sc=1 [^]
|
|