Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Deploy to Tomcat by dropping .WAR into webapps folder stops root app working #192
Steps to reproduce:
The problem is that we don't want our WAR affecting other apps.
If you follow similar steps but instead of deploying by dropping the .WAR file into the directory you use the app manager and deploy via the web interface then the 500 error doesn't happen.
Currently the war command is broken because it uses the LegacyFileBundlerPlugin which has a hard-coded dependency on 'caplin-bootstrap'
referenced this issue
Feb 6, 2014
Latest update is as follows:
Further to this, when I drop it into tomcat webapps folder, the served js bundle when viewed via Chrome's debugger has all sorts of strange characters.
This indicates that there's an encoding issue somewhere and we need to investigate further.
There is an issue related to the war command though: If there were issues producing a bundle to go in the war, should the war command not fail rather than producing a war that is invalid?