![]() ![]() Only for it to be created again immediately by the next lifecycle phase. ![]() What the clean goal is doing is to try to delete every target folder in every module of your project. Not every “.java” file maps clearly to a pre-known output file. One could argue that in the case of java or JVM based projects this would be a tough task anyway. Or should I say it is rather “dumb” enough? Maven tends to build more than is necessary because unlike ye olde autotools it doesn’t factor in file timestamps of source and target items to reduce the workload. we need to clean, or do we?įirst things first: why do we prefix the command with clean? Well the target directory could hold outdated stuff right? Can you actually remember a case where this was relevant? Maven usually is smart enough to deal with whatever is left over in the target directory. But actually it is probably doing more than you are looking for. You see mvn clean install has been handed around for years as the goto command to “build the software”. If you’re not convinced please keep reading. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |