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

Extension version 0.11.1 no longer respecting META-INF/context.xml #234

Closed
gmowhiz opened this issue Dec 7, 2018 · 1 comment
Closed

Comments

@gmowhiz
Copy link
Contributor

gmowhiz commented Dec 7, 2018

  • VSCode Version: 1.29.1
  • OS Version: macOS mojave 10.14.1 (18B75)
  • Tomcat Extension Version: 0.11.1

Steps to Reproduce:
In version 0.11.0 of the extension, a new feature was added to support the designation of the deployment context in the META-INF/context.xml file. This appears to be broken in version 0.11.1 of the extension (at least it is for me).

  1. Build a project with a META-INF/context.xml file that contains the following:
<?xml version="1.0" encoding="UTF-8"?>
<Context path=""/>
  1. Build your project.

  2. Validate that META-INF/context.xml is present in the generated war or output directory.

  3. Right-click and select "Debug on Tomcat Server" for either the generated <projectName>.war or the target/<projectName> output directory.

  4. Confirm that Tomcat is launched but the app was deployed to the <projectName> context rather than the root context as was defined in the context.xml.

  5. This worked for me in 0.11.0 of vscode-tomcat but is not working in 0.11.1. The workaround is to revert back to the previous extension version.

@gmowhiz gmowhiz changed the title Latest version no longer respecting META-INF/context.xml Extension version 0.11.1 no longer respecting META-INF/context.xml Dec 7, 2018
@Eskibear
Copy link
Collaborator

fixed in 0.12.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants