versioning - Should i release maven library if one of its dependency changed? -


i have few libraries, of them depend on another. eg:

a 1.0.0 no dependencies

b 1.0.0 depends on: 1.0.0

question is:

if release 1.0.1 , release backward compatible 1.0.0 should release b?

this can depend lot on specifics of code , how artifacts deployed, in general, need release b make code changes in visible.

  • assume b jar artifact, , client has <dependency> on artifact. means client has transitive dependency on a, @ specific version expressed in <dependency> in b. taking example, client has dependency on b 1.0.0, has dependency on 1.0.0, client pick 1.0.0 transitively. in order publish bug fix in client, need release b 1.0.1 <dependency> on updated point 1.0.1.
  • assume b war artifact deployed in web application container. each jar <dependency> used web application shipped inside lib directory of built war. in order publish bug fix in web application, need release b 1.0.1 <dependency> on updated point 1.0.1.

in first example, (client depends on b jar), possible workaround client override version of adding own explicit <dependency> on a, perhaps using version range flexibility pick latest released version. can cause maintenance pitfalls though, because means client combining version of , version of b not tested part of b build. in general, it's preferrable release b, if difficult release b, can viable short-term workaround.

more details on transitive dependencies , version range syntax available here:


Comments

Post a Comment

Popular posts from this blog

javascript - Create a stacked percentage column -

i have collection of data : var data = [ {"p301a":"10","p301b":"7","p301c":"7","p301d":"3","p301e":"8","p301f":"8","p301g":"8","p301h":"8","p301i":"8","p301j":"8","p301k":"8","p301l":"8","p301m":"8","p301n":"8","p301o":"8","age":"31-40 years","profesion":"2","position":"2"}, {"p301a":"5","p301b":"4","p301c":"4","p301d":"4","p301e":"4","p301f":"4","p301g":"4","p301h":"4","p301i":"4","p301j":"4","p301k":"4...
Read more

Optimising Firebase database by automatically overwriting data -

in firebase app have following structure: posts latest all users can write posts > latest . want limit entries 20 posts save space in database. , posts beyond 20 unnecessary never shown on homepage. how can limit posts 20, when user writes posts > latest posts @ end drop off (be deleted) automatically? this sample should you. you need : const max_log_count = 20; exports.removeold = functions.database.ref('/posts/latest/{postid}').oncreate(event => { const parentref = event.data.ref.parent; return parentref.once('value').then(snapshot => { if (snapshot.numchildren() >= max_log_count) { let childcount = 0; const updates = {}; snapshot.foreach(function(child) { if (++childcount <= snapshot.numchildren() - max_log_count) { updates[child.key] = null; } }); // update parent. removes children. ...
Read more

javascript - Angular UI-Grid customTemplate directive causing rows to load slowly/? -

Image
each grid cell can have more 1 customtemplate loaded. have directive holds watcher on model_col_field listen cell updates on scroll when dom rows updated , recompile celltemplate . without watcher , $compile rows repeat on scroll, showing same set of rows. is there more angular way of approaching or way improve performance? relevant controller code: create gridoptions.data & gridoptions.columndefs : var customtemp = '<div ng-repeat="opt in grid.appscope.colvalueoptionsmodel" ng-init="tempstring=model_col_field.clazz+opt.key;"><comparison-directive dbo="model_col_field" attobj="opt" fff="grid.appscope.getattributetemplate(tempstring)" /></div>'; $scope.gridoptions.columndefs = [ { name:'yindex',pinnedleft:true,celltemplate: customtemp, displayname:'index'}, { name:'col1',celltemplate: customtemp}, { name:'col2',celltemplate: c...
Read more