1. Error reporting
2. Cause
The latest artifact is not updated in the Tomcat configuration in the idea configuration.
3. Solution
1. Edit configuration
2. Click deployment to see that war is red. Click the ‘-‘ sign on the right to delete the old war package
3. Add a new artifact
4. OK.
Read More:
- Error:Cannot build artifact xxx:war exploded’ because it is included into a circular dependency
- [Solved] Artifact AServletTestCode:war exploded: Error during artifact deployment. See server log for details
- [Solved] Artifact spbjh:war exploded: Error during artifact deployment. See server log for details.
- [Solved] Tomcat Start Project Error: Artifact xxxxxx:war exploded: Error during artifact deployment. See server log
- [Solved] The war package Error: The reason why the XSD file could not be found
- [How to Solve] Java nested object @validated is not valid
- Error assembling War: webxml attribute is required
- [Fixed] Disgusting bug Error:Failed to Load project configuration: cannot parse filemessage: content is not allowed in the preface.
- Mongodb java version 3.X, prompt “XXX (an encryption algorithm) is not available” when there is a user name and password
- [Solved] BindingException: Type interface XXX is not known to the MapperRegistry
- [Solved] spring source code compile error: target package does not exist
- [Solved] IDEA plug-in jrbel hot deployment cannot be started error
- Eclipse relies on spring boot configuration processor, and there is no prompt for writing properties and YML
- [Solved] Maven Multi-Project Compile Error: The POM for xxx is invalid
- ERROR StatusLogger No Log4j 2 configuration file found. Using default configuration…
- [Solved] Mapped Statements collection does not contain value for xxx
- How to Solve Tomcat Error: Could not resolve view with name ‘xxx/xxxxxxx‘ in servlet with
- Idea create Maven project Error: [error] no longer supports source option 1.5. Please use version 1.6 or higher, and the idea reports an error: error: Java does not support the error of release version 5
- [Solved] Error running ‘ServiceStarter’: Command line is too long. Shorten command line for ServiceStarter or also for Application default configuration
- Feign Error: Load balancer does not have available server for client:XXX