Double deploy
- Dominant language
- Java
- Stars
- 3.1k
- Forks
- 935
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 17
Description
### Apache NetBeans version
Latest release
### What happened
1. Deploy Java web application to Tomcat (run from Netbeans).
2. Stop Tomcat (e.g. from Netbeans).
3. Wait (for Tomcat to fully stop).
4. Debug the app (debug project from Netbeans).
The app starts twice. Is first started with the server and then re-deployed. This causes various problems. Obviously longer startup. But also some tasks will run twice (tasks scheduled on app startup).
The app should be deployed once (remove the app before starting Tomcat and then start and deploy).
### Did this work correctly in an earlier version?
- [ ] This used to work!
### Operating System
Windows 10
### JDK
JDK 15
### Apache NetBeans packaging
Apache NetBeans provided installer
### Anything else
Note that I had this with JDK7 and Tomcat7 and the same on Tomcat9 with JDK15. The project is on Spring Boot 2.6 on Maven (older on Spring 3 something and also a Maven project). So none of that seem to be a factor.
### Are you willing to submit a pull request?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow the Apache Software Foundation's [Code of Conduct](https://www.apache.org/foundation/policies/conduct.html)
Contributor guide
Research direction
No source file, test, or entry point is named. Reproduce the sequence with NetBeans, Tomcat, and the Spring Boot project, then trace the server start and debug deployment integration. Done means the application is deployed only once after Tomcat restarts, without duplicate startup tasks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java, spring-boot
- Domain
- devtools
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100