maven... Failed to clean project: Failed to delete ..\org.ow2.util.asm-asm-tree-3.1.jar

Question

I use STS(spring tool suite) + maven plugin.

Every time when I run my application using maven-clean I see 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 have 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 again it works, but this is a hassle.

Can you help me with this problem?

UPDATE
for Kalathoki L.

I run maven-clean from this state:

STS screen shot

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

If I watch unlocker when STS is running I see

unlocker screen shot :

Make sure you stop all the process that are using same server are stopped — lakshmi, Sep 22 '16 at 20:00
TL;DR answers: 1. If you have opened any project artifact outside Eclipse, close it and re-try. 2. If that doesn't work, restart eclipse. — lupchiazoem, Feb 10 '19 at 11:26

Yubaraj · Answer 1 · 2013-10-21T10:05:00.700

69

Stop your server before you start to clean.

Stopping a server

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 that you want to stop.
Click the Stop the server icon in the toolbar. In the Servers view, the status of the server changes to Stopped.
If for some reason the server fails to stop, you can terminate the process as follows:

a. Switch to the Debug perspective.

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

c. Click the Terminate icon in the toolbar.

Note: When terminating a server, the server process will end and the server will not go through the normal routine of stopping, for example calling the destroy() method on a servlet.

Source: Eclipse Help

edited Oct 21 '13 at 10:05

answered Oct 21 '13 at 08:46

Yubaraj

3,800
7
39
57

How I can make it? I want to see more details. – Oct 21 '13 at 09:26
@user2740224 See **Stopping a server** – Yubaraj Oct 21 '13 at 10:11
my sever is stoped in eclipse when I use *maven-clean* – Oct 21 '13 at 10:37
I do not want restart my server cause it takes too much to re-start. What should I do? My friends do not need to restart it – Rafael Andrade Jul 12 '18 at 12:53
How this would be in VSCode? – Ashok kumar Ganesan Jul 17 '20 at 05:06

score 37 · Answer 2 · answered Sep 19 '14 at 06:34

37

You may also try try -Dmaven.clean.failOnError=false (from Maven FAQ)

answered Sep 19 '14 at 06:34

Bartosz Bilicki

12,599
13
71
113

6

This works but is dangerous as you might encounter unexpected behaviour while using outdated classes. – Chris311 Feb 22 '18 at 13:28
3

To make my last comment more clear: The maven build will then run through, but the target folder(s) might still be there! – Chris311 Mar 19 '18 at 15:52
Why is this in answers? – lpkej Oct 16 '19 at 14:48
2

Because someone answered the question with this answer? – Paul Brittain Jun 22 '20 at 10:24

score 31 · Answer 3 · answered Jun 14 '17 at 14:15

31

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

answered Jun 14 '17 at 14:15

Bibek Shrestha

470
5
13

1

Is there a way to do without doing this? My server needs some time to go up and I do not want that =( – Rafael Andrade Aug 01 '18 at 11:44
This worked for me. But, I'd like to know why it worked. How do you know that java.exe is the only one which has a "lock" on the jar. – MasterJoe Jul 01 '19 at 18:02
This worked for me, but isn't there a more "proper" way to stop the server? I started it from command line with mvnw... isn't there a way to stop it as well? – Svend Hansen Jul 28 '19 at 10:55
without stop can't we? – Naanii Aug 26 '21 at 06:13

score 16 · Answer 4 · answered Oct 21 '13 at 08:56

16

Your problem is that a running process within STS is using files located in your target directory while you execute a mvn clean command. Maven will be unable to delete these files (since other processes are still accessing them) and thus fail with that error.

Try to stop all processes (tests, servers, applications) from within STS before running Maven console commands. Look out: This behaviour might also appear if STS is cleaning up the projects and thus re-compiles the sources, and not running a process.

answered Oct 21 '13 at 08:56

Scorpio

2,309
1
27
45

1

Can you ask activities for fixing another than **Kalathoki L.** – gstackoverflow Oct 21 '13 at 10:44
1

How I can fix it ?** Look out: This behaviour might also appear if STS is cleaning up the projects and thus re-compiles the sources, and not running a process.** – Oct 21 '13 at 10:48
your just awesome, thats correct in my case i.e running process – user1742919 Mar 17 '17 at 12:16

score 13 · Answer 5 · answered Feb 03 '17 at 07:25

13

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

answered Feb 03 '17 at 07:25

Neha

131
1
2

5

This worked for me. I had the target folder open in a terminal, which made maven unable to clean the target folder. After `cd`-ing out of the folder, maven was able to clean again. – Idva Jul 19 '17 at 11:47
1

Yep, I had the folder open in windows explorer! – Pavel Mar 29 '18 at 14:49
2

Had folder open in windows explorer. This helped! – lpkej Oct 16 '19 at 14:55
1

I had the cmd open in the /target path – Dave Rincon Apr 25 '22 at 00:44

score 9 · Answer 6 · answered Aug 22 '16 at 15:06

9

Probably there are many processes that use sources compiled, could be a server, an old maven instruction or IDE. Sure terminate all processes, stop the server and then execute maven again. If the problem persists, you should close java.exe process.

Regards!

answered Aug 22 '16 at 15:06

Jhonatan Alarcon

339
5
13

1

Adding my two cents since It sorts of expands on this answer: It could for example be a folder synchronization process like Google Drive that's hogging your files. This was the problem in my case. Just kill the process and building will work again. – Sargon1 Oct 17 '16 at 10:24
This was my solution. I had an unexpected java.exe process running in background which was preventing maven from properly executing. – Michael Fayad Jan 15 '18 at 22:18

score 7 · Answer 7 · answered Jan 08 '16 at 12:03

Try disabling Project->Build Automatically.

As Scorpio suggested, there's a process running that's got a lock on a file somewhere.

I have a large multi-module maven project that regularly fails on clean and this resolves it for me. I re-enable Build Automatically when I'm done.

score 6 · Answer 8 · answered Jun 06 '16 at 07:36

6

I have same problem and this

mvn clean install -U

command fixed the error.

answered Jun 06 '16 at 07:36

Amir

652
9
19

1

What does -U do? – wheeleruniverse Jan 23 '19 at 04:06
@jDub9 -U Forces a check for updated releases and snapshots on remote repositories – Amir Jan 23 '19 at 09:45

score 5 · Answer 9 · edited May 23 '17 at 12:34

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

Steps:

Bind the maven-antrun-plugin:run goal to the pre-clean phase of mvn clean. See how to do this here
See how to use the antrun plugin to run an external batch file in Windows here : sblundy's answer to "Starting external process". Let's call this file unlock_handles.bat
Use the Sysinternals handle utility download link in the pre_clean.bat to a) stop the Tomcat server and b) unlock the .jar file. handle -c and handle -p would be useful here.

Whew! That's a bit of work, but it will reliably automate the process for you so that you do need to do it manually yourself each time!

OK, here's a rough, proof-of-concept version of unlock_handles.bat for you to try out:

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 have to change the path to Sysinternals' handle.exe before giving this a try.

It is will helpfull if you write more details about second item — , Oct 24 '13 at 07:36
I will try to get back with a rough version for you later today, but basically, we have to write it; it's not something that exists! (Also, unlock_files.bat is a better name for what it does; pre-clean is the context in which it is used). — vijucat, Oct 24 '13 at 08:30
I updated the answer with a unlock_handles.bat that you can run. Let me know if it works for you! Edit : parsing strings in DOS batch files is so...hacked together :-) — vijucat, Oct 24 '13 at 16:31

score 4 · Answer 10 · answered Nov 21 '17 at 04:32

4

If all steps (in existing answers) dont work , Just close eclipse and again open eclipse .

answered Nov 21 '17 at 04:32

Vijay

4,694
1
30
38

1

Your answer is the best one. – Diego Romero Jul 17 '19 at 15:55

score 3 · Answer 11 · answered May 23 '14 at 12:54

3

For linux users: possible solution.

Build error due to "Failed to delete < any-file-or-folder >" will occur if there is by chance of only delete access provided to root user rather to normal-user.

Fix : type ll command to list file that cannot be deleted, if the file is given root access, change to normal user by :

sudo chown -R user-name:user-name filename

Later try for maven clean and build.

answered May 23 '14 at 12:54

ram

2,275
3
27
38

thank you, You're save my life. cause privilege on my target folder so I can not to clear via mvn – Huỳnh Tú Jan 06 '20 at 04:00
I also had this permission issue in ubuntu. `chmod -R 777 /folder/path/here` fixed my issue. thanks – Ish Mar 30 '21 at 07:31

score 3 · Answer 12 · answered Sep 03 '20 at 08:16

3

solved by deleting the target folder manually.

answered Sep 03 '20 at 08:16

Ahmed Emad

265
2
4

score 1 · Answer 13 · answered Mar 21 '16 at 23:42

1

I had similar issue. Earlier I was using Maven 3 to build the project. After switching to maven 2 , I had the above error.

Solved it by switching to Maven 3.

answered Mar 21 '16 at 23:42

Madhu V Rao

917
1
12
24

score 1 · Answer 14 · answered May 09 '17 at 01:01

1

Maven complains if you do not have admin permissions on the target folder.Check if you have admin right to delete that folder.

answered May 09 '17 at 01:01

reshma

381
3
6

score 1 · Answer 15 · answered Feb 14 '18 at 20:14

1

I solved mine by doing:

mvn clean
mvn install
mvn clean install

For some reasons it worked for me . Good luck !!

answered Feb 14 '18 at 20:14

Boris_Ndong

247
2
4

Thanks. Running with separate commands solved this. I believe this is because the install phase of the prior module had a lock on future maven build modules which then did a clean as their first step before running install. – Freddie Nov 14 '18 at 19:23

Grim · Answer 16 · 2014-07-07T11:21:14.510

0

If you lock org.ow2.util.asm-asm-tree-3.1.jar and start eclipse, the logging shows who was unable to lock the file. The same codeline who cant lock the file will not release the lock.

edited Jul 07 '14 at 11:21

answered Jul 07 '14 at 09:51

Grim

1,938
10
56
123

Raul Villalba · Answer 17 · 2017-04-11T11:25:53.173

0

In pre-clean phase I execute with Maven Unlocker program. This program unlock all files and directory for anyone program.

I execute this with maven-antrun-plugin and only in 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>

edited Apr 11 '17 at 11:25

answered Sep 10 '15 at 11:04

Raul Villalba

11
4

1

Can you add an explanation? – Robert Sep 10 '15 at 11:10
I believe he's trying to run Unlocker windows program - http://filehippo.com/download_unlocker/tech/ . This removes any dependencies on the current execution directory. It's not a reliable or safe way to do it. – Ashok Goli Jan 20 '16 at 16:35
maven-antrun-pluign execute unlocker automatically in pre-clean maven phase. – Raul Villalba May 30 '16 at 15:45
Yes I execute unlocker program. Windows lock more files because he is Windows. Unlocker is a good utility for this problem – Raul Villalba Apr 11 '17 at 08:09

score 0 · Answer 18 · answered Jan 25 '19 at 11:42

0

Please close all the browser tab. And next time when you try to upload war from another place except target folder.

answered Jan 25 '19 at 11:42

Atul Jain

1,035
2
16
24

score 0 · Answer 19 · answered Sep 10 '19 at 16:29

0

If you run into this error in an IDE like Eclipse or IntelliJ, you may have one or more debug windows open and paused on a break-point. Terminate them.

answered Sep 10 '19 at 16:29

arcadeblast77

560
2
12

score 0 · Answer 20 · answered Mar 03 '20 at 10:04

The reason for this error is, the file which maven is trying to delete is being used by some process. One example of such process is Eclipse or any other IDE is doing validation on same project.

Please make sure that no validation running from eclipse or in any other IDE where project is open.

score 0 · Answer 21 · answered Mar 31 '21 at 19:53

0

I closed Git Bash (might be another terminal you are working on). It stops the process
Delete ...0.0.1-SNAPSHOT.jar
mvn clean install (or other start your project command; we have .sh)

answered Mar 31 '21 at 19:53

Irina Danovich

45
5

score 0 · Answer 22 · answered May 18 '21 at 14:36

If you have a process running that using the packaged app deployed like an ftp or ssh session - it could prevent the resource being deleted or moved:

so identify the open port which is using the war or jar, close it - then restart

sftp - ssh port : 22

ssh port : depend on config

score 0 · Answer 23 · answered Apr 13 '23 at 12:46

0

I solved it by opening Task Manager and killing java processes. Then mvn clean install and everything worked fine.

answered Apr 13 '23 at 12:46

Ledjon

105
8

score -1 · Answer 24 · edited Dec 30 '20 at 11:54

-1

for me

mvn install
mvn clean install

worked..

edited Dec 30 '20 at 11:54

Sergey Shcherbakov

4,534
4
40
65

answered Dec 30 '20 at 10:57

Amol Aranke

51
1
5

maven... Failed to clean project: Failed to delete ..\org.ow2.util.asm-asm-tree-3.1.jar

24 Answers24

Linked