bamaer opened a new issue, #9613:
URL: https://github.com/apache/hop/issues/9613

   ### What would you like to happen?
   
   Updating a marketplace plugin today means installing the new version over 
the old one (#{N1}), and there is no way back.
   
   An update goes through one transaction:
   1. stage the new version and compare it with the receipt
   2. back up what will be replaced or removed to 
`plugins/.marketplace/backup/<artifactId>/<version>`
   3. apply, then write the receipt
   
   If any step fails, the backup is restored.
   
   - `hop marketplace update <artifactId>` and `--all`
   - `hop marketplace list --outdated`
   - `hop marketplace rollback <artifactId>` restores the previous version
   - Plugins tab: an "Update available" column and Update / Rollback buttons
   - `hop marketplace apply` uses the same path when a version in the install 
spec changes
   
   On Windows, `lib/core` changes that cannot be made while Hop runs stay 
pending until #{N6}.
   
   Needs the receipt changes from #{N2}.
   
   
   ### Issue Priority
   
   Priority: 2
   
   ### Issue Component
   
   Component: Marketplace
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to