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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0027700
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] A. Platformminorhave not tried2014-09-29 10:122022-02-01 08:05
ReportershuehnerView Statuspublic 
Assigned ToTriage Platform Base 
PrioritynormalResolutionopenFixed in Version
StatusacknowledgedFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
ModulesCore
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo
Summary

0027700: build.apply subfolder is not deleted in install.source

DescriptionThe build.apply folder (used for compiling subset of code needed for ApplyModulesTask) is not deleted on install.source.

That leads to following problem:
If one .class file is generated wrongly ever for some reason (i.e. exists with uptodate timestamp but 0 bytes).

Then every following install.source will also fail instead of cleanly reinstalling.

Note: build.apply is normally cleanup up after ApplyModules. So error truncating that file must have happened during execution of that task.

Note: to be decided if to delete build.apply only in install.source (i.e. cleanSubfolder of main build.xml) or in all compile.complete (i.e. src/build.xml clean task).

Note: as build.apply is always deleted after use normally no bad effect of doing every compile.complete and will give 'easier' fixing of the compilation problem described here.
Steps To ReproduceObserved in ci.

Probably following steps could reproduce it.
edit src/build.xml and comment out following line inside 'apply.module' task..
   <delete includeEmptyDirs="true" dir="${build.apply.module}" />
Needed to keep build.apply around after compile.
ant install.source
truncate -s0 ./build.apply/classes/org/openbravo/erpCommon/modules/ApplyModuleTask.class
That is to simulate that file being broken.

ant install.source again
Should work but will fail always as it will not recompile the ApplyModuleTask.java file (as .class exists and is recent enough (file timestamp newer then java).
Proposed Solutionadd line to delete build.apply (with content), ignoring if non-existent
to i.e. cleanSubFolders task.

TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
blocks design defect 0038296 acknowledgedTriage Platform Base Review & cleanup build.xml 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2014-09-29 10:12 shuehner New Issue
2014-09-29 10:12 shuehner Assigned To => AugustoMauch
2014-09-29 10:12 shuehner Modules => Core
2014-09-29 10:12 shuehner Triggers an Emergency Pack => No
2014-12-10 16:36 alostale Assigned To AugustoMauch => NaroaIriarte
2015-03-11 11:20 alostale Status new => acknowledged
2015-03-17 14:38 alostale Assigned To NaroaIriarte => platform
2018-04-08 16:56 shuehner Relationship added blocks 0038296
2022-02-01 08:05 alostale Assigned To platform => Triage Platform Base


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker