Accepted answer

its function depends on the builders that you have in your project (they can choose to interpret clean command however they like) and whether you have auto-build turned on. if auto-build is on, invoking clean is equivalent of a clean build. first artifacts are removed, then a full build is invoked. if auto-build is off, clean will remove the artifacts and stop. you can then invoke build manually later.


i also faced the same issue with eclipse when i ran the clean build with maven, but there is a simple solution for this issue. we just need to run maven update and then build or direct run the application. i hope it will solve the problem.


there's another problem at work here. the clean functionality of eclipse is broken. if you delete files outside of eclipse it will not pick up on the fact that the files are now missing, and you'll get build errors until you delete the files manually. even then, that will not necessarily work either, especially if there are a lot of files missing. this happens to me rather often when i check out a branch of code that has had a lot of changes since the last time i built it. in that case, the only recourse i've found is to start a brand new workspace and reload the project from scratch.


it removes whatever already-compiled files are in your project so that you can do a complete fresh rebuild.

Related Query