Anonymous | Login
News | My View | View Issues | Roadmap | Summary

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformminorhave not tried2018-06-15 09:412018-06-22 10:21
ReporteralostaleView Statuspublic 
Assigned Toalostale 
PrioritynormalResolutionfixedFixed in Version3.0PR18Q3
StatusclosedFix in branchFixed in SCM revisiondb7d0b968a64
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned Tocaristu
Web browser
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0038765: ant version sent to heartbeat is not updated

Descriptionant version sent to heartbeat corresponds to the initial version in use when Openbravo was initially installed but not to the one used in latest builds.
Steps To Reproduce1. Using not the latest ant version run install.source
2. Update ant version
3. Build Openbravo again
4. Log in Openbravo and schedule a beat
5. Open Heartbeat configuration and check last beat in Heartbeat Log tab
  -> ERROR: it shows the ant version used in install.source, not the latest one
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to defect 0038740 closedalostale Tomcat version field sent in heartbeat statistics cannot be trusted as it is sending value from initial install forever. 
related to defect 0038838 closedcaristu ant version is not properly displayed in form view of System Info window 

-  Notes
hgbot (developer)
2018-06-15 10:13

Repository: erp/devel/pi
Changeset: db7d0b968a64c06dde36724e9c068d0fa8e530c2
Author: Asier Lostalé <asier.lostale <at>>
Date: Fri Jun 15 10:13:26 2018 +0200
URL: [^]

fixed issue 38765: ant version sent to heartbeat is not updated

  The ant version sent to heartbeat was calculated on install.source and never
  updated afterwards.

  Now it gets updated after each build (on update.database), this should add no
  overhead as ad_system_info was already updated anyway to set last time build
  has been performed.

M src-db/database/build.xml
hudsonbot (developer)
2018-06-19 13:24

A changeset related to this issue has been promoted main and to the
Central Repository, after passing a series of tests.

Promotion changeset: [^]
Maturity status: Test
caristu (developer)
2018-06-22 10:21

Code reviewed + tested OK.

- Issue History
Date Modified Username Field Change
2018-06-15 09:41 alostale New Issue
2018-06-15 09:41 alostale Assigned To => platform
2018-06-15 09:41 alostale Modules => Core
2018-06-15 09:41 alostale Triggers an Emergency Pack => No
2018-06-15 09:41 alostale Relationship added related to 0038740
2018-06-15 10:11 alostale Assigned To platform => alostale
2018-06-15 10:11 alostale Review Assigned To => caristu
2018-06-15 10:13 hgbot Checkin
2018-06-15 10:13 hgbot Note Added: 0105166
2018-06-15 10:13 hgbot Status new => resolved
2018-06-15 10:13 hgbot Resolution open => fixed
2018-06-15 10:13 hgbot Fixed in SCM revision => [^]
2018-06-19 13:24 hudsonbot Checkin
2018-06-19 13:24 hudsonbot Note Added: 0105240
2018-06-22 10:21 caristu Note Added: 0105331
2018-06-22 10:21 caristu Status resolved => closed
2018-06-22 10:21 caristu Fixed in Version => 3.0PR18Q3
2018-06-26 12:35 caristu Relationship added related to 0038838

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker