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

View Issue DetailsJump to Notes ] Issue History ] Print ]
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Openbravo ERP] Y. DBSourceManagerminorhave not tried2021-02-22 15:062021-02-22 15:06
ReportershuehnerView Statuspublic 
Assigned Toplatform 
PrioritynormalResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Review Assigned To
Web browser
Regression level
Regression date
Regression introduced in release
Regression introduced by commit
Triggers an Emergency PackNo

0045934: Update commons-collections in dbsm repo (3.2.1) to same version as present in backoffice (3.2.2)

DescriptionIssue 40161 update that library from 3.2.1 to latest 3.2.2 version to also get a security fix.

However there is 2nd copy of the same library in dbsm repo left at the older version.

Note that the older copy is only used to compile dbsm and not at runtime (in which updated copy from backoffice repo is already used).

So no runtime change is expected by this update but it removes out the outdated jar version coming up in repo scanning.
Steps To Reproducerun i.e. owasp-dependency check against dbsm repo
Proposed SolutionApply same update as done in 40161 also to dbsm repo.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]
related to design defect 0040161 closedalostale update commons-collections dependency 

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2021-02-22 15:06 shuehner New Issue
2021-02-22 15:06 shuehner Assigned To => platform
2021-02-22 15:06 shuehner Modules => Core
2021-02-22 15:06 shuehner Triggers an Emergency Pack => No
2021-02-22 15:06 shuehner Relationship added related to 0040161

Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker