-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
Improve deployment of symlinked webapplications #6565
Comments
I think that at deployment time, either the deployer or the WebAppContext needs to resolve the base resource to its real path, but use the linked path for determining the context path (if none is set). |
It looks like this can be fixed by resolving to the real file either in the deployer or in the ContextHandler. This first corrects this issue only for deployed webapps, whilst the later will resolve for all usages. |
Fix #6565 Deploy Symlinked applications by treating extracting context name (which becomes the default context path) from the base resource and then following aliases, so that base resource will not be an alias. Added warning in ContextHandler if the base resource is an alias that we may not support this in future releases. Signed-off-by: Greg Wilkins <gregw@webtide.com>
Keep resource and file the same. Signed-off-by: Greg Wilkins <gregw@webtide.com>
Fix #6565 Deploy Symlinked applications by treating extracting context name (which becomes the default context path) from the base resource and then following aliases, so that base resource will not be an alias. Added warning in ContextHandler if the base resource is an alias that we may not support this in future releases. Signed-off-by: Greg Wilkins <gregw@webtide.com>
Target Jetty version(s)
9, 10
Enhancement Description
After #6114 we can now deploy symlinked war files with the correct context path. eg.
But the following does not work correctly:
The text was updated successfully, but these errors were encountered: