[RTFACT-9921] In remote repositories, the bower.version should always be set from the tag Created: 21/Apr/16  Updated: 14/Nov/17  Resolved: 23/Jun/16

Status: Resolved
Project: Artifactory Binary Repository
Component/s: Bower
Affects Version/s: 4.5.2
Fix Version/s: 4.9.0

Type: Improvement Priority: Normal
Reporter: Alexei Vainshtein Assignee: Alexei Vainshtein
Resolution: Fixed Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Support Tickets:

American Family Insurance - Support Case, Lead - Support Case

Product Backlog: 4.9.0
Assigned QA: Mor Iluz (Inactive)
Internal Priority: Normal

 Description   

Currently, if there is a bower.json file and version inside the file, the bower.version is populated from this file. If the version is missing then we are putting the tag as a version.

The issue that can happen if the tag and the version inside the bower.json file are not matching. In this case the resolution will be according to the tag but the version property will be different.


Generated at Mon Dec 16 11:42:17 UTC 2019 using JIRA 7.6.16#76018-sha1:9ed376192612a49536ac834c64177a0fed6290f5.