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

View Issue DetailsJump to Notes ] Issue History ] Print ]
ID
0015152
TypeCategorySeverityReproducibilityDate SubmittedLast Update
defect[Modules] Central Repositoryminorhave not tried2010-11-10 16:562020-04-13 10:56
ReportermarvintmView Statuspublic 
Assigned Toalostale 
PrioritynormalResolutionopenFixed in Version
StatusnewFix in branchFixed in SCM revision
ProjectionnoneETAnoneTarget Version
OSAnyDatabaseAnyJava version
OS VersionDatabase versionAnt version
Product VersionSCM revision 
Regression date
Regression introduced by commit
Regression level
Review Assigned To
Regression introduced in release
Summary

0015152: When a module version in an instance doesn't exist in central repository, only that module version is considered "compatible"

DescriptionConsider the following case:
- An Openbravo instance contains the following modules:
   * Module A with version 1.0.0
   * Module B with version 1.0.0, which depends on module A 1.0.0

- Central repository contains:
   * Module A with version 1.0.1
   * Module B with versions 1.0.0, and 1.0.1 (version 1.0.1 depends on module A 1.0.1)

Scan for updates will not find anything, because the module A version 1.0.0 doesn't exist in the central repository, and therefore will be the only version of module A considered compatible.
TagsNo tags attached.
Attached Files

- Relationships Relation Graph ] Dependency Graph ]

-  Notes
There are no notes attached to this issue.

- Issue History
Date Modified Username Field Change
2010-11-10 16:56 marvintm New Issue
2010-11-10 16:56 marvintm Assigned To => alostale
2020-04-13 10:56 alostale Severity major => minor


Copyright © 2000 - 2009 MantisBT Group
Powered by Mantis Bugtracker