Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Prefer latest built add-on #5109

Merged
merged 1 commit into from
Nov 9, 2018

Conversation

thc202
Copy link
Member

@thc202 thc202 commented Nov 9, 2018

Consider newer (by modification date) add-on to be update to older
add-on when both have the same name, status, and version to ensure that
the latest built add-on is always used even if deployed to a different
plugin dir (e.g. home, install, or additional add-on dirs).

Consider newer (by modification date) add-on to be update to older
add-on when both have the same name, status, and version to ensure that
the latest built add-on is always used even if deployed to a different
plugin dir (e.g. home, install, or additional add-on dirs).
@psiinon psiinon merged commit edf182e into zaproxy:develop Nov 9, 2018
@thc202 thc202 deleted the add-on-update-latest-built branch November 9, 2018 16:53
@lock
Copy link

lock bot commented Oct 31, 2019

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked and limited conversation to collaborators Oct 31, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

Successfully merging this pull request may close these issues.

3 participants