Maven ... Failed to clean up the project: could not delete .. \ org.ow2.util.asm-asm-tree-3.1.jar

Question

I am using the STS (spring) + maven toolkit.

Every time I run my application using maven-clean , I see the following error:

 [INFO] Scanning for projects... [INFO] [INFO] ------------------------------------------------------------------------ [INFO] Building hhsystem ui 1.0.0-SNAPSHOT [INFO] ------------------------------------------------------------------------ [INFO] [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ ui --- [INFO] Deleting C:\Users\Nikolay_Tkachev\workspace\HHSystem\UI\target [INFO] ------------------------------------------------------------------------ [INFO] BUILD FAILURE [INFO] ------------------------------------------------------------------------ [INFO] Total time: 0.471s [INFO] Finished at: Mon Oct 21 12:34:33 MSK 2013 [INFO] Final Memory: 2M/90M [INFO] ------------------------------------------------------------------------ [ERROR] Failed to execute goal org.apache.maven.plugins:maven-clean-plugin:2.4.1:clean (default-clean) on project ui: Failed to clean project: Failed to delete C:\Users\Nikolay_Tkachev\workspace\HHSystem\UI\target\org.ow2.util.asm-asm-tree-3.1.jar -> [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch. [ERROR] Re-run Maven using the -X switch to enable full debug logging. [ERROR] [ERROR] For more information about the errors and possible solutions, please read the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException 

I need to close STS and go to C:\Users\Nikolay_Tkachev\workspace\HHSystem\UI\target and delete org.ow2.util.asm-asm-tree-3.1.jar

After starting STS, it works again, but it's a hassle.

Can you help me with this problem?

UPDATE
for Kalatoka L.

I run maven-clean from this state:

I see the same behavior from the command line as from the eclipse plugin

If I watch the unlock when STS starts, I see

:

Answer 1

Stop your server before starting the cleanup.

Server stop

You can stop the server from the Servers view.

To stop the server:

• In the Servers view ( Window> Show view> Other> Server> Servers> OK ), select the server you want to stop.
• Click the Stop Server icon in the toolbar. In the Servers view, the server status changes to Stopped.

• If for some reason the server cannot stop, you can complete the following:

  but. Switch to the debugging perspective.

  b. In the Process view, select the server process that you want to stop.

  from. Click Finish toolbar icon.

Note. . When the server shuts down, the server process ends and the server will not go through the usual shutdown procedure, for example, calling the destroy () method on the servlet.

Source: Eclipse Help

Answer 2

You can also try trying -Dmaven.clean.failOnError=false (from the Maven Frequently Asked Questions )

Answer 3

Delete the java.exe process in the Task Manager and run mvn clean install.It worked for me.

Answer 4

Your problem is that the running process in STS uses the files located in your target directory when executing the mvn clean command. Maven will not be able to delete these files (as other processes are still accessing them) and thus fail with this error.

Try stopping all processes (tests, servers, applications) from within STS before running Maven console commands. Look: this behavior can also occur if STS cleans up projects and, therefore, recompiles sources and does not start the process.

Answer 5

Perhaps there are many processes that use source compilation, may be a server, an old maven command, or an IDE. Of course, stop all processes, stop the server, and then run maven again. If the problem persists, you should close the java.exe process.

Hello!

Answer 6

Try disabling Project-> Build Automatically.

As Scorpio said, a process works there that blocked a file somewhere.

I have a large multi-module maven project that regularly fails in its pure form, and this resolves this for me. I turn Build Automatically on again when done.

Answer 7

Close the target folder and its file that you opened before mvn clean

Answer 8

Summary: Use an external script (batch file) that: a) stops the server and b) unlocks the .jar file before running maven-clean.

Steps:

• Bind maven-antrun-plugin: start the target in the mvn clean pre-cleaned phase. See how to do it here.

• See how to use the antrun plugin to run an external batch file on Windows here: sblundy answer to "Run an external process . " Call this file unlock_handles.bat

• Use the Sysinternals handle utility to download the link in the pre_clean.bat file to: a) stop Tomcat and b) unlock the .jar file. handle -c and handle -p .

Phew! This is a little work, but it will reliably automate the process for you, so you need to do it manually every time!

---

OK, here's an example version of unlock_handles.bat with proof of concept:

 REM "Use handle.exe to figure out the process id and handle ids, parse the output, then close the handle (again using handle.exe)" cd "C:\Users\Nikolay_Tkachev\workspace\HHSystem\UI\target" "c:/Program Files/Process Explorer/handle.exe" -p java.exe "C:\Users\Nikolay_Tkachev\workspace\HHSystem\UI\target" > handles.txt @echo "O====== Going to unlock all the below file handles! =======O" FOR /F "tokens=1-26 delims=: " %a in (handles.txt) DO @echo %h FOR /F "tokens=1-26 delims=: " %a in (handles.txt) DO handle -p %c -c %f -y 

Of course, you must change the path of the handle.exe Sysinternals file before you try.

Answer 9

I have the same problem and this

 mvn clean install -U 

bug fixed.

Answer 10

If all steps (in existing answers) do not work, just close the eclipse and close eclipse again.

Answer 11

For Linux users: a possible solution.

A build error due to the error “Failed to delete <any-file-or-folder>” will occur if there is a chance that data access, available only to the root user , is provided only by the normal -user .

Fix: enter the ll command to display a file that cannot be deleted if root access is granted for the file, change it to a regular user:

sudo chown -R username: username file_name

Later try maven clean and build.

Answer 12

I had a similar problem. I used to use Maven 3 to create a project. After switching to maven 2, I had the error above.

Solved it by switching to Maven 3.

Answer 13

I solved mine by doing:

• mvn clean
• install MVN
• mvn clean install

For some reason this worked for me. Good luck !!

Answer 14

If you block org.ow2.util.asm-asm-tree-3.1.jar and run eclipse, the log shows who could not block the file. The same code line that cannot lock the file will not release the lock.

Answer 15

In the pre-cleaning phase, I run the Maven Unlocker program. This program unlocks all files and directory for any program.

I do this with maven-antrun-plugin and only on windows systems

 <profile> <activation> <os> <family>windows</family> </os> </activation> <build> <plugins> <plugin> <artifactId>maven-antrun-plugin</artifactId> <version>1.8</version> <executions> <execution> <phase>pre-clean</phase> <configuration> <tasks> <exec dir="${project.build.directory}" executable="cmd" failonerror="false"> <arg value="Unlocker.exe" /> <arg value="/S" /> </exec> </tasks> </configuration> <goals> <goal>run</goal> </goals> </execution> </executions> </plugin> </plugins> </build> </profile> 

Answer 16

Maven complains if you do not have administrator rights in the destination folder. Check if the administrator has the right to delete this folder.

Answer 17

Delete the target file and close the code editor, then open it again, it will certainly work. This one is temporarily looking for a permanent.

Answer 18

Please close all browser tabs. And the next time you try to load the war from a place other than the destination folder.

Answer 19

If you encounter this error in an IDE such as Eclipse or IntelliJ, you may have one or more debug windows open and paused at the breakpoint. Stop them.

Answer 20

I had this problem when trying to call mvn clean install after sending a colleague an email with .jar from / target via Microsoft Outlook.

I had to close Microsoft Outlook to invoke mvn clean install .