Maven plugins can not be found in IntelliJ

Question

After updating IntelliJ from version 12 to 13, the following Maven-related plugins cannot be resolved:

org.apache.maven.plugins:maven-clean-plugin:2.4.1
org.apache.maven.plugins:maven-deploy-plugin
org.apache.maven.plugins:maven-install-plugin
org.apache.maven.plugins:maven-site-plugin

When using IntelliJ 12, these were not in the plugins list. Somehow they've been added after the update and now IntelliJ complains they cannot be found. Where can I remove these plugins from the list OR resolve the problem by installing them?

I can run maven goals clean and compile without problem, but the profile/plugins appear red with warnings in the IDE.

EDIT after 8 years: Please also have a look at all other good answers here. The accepted answer is a common solution but might not work for you or for your IDE version

Press Ctrl + Alt + S.Go to plugins. Is "Maven integration" checked? — memainjm, Dec 10 '13 at 14:02

score 473 · Accepted Answer · edited Nov 10 '20 at 03:31

473

For newer versions of IntelliJ, enable the use plugin registry option within the Maven settings as follows:

Click File Settings.
Expand Build, Execution, Deployment Build Tools Maven.
Check Use plugin registry.
Click OK or Apply.

For IntelliJ 14.0.1, open the preferences---not settings---to find the plugin registry option:

Click File Preferences.

Regardless of version, also invalidate the caches:

Click File Invalidate Caches / Restart.
Click Invalidate and Restart.

When IntelliJ starts again the problem should be vanquished.

edited Nov 10 '20 at 03:31

Dave Jarvis

30,436
41
178
315

answered Nov 27 '14 at 10:49

GarfieldKlon

11,170
7
31
33

22

For Mac users, you can find it under Preferences. (Click on IntelliJ IDEA on the menu bar-> Preferences) or (Command⌘+,) ->(Same as above)Build, Execution, Deployment -> Build Tools -> Maven. – Ayush Chaurasia Sep 27 '20 at 08:55
I'm using version 20.x.x. This didn't work for me. Could it be another problem? – manikanta nvsr Dec 03 '20 at 08:16
1

@manikanta nvsr:Could you check that 1) that 'Use plugin registry' is activated? 2) Within your Maven local repo that the dep is there but not really downloaded? In this case remove the directory and synch again (button on the right). It solved the problem for me. – Rudy Vissers Jan 07 '21 at 05:30
3

using Invalidate and Restart, works for me. Am using IntellIj 2020.03. – Ornelio Chauque Mar 04 '21 at 06:45
20

Does anyone know why this isn't a default in Intellij? This should be enabled by default. – Mugen Apr 19 '21 at 11:10
I was also wondering why they haven't enabled it by default. – Celdor Jun 17 '21 at 10:44
27

Not solving the issue – Rahul Aug 28 '21 at 18:15
15

did not solve the issue for me in 2022.1 – gdogra Feb 12 '22 at 13:14
2 years later, and your answer still useful, Thank you so much, I have been looking for a solution for the last 2 days. – Abdelrahman Nassar Feb 17 '22 at 06:22
1

This is how it can be solved in 2022.1 IntelliJ version: https://stackoverflow.com/questions/64639836/plugin-org-springframework-bootspring-boot-maven-plugin-not-found – pyfyc Sep 29 '22 at 11:55
not solving the issue for IntelliJ IDEA 2022.2 (Community Edition) – Paulius Nyoumi Oct 25 '22 at 22:14
Solved the problem, thanks: `IntelliJ IDEA 2022.1.2 (Community Edition)` `Build #IC-221.5787.30, built on May 31, 2022` – Makc Jun 02 '23 at 14:00

score 86 · Answer 2 · edited Feb 04 '20 at 16:15

86

I had this problem for years with the maven-deploy plugin, and the error showed up even though I was not directly including the plugin in my POM. As a work-around I had to force include the plugin with a version into my POMs plugin section just to remove the red-squiggly.

After trying every solution on Stack Overflow, I found the problem: Looking into my .m2/repository/org/apache/maven/plugins/maven-deploy-plugin directory there was a version 'X.Y' along with '2.8.2' et al. So I deleted the entire maven-deploy-plugin directory, and then re-imported my Maven project.

So it seems the issue is an IntelliJ bug in parsing the repository. I would not not remove the entire repository though, just the plugins that report an error.

edited Feb 04 '20 at 16:15

anothernode

5,100
13
43
62

answered Jul 03 '17 at 11:00

Steven Spungin

27,002
5
88
78

9

Nice. I had a few of these due to IntelliJ battling my company's proxy server. Finally blew them out. Thanks! – paultamalunas Oct 26 '17 at 23:12
"update maven indices" (under ctrl + enter) after that – Line Sep 03 '19 at 12:36
1

I didn't have the issue of the local repository being corrupted. But adding the version did it. – fan Nov 18 '19 at 17:17
Where is that directory? – Human programmer Sep 06 '20 at 21:50
Found it (Windows 10): "C:\Users\your_user\.m2\repository\org\apache\maven\plugins\maven-site-plugin\". I had only 1 file inside another directory there. I removed folder, IntelliJ redownloaded it, but then there were couple files, including .jar. Before that I had 2 to 5 errors in IntelliJ, after that I have only 1. The same as before with that folder. – Human programmer Sep 06 '20 at 22:13
Replying to @fan: "I didn't have the issue of the local repository being corrupted" - it doesn't need to be corrupted, just if there is a newer version, the old one can't be override and that's the reason it's not updated. – Shai Alon Jun 27 '21 at 11:29
This also worked for me, thanks. – Artyom Chernetsov Nov 11 '21 at 00:33
This issues fixed it for me. For me it was org/apache/maven/plugins/maven-jar-plugin – Ammar Dec 17 '21 at 05:05
This worked for me as well :+1 – el_chupacabra Aug 12 '22 at 19:30
This gave me an insight. I just completely deleted everything under `/repository` and made IntelliJ do its thing again. No error so far – Guilherme Taffarel Bergamin May 16 '23 at 12:21
It works nice a charm – thegiau.pham Jun 13 '23 at 07:11

score 78 · Answer 3 · answered Dec 10 '13 at 16:16

78

Run a Force re-import from the maven tool window. If that does not work, Invalidate your caches (File > Invalidate caches) and restart. Wait for IDEA to re-index the project.

answered Dec 10 '13 at 16:16

Javaru

30,412
11
93
70

For my colleague, force re-import worked when plugins had not been shown in the right maven panel. – mirelon Mar 11 '14 at 10:44
it worked for me. It seems it was using an outdated settings.xml – Antón R. Yuste Aug 16 '19 at 08:06
How do you do a force reimport in IntelliJ? – qwerty Dec 27 '20 at 23:06
6

@a-p From the Maven tool window, click the "Reload all Maven Projects" button (it's the left most button and looks like two arrows in a circle, much like most refresh icons.) It use to be labeled "Re-import..." rather than "Reload...", hence why in my above answer I said "re-import". They changed the nomenclature used a few years ago. – Javaru Jan 02 '21 at 17:29

score 62 · Answer 4 · edited Dec 11 '20 at 09:19

62

None of the other answers worked for me. The solution that worked for me was to download the missing artifact manually via cmd:

mvn dependency:get -DrepoUrl=http://repo.maven.apache.org/maven2/ -Dartifact=ro.isdc.wro4j:wro4j-maven-plugin:1.8.0

After this change need to let know the Idea about new available artifacts. This can be done in "Settings > Maven > Repositories", select there your "Local" and simply click "Update".

Edit: the -DrepoUrl seems to be deprecated. -DremoteRepositories should be used instead. Source: Apache Maven Dependency Plugin – dependency:get.

edited Dec 11 '20 at 09:19

Logan Farci

5
1
2

answered Oct 28 '16 at 15:39

Eng.Fouad

115,165
71
313
417

1

So even after I deleted \.m2\repository\, I was finding that my \.m2\repository\com\whatever\thing\my-plugin\1.2.3 was only "partially' being populated. I deleted the 1.2.3 directory and did what you say here, and then it looked correct populated. I think this is the "nail" solution vs the hammer solution of deleting \.m2\repository thanks. – granadaCoder Jun 16 '20 at 21:38
3

I tried everything else in this thread, only this one resolved the issue in my case. – Vincent Jun 26 '20 at 09:43
2

I think that this should be the right answer, probably it's the main cause when plugins are not found. Apparently plugin dependencies are not downloaded until the associated profile is enabled (I looked into the maven repository and plugins marked in red where missing). I would try this before to delete the whole m2 repository (it can take some time to re-download). – funder7 Oct 15 '20 at 19:09
1

I tried many solutions and this was the only one that worked for me. Thanks! – cbmeeks Jul 16 '21 at 17:17
1

This one worked for me loading a project that was built using an older version of IntelliJ. Thanks a bunch! – seanquijote Jan 05 '22 at 03:47
1

Thank you. I had (and hated) that problem for months.. – Danny Mar 08 '22 at 16:51
1

still accurate with IntelliJ CE 2022.1. I already had the jar in my local repo so updating the local repo fixed it. Thx – Antoine Wils Nov 14 '22 at 09:35

score 44 · Answer 5 · answered Sep 25 '17 at 15:56

44

The red with warnings maven-site-plugin resolved after the build site Lifecycle:

My IntelliJ version is Community 2017.2.4

answered Sep 25 '17 at 15:56

Wendel

2,809
29
28

1

This downloaded all my missing maven plugins. Thanks for the tip. – Gibado Mar 13 '19 at 14:56
Same for the clean, compile, install, but NOT deploy lifecycles, for which I get the following error `Deployment failed: repository element was not specified in the POM inside distributionManagement element or in -DaltDeploymentRepository=id::layout::url parameter` – andreagalle Mar 03 '22 at 07:54
Thank you! It worked for Community 2021.3.2 – Yonshoku Mar 17 '22 at 16:00

Randhir Ray · Answer 6 · 2019-09-20T15:25:07.947

38

SOLVED !!!

This is how I fixed the issue...

Tried one of the answers which include 'could solve it by enabling "use plugin registry" '. Did enable that but no luck.
Tried again one of the answers in the thread which says 'If that does not work, Invalidate your caches (File > Invalidate caches) and restart.' Did that but again no luck.
Tried These options .. Go to Settings --> Maven --> Importing and made sure the following was selected

Import Maven projects automatically

Create IDEA modules for aggregator projects Keep source...

Exclude build dir...

Use Maven output...

Generated souces folders: "detect automatically"

Phase to be...: "process-resources"

Automatically download: "sources" & "documentation"

Use Maven3 to import

project VM options for importer: -Xmx512m

But again no success.
1. Now lets say I had 10 such plugins which didn't get resolve and among them the first was 'org.apache.maven.plugins:maven-site-plugin' I went to '.m2/repository/org/apache/maven/plugins/' and deleted the directory 'maven-site-plugin' and did a maven reimport again. Guess what, particular missing plugin got dowloaded. And I just followed similar steps for other missing plugins and all got resolved.

edited Sep 20 '19 at 15:25

answered Sep 20 '19 at 07:14

Randhir Ray

540
5
14

And on Windows 10 that directory is here: "C:\Users\your_user\.m2\repository\org\apache\maven\plugins\maven-site-plugin\". I had only 1 file inside another directory there. I removed folder, IntelliJ redownloaded it, but then there were couple files, including .jar. Before that I had 2 to 5 errors in IntelliJ, after that I have only 1. The same as before with that folder. – Human programmer Sep 06 '20 at 22:12
4th one is an effective solution.. I think deleting repo finally works in any maven conflict case :) – ankit.vishen Mar 15 '21 at 11:11
In short, delete the folder for the offending dependency from inside repository (.m2/repository/path/to/offending/dependency) – Sнаđошƒаӽ Sep 23 '21 at 14:22
Deleting folders of missing plugins is the only solution that worked for me. – kumar May 18 '22 at 09:00
This is the only really working solution – Luke May 27 '23 at 13:42
no idea how this works, but it does. I tried deleting the whole .m2 and reimporting everything but even that doesnt work, but deleting the plugin part works? – experiment unit 1998X Jun 09 '23 at 06:53

score 28 · Answer 7 · answered Feb 09 '17 at 05:06

28

I had the same issue. I added the plugins into my pom.xml dependencies and it works for me.

    <dependency>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-site-plugin</artifactId>
        <version>3.3</version>
        <type>maven-plugin</type>
    </dependency>

    <dependency>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-install-plugin</artifactId>
        <version>2.4</version>
        <type>maven-plugin</type>
    </dependency>

    <dependency>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-deploy-plugin</artifactId>
        <version>2.7</version>
        <type>maven-plugin</type>
    </dependency>

answered Feb 09 '17 at 05:06

olivejp

900
1
9
14

5

It's worth mentioning that I tried all the 'above' answers before finally caving and adding the declaration directly in my projects pom.xml This is a less-than-optimal solution because we have to add the maven plugins to each new project. Edit: I took this one step further and now REMOVED the declaration. Now the inspection error is gone... – blackstrype Nov 27 '20 at 17:40
3

Helped me. I added the repository once, removed it and then it works well. – Mindaugas Bernatavičius Jan 09 '21 at 19:49

score 21 · Answer 8 · answered Aug 29 '20 at 18:27

21

I tried the other answers, but none of them solved this problem for me.

The problem disappeared when I explicitly added the groupId like this:

<plugins>
    <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-clean-plugin</artifactId>
        <version>3.1.0</version>
    </plugin>
</plugins>

Once the color of the version number changed from red to black and the problem disappeared from the Problems tab the groupId can be removed again from the problematic plugin, the error does not show up again and the version number even shows up as suggestion for version.

answered Aug 29 '20 at 18:27

Johannes

828
12
29

3

This is exactly what worked for me. What remains unexplained, however, is what is the cause of this bizarre behaviour, especially considering that `org.apache.maven.plugins` is the [default value](https://maven.apache.org/ref/3.6.3/maven-model/maven.html#class_plugin) of `groupId`? – Marchyello Jan 05 '21 at 13:31
@Marchyello the most likely reason is the bug in IntelliJ maven plugin. It just expects that each plugin has a groupId, when it is completly fine to omit one for maven own plugins. – blekione Jan 19 '22 at 15:58

score 13 · Answer 9 · answered Nov 14 '18 at 10:04

13

I am using IntelliJ Ultimate 2018.2.6 and found out, that the feature Reimport All Maven Project does not use the JDK, which is set in the Settings: Build, Execution, Deployment | Build Tools | Maven | Runner. Instead it uses it's own JRE in IntelliJ_HOME/jre64/ by default. You can configure the JDK for the Importer in Build, Execution, Deployment | Build Tools | Maven | Importing.

In my specific problem, an SSL certificate was missing in the JREs keystore. Unfortunately IDEA only logs this issue in it's own logfile. A little red box to inform about the RuntimeException had been really nice...

answered Nov 14 '18 at 10:04

Nils

476
3
4

1

Thanks for the tip! Did the above, then deleted the problematic plugin directories, then Reimport and voila! – Vlad Aug 12 '19 at 14:26
This worked for me. I also did the comment given by @Vlad. Upvoted both answer and comment. Intellij Version 2019.2 installed after formatting the machine. – Raghu Nov 25 '19 at 16:43
Thanks a lot. This worked for me after struggling for 1 day. – Gauranga Rathod Mar 16 '21 at 09:35
To update the cacerts file did it for me (using an own nexus with own SSL certificate). The cacerts file has a default password of "changeit". https://intellij-support.jetbrains.com/hc/en-us/community/posts/206153629-How-to-add-a-SSL-root-certificate-to-IDEA-on-OS-X-. You import the own crt file with: keytool.exe -import -alias mynexus -keystore \cacerts -file \dataic.crt – Andreas May 03 '21 at 18:06

score 11 · Answer 10 · answered Mar 12 '14 at 10:14

I had the same error and was able to get rid of it by deleting my old Maven settings file. Then I updated the Maven plugins manually using the mvn command:

mv ~/.m2/settings.xml ~/.m2/settings.xml.old
mvn -up

Finally I ran the "Reimport All Maven Projects" button in the Maven Project tab in IntelliJ. The errors vanished in my case.

score 9 · Answer 11 · edited Dec 26 '21 at 14:36

9

None of the other solutions worked for me.

My solution:

Maven Settings -> Repositories -> select Local Repository in the list, Update

Worked like a charm!

edited Dec 26 '21 at 14:36

cigien

57,834
11
73
112

answered Dec 26 '21 at 14:24

Tamás Bárász

352
3
6

1

In my case, I had to update the cloud maven repository index as well in the same page. On my mac the navigation was: Preferences > Maven > Repositories > select required Repository > click on Update > Apply. – Renju Jose Mar 20 '22 at 07:30

score 8 · Answer 12 · answered Aug 28 '14 at 03:03

8

This did the trick for me...delete all folders and files under 'C:\Users[Windows User Account].m2\repository'.

Finally ran 'Reimport All Maven Projects' in the Maven Project tab in IntelliJ.

answered Aug 28 '14 at 03:03

Brandon Oakley

310
4
6

score 7 · Answer 13 · edited Nov 06 '19 at 14:05

7

Remove your local Maven unknown plugin and reimport all maven projects. This will fix this issue.

You can find it under View > Tool Windows > Maven :

edited Nov 06 '19 at 14:05

DependencyHell

1,027
15
22

answered Jul 12 '18 at 01:13

Xin Cai

161
3
5

score 7 · Answer 14 · answered Aug 21 '20 at 09:22

For me it was as simple as giving the plugin a version:

<version>3.3.0</version>

The full plugin code sample is given below:

<build>
<plugins>
  <plugin>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-assembly-plugin</artifactId>
    <version>3.3.0</version>
    <executions>
      <execution>
        <phase>package</phase>
        <goals>
          <goal>single</goal>
        </goals>
        <configuration>
          <archive>
            <manifest>
              <mainClass>Main</mainClass>
            </manifest>
          </archive>
          <descriptorRefs>
            <descriptorRef>jar-with-dependencies</descriptorRef>
          </descriptorRefs>
        </configuration>
      </execution>
    </executions>
  </plugin>

Before the version you must force to download the correct version. Then it perfectly run. — mcolak, Apr 10 '21 at 11:05

score 5 · Answer 15 · answered Mar 09 '17 at 11:51

5

I was recently faced with the same issue. None of the other solutions resolved the red error lines.

What I did was run the actual targets in question (deploy, site). I could see those dependencies then being fetched.

After that, a reimport did the trick.

answered Mar 09 '17 at 11:51

Denham Coote

634
8
18

Seems like intellij didnt auto download these plugins without actually runing the maven goal. Kind of makes sense:-) Worked for me even if the actual site and deploy goals did fail :-) – Marti Nito Nov 17 '17 at 12:42

score 5 · Answer 16 · edited Jul 28 '22 at 08:29

If an artifact is not resolvable. Go in the directory of your .m2/repository and check that you DON'T have that kind of file :

build-helper-maven-plugin-1.10.pom.lastUpdated

If you don't have any artefact in the folder, just delete it, and try again to re-import in IntelliJ.

the content of those files is like :

#NOTE: This is an Another internal implementation file, its format can be changed without prior notice.
#Fri Mar 10 10:36:12 CET 2017
@default-central-https\://repo.maven.apache.org/maven2/.lastUpdated=1489138572430
https\://repo.maven.apache.org/maven2/.error=Could not transfer artifact org.codehaus.mojo\:build-helper-maven-plugin\:pom\:1.10 from/to central (https\://repo.maven.apache.org/maven2)\: connect timed out

Without the *.lastUpdated file, IntelliJ (or Eclipse by the way) is enabled to reload what is missing.

Thx! this finally did the trick for me so you guys could try to cd ~/.m2/repository && find . -type f -name '*lastUpdated' | xargs rm — pocketrocket, Mar 25 '21 at 16:32

score 5 · Answer 17 · answered Mar 31 '21 at 03:04

5

This worked for me

Go to Settings --> Maven --> Importing --> JDK for importer --> use "Use Project JDK" option instead of a custom JDK set previously.
Re-build/re-import all the dependencies.

answered Mar 31 '21 at 03:04

mohit jain

77
1
4

score 4 · Answer 18 · answered May 04 '15 at 13:40

4

I could solve this problem by changing "Maven home directory" from "Bundled (Maven 3) to "/usr/local/Cellar/maven/3.2.5/libexec" in the maven settings of IntelliJ (14.1.2).

answered May 04 '15 at 13:40

MathiasJ

1,661
1
14
20

score 4 · Answer 19 · answered Nov 04 '15 at 06:48

4

Uncheck the "Work offline" checkbox in Maven settings.

answered Nov 04 '15 at 06:48

Maheshkumar

724
1
10
19

score 4 · Answer 20 · answered Aug 07 '19 at 14:06

Here is what I tried to fix the issue and it worked:

Manually deleted the existing plugin from the .m2 repo
Enabled "use plugin registry" in IntelliJ
Invalidated the cache and restarted IntelliJ
Reimported the maven project in IntelliJ

After following above steps, the issue was fixed. Hopefully this helps you as well.

score 4 · Answer 21 · answered Feb 26 '20 at 13:00

For me which worked is putting the repository which contained the plugin under pluginRepository tags. Example,

<pluginRepositories>
    <pluginRepository>
        <id>pcentral</id>
        <name>pcentral</name>
        <url>https://repo1.maven.org/maven2</url>
    </pluginRepository>
</pluginRepositories>

score 4 · Answer 22 · answered Jul 18 '20 at 05:20

4

Enabling "use plugin registry" and Restart project after invalidate cash solved my problem

to Enabling "use plugin registry" >>> (intelij) File > Setting > Maven > enable the option from the option list of maven

To invalidate cash >>> file > invalidate cash

That's it...

answered Jul 18 '20 at 05:20

DalusC

391
1
12

Worked for me. Thanks. Could you please explain what it actually does? – NIKHIL CHAURASIA Jul 25 '20 at 19:44
@NIKHILCHAURASIA The Maven Clean Plugin, attempts to clean the files and directories generated by Maven during its build. While there are plugins that generate additional files, the Clean Plugin assumes that these files are generated inside the target directory. When considering about maven-deploy-plugin deploying means not only copying the artifacts but making sure all this information is correctly updated. But if these files override with cashed files, it may course errors – DalusC Jul 27 '20 at 09:02
@NIKHILCHAURASIA When executing Maven, it'll first look in this local cache for artifacts. If the artifact cannot be found here, Maven will access the remote repositories to find the artifact. Once found it will be stored into the local repository, so it's available for current and future usage. – DalusC Jul 27 '20 at 09:02

score 3 · Answer 23 · answered Jan 24 '19 at 09:16

This worked for me:

Close IDEA
Delete "*.iml" and ".idea" -directories(present in the root folder of project)
Run "mvn clean install" from the command-line
Re-import your project into IDEA

After re-importing the entire project, installation of dependencies will start which will take some minutes to complete depending upon your internet connection.

Dmitriy Popov · Answer 24 · 2020-11-06T10:14:15.783

My case:

maven-javadoc-plugin with version 3.2.0 is displayed red in IntelliJ.
Plugin is present in my local maven repo.
Re-imported maven million times.
Ran mvn clean install from the command line N times.
All my maven settings in IntelliJ are correct.
Tried to switch between Bundled and non-bundled Maven.
Tried do delete the whole maven repo and to delete only the plugin from it.
Nothing of the above worked.
The only thing that almost always helps with modern IntelliJ IDEA versions is "Invalidate caches / Restart". It helped this time as well. maven-javadoc-plugin is not red anymore, and I can click on it and to to the source pom file of the plugin.

score 3 · Answer 25 · answered Nov 07 '20 at 17:50

3

Recently I faced the same issue. All tips doesn't work in my cause.

But I fix it.

Go to Intellij idea setting, find Maven, and in it you need to open Repository tab and update maven and local repos. That's all.

answered Nov 07 '20 at 17:50

Roman Egorov

31
2

score 2 · Answer 26 · answered Oct 02 '14 at 17:47

2

If you have red squiggles underneath the project in the Maven plugin, try clicking the "Reimport All Maven Projects" button (looks like a refresh symbol).

Reimport all Maven Projects

answered Oct 02 '14 at 17:47

satoukum

1,188
1
21
31

score 2 · Answer 27 · answered May 14 '19 at 16:02

You can add them as dependencies:

<dependencies>
    <dependency>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-clean-plugin</artifactId>
        <version>2.4.1</version>
    </dependency>
</dependencies>

Intellij will resolve them. After successfull import dependencies, you can clean them.

score 2 · Answer 28 · answered May 27 '20 at 06:34

Check the plugins which cannot be found (maven-site-plugin,maven-resources-plugin)
go to '.m2/repository/org/apache/maven/plugins/'
delete the directory rm -rf plugin-directory-name (eg: rm -rf maven-site-plugin)
exit project from intellij
import project again
Do a Maven reimport

Explanation: when you do a maven reimport, it will download all the missing plugins again.

Happy Coding

score 2 · Answer 29 · answered May 29 '21 at 21:54

I use the community edition packaged as snap on Ubuntu 18.04.

I experience that issue each time there a IntelliJ release.

In that scenario, my working solution is to invoke the invalidate cache and restart from the file menù flagging the indexes removal too.

score 2 · Answer 30 · edited Aug 23 '22 at 05:02

June/2021:

No Delete, No Reimport.

What I did is, I was going to :

C:\Users\dell\.m2\repository\org\apache\maven\plugins

Then double Click on every Plugin Folders, And see what version it is downloaded.

Then I came back to pom file, and according to downloaded version, I carefully changes those versions in <version>....</version> Tags. Then refresh.

And That way, All red marks are gone, Even gone those Yellow Marks.

All Clean.

Here is my full pom file for further notice. The Project is JavaFx+Maven with Shade :

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0"
         xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
    <modelVersion>4.0.0</modelVersion>

    <groupId>main.java.sample</groupId>
    <artifactId>ThreeColumnTable</artifactId>
    <version>1.0-SNAPSHOT</version>

    <properties>
        <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
        <maven.compiler.source>11</maven.compiler.source>
        <maven.compiler.target>11</maven.compiler.target>
    </properties>
    <dependencies>
        <dependency>
            <groupId>org.openjfx</groupId>
            <artifactId>javafx-controls</artifactId>
            <version>15.0.1</version>
        </dependency>
        <dependency>
            <groupId>org.openjfx</groupId>
            <artifactId>javafx-fxml</artifactId>
            <version>15.0.1</version>
        </dependency>
        <dependency>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-install-plugin</artifactId>
            <version>2.4</version>
            <type>maven-plugin</type>
        </dependency>

        <dependency>
            <groupId>org.apache.maven.plugins</groupId>
            <artifactId>maven-deploy-plugin</artifactId>
            <version>2.7</version>
            <type>maven-plugin</type>
        </dependency>
    </dependencies>
    <build>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-compiler-plugin</artifactId>
                <version>3.8.0</version>
                <configuration>
                    <source>11</source>
                    <target>11</target>
                    <release>11</release>
                </configuration>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-resources-plugin</artifactId>
                <version>2.6</version>
                <executions>
                    <execution>
                        <phase>test</phase>
                        <goals>
                            <goal>resources</goal>
                            <goal>testResources</goal>
                        </goals>
                    </execution>
                </executions>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-project-info-reports-plugin</artifactId>
                <version>3.1.2</version>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-clean-plugin</artifactId>
                <version>3.1.0</version>
                <configuration>
                    <filesets>
                        <fileset>
                            <directory>src/main/generated-groovy-stubs</directory>
                        </fileset>
                    </filesets>
                </configuration>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-jar-plugin</artifactId>
                <version>2.4</version>
                <configuration>
                    <archive>
                        <manifest>
                            <mainClass>org.example.App</mainClass>
                            <manifestFile>src/main/resources/META-INF/MANIFEST.MF</manifestFile>
                        </manifest>
                    </archive>
                </configuration>
            </plugin>
            <plugin>
                <groupId>org.openjfx</groupId>
                <artifactId>javafx-maven-plugin</artifactId>
                <version>0.0.1</version>
                <configuration>
                    <mainClass>org.example.App</mainClass>
                </configuration>
            </plugin>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-shade-plugin</artifactId>
                <version>3.2.4</version>
                <executions>
                    <execution>
                        <goals>
                            <goal>shade</goal>
                        </goals>
                        <configuration>
                            <shadedArtifactAttached>true</shadedArtifactAttached>
                            <shadedClassifierName>project-classifier</shadedClassifierName>
                            <transformers>
                                <transformer implementation=
                                                     "org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
                                    <mainClass>org.example.Main</mainClass>
                                </transformer>
                            </transformers>

                        </configuration>
                    </execution>
                </executions>
            </plugin>
        </plugins>
    </build>
</project>

But why does it happen? What's the reason, shouldn't the plugins only be downloaded in the respected versions? — Danon, Jul 07 '21 at 12:26
Generally people don't provide version and may be defaulted version is not the one that is existing. Another reason is wrong plugin version mentioned in the pom so that will not be found either. The key @Noor Hossain has mentioned is provide the right version and it should work. — prash, Aug 18 '21 at 23:56

score 1 · Answer 31 · answered Sep 21 '16 at 08:58

1

Goto IntelliJ -> Preferences -> Plugin

Search for maven, you will see 1. Maven Integration 2. Maven Integration Extension.

Select the Maven Integration option and restart your Intellij

answered Sep 21 '16 at 08:58

Anil

595
1
5
15

score 1 · Answer 32 · answered Nov 29 '19 at 15:25

For me, I download them manually and put theme in my .m2 folder then i did invalidate cache and restart (I m using Intellij IDEA). The steps are for example:

<groupId>org.codehaus.mojo</groupId>
              <artifactId>jdepend-maven-plugin</artifactId>
<version>2.0</version>

I go to https://mvnrepository.com/ then serch for jdepend-maven-plugin choose the version 2.0
In Files go and click on View All
Download this files jdepend-maven-plugin-2.0.jar jdepend-maven-plugin-2.0.jar.sh1 jdepend-maven-plugin-2.0.pom jdepend-maven-plugin-2.0.pom.sh1
go to .m2 folder then org/codehaus/mojo Create folder with name jdepend-maven-plugin inside with name 2.0 inside put the 4 files downloaded befor.
create file with name _remote.repositories open it with text editor and write inside

jdepend-maven-plugin-2.0.jar>central=
jdepend-maven-plugin-2.0.pom>central=

go to intellij IDEA invalidate cache and restart.

Eyal Sooliman · Answer 33 · 2021-03-09T09:33:14.923

1

I had the same problem, After checking the pom.xml file, found out that I have duplicated plugins for the surefire. After deleting and leaving only 1 inside the pom.xml - issue resolved.

Also maven-surefire-report-plugin == LATEST and

     <dependency>
        <groupId>org.testng</groupId>
        <artifactId>testng</artifactId>
        <version>6.9.8</version>
    </dependency>

edited Mar 09 '21 at 09:33

answered Mar 04 '20 at 14:34

Eyal Sooliman

1,876
23
29

score 1 · Answer 34 · answered Mar 18 '20 at 23:52

1

For me the Plugins were related to a Profile. I have to enable the relevant profile via Maven (right sidebar menu), Profiles and let the dependencies download.

answered Mar 18 '20 at 23:52

Steve Macleod

45
1
9

score 1 · Answer 35 · answered Jul 23 '20 at 11:51

Tried invalidating cache, reimporting the project, removing .m2 folder partially and as a whole, and switching to the Idea bundled Maven. Nothing worked, and I've finally broken Maven completely: when it would build the project in the console, now it stopped. Had to reinstall Maven, and it helped!

score 1 · Answer 36 · edited Oct 11 '20 at 07:34

1

Try to put the following code in your pom.xml. If this does not work, try to change the <version>2.8.2</version> (diferent versions can be found in the maven repo.)

<build>
    <pluginManagement>
        <plugins>
            <plugin>
                <groupId>org.apache.maven.plugins</groupId>
                <artifactId>maven-deploy-plugin</artifactId>
                <version>2.8.2</version>
            </plugin>
        </plugins>
    </pluginManagement>
</build>

edited Oct 11 '20 at 07:34

David Buck

3,752
35
31
35

answered Oct 10 '20 at 18:01

Leotrim Vojvoda

11
1

This solved it for me as well. Needed to specify the groupId and the version. – TJA Mar 07 '23 at 19:07

score 1 · Answer 37 · edited Jul 28 '23 at 10:25

1

I just delete all my maven plugins stored in .m2\repository\org\apache\maven\plugins, and IntelliJ downloaded all the plugins again a it solve my problem and it worked fine for me!!!

edited Jul 28 '23 at 10:25

banan3'14

3,810
3
24
47

answered Dec 16 '20 at 23:50

SJ Cam

21
1

I've been trying several options but this is the one that worked for me. But maybe it's because another steps I made that affected too. – dmance May 31 '21 at 09:39

score 1 · Answer 38 · edited Oct 18 '22 at 06:30

1

Deleted all folders from below and did the "Reload All Maven Projects" refresh button and it worked for me.

C:\Users\<username>\.m2\repository\org\apache\maven\plugins

edited Oct 18 '22 at 06:30

Procrastinator

2,526
30
27
36

answered Oct 12 '22 at 19:14

sankar

189
1
10

score 0 · Answer 39 · answered Mar 31 '16 at 14:42

0

In my case, there were two slightly different dependences (version 2.1 vs 2.0) in two maven sub-modules. After I switched to a single version the error has gone in IDEA 14. (Refresh and .m2 swipe didn't help.)

answered Mar 31 '16 at 14:42

Pavel Vlasov

4,206
6
41
54

score 0 · Answer 40 · answered Aug 25 '17 at 13:19

0

I have change the Maven home directory from Bundled(Maven 3) to Bundled(Maven 2) in the maven setting. And this works for me. Have a try!

answered Aug 25 '17 at 13:19

Culbert

1

score 0 · Answer 41 · answered Oct 03 '18 at 08:35

0

"IntelliJ IDEA and Maven - "Unresolved Plugin" Solutions" - in particular, deleting the plugin-folder - then reimporting all maven plugins after ide restart - worked for me.

answered Oct 03 '18 at 08:35

womd

3,077
26
20

score 0 · Answer 42 · answered Dec 11 '18 at 13:00

0

this might help someone down the line

i faced similar issues, my system was not able to resolve the proxy server
so connected to the local wifi hotpsot.

answered Dec 11 '18 at 13:00

Abhishek D K

2,257
20
28

Prashant · Answer 43 · 2019-05-29T10:19:40.510

For me, there was a mistake in the settings.xml. I was using http:// in the url due to which it wasn't working. Once i removed it the plugins were downloaded successfully.

<proxy>
   <id>optional</id>
   <active>true</active>
   <protocol>http</protocol>
   <host>www-proxy.xxxx.com</host>
   <port>80</port>
  <!-- <nonProxyHosts>local.net</nonProxyHosts>-->
  </proxy>

  <!-- Proxy for HTTPS -->
  <proxy>
   <id>optional1</id>
   <active>true</active>
   <protocol>https</protocol>
   <host>www-proxy.xxxx.com</host>
   <port>80</port>
   <!--<nonProxyHosts>local.net</nonProxyHosts>-->
  </proxy>

score 0 · Answer 44 · edited Jul 28 '23 at 10:27

If problem persist, you can add manually the missing plugins files.

For example if maven-site-plugins is missing, go to https://mvnrepository.com/artifact/org.apache.maven.plugins/maven-site-plugin

Choice your version, and download files associated directly into your .m2 folder, in this example : C:\Users\ {USERNAME} \.m2\repository\org\apache\maven\plugins\maven-site-plugin\ {VERSION}

In IntelliJ IDEA, open Maven sidebar, and reload (tooltip : Reimport All Maven projects)

score 0 · Answer 45 · answered Oct 20 '20 at 18:28

0

In my case, I tried most of the answers above. I solve this problem by:

Cleaning all items in the .m2/repository folder
Uninstall Intellij Ultimate Version
Install Community Version

It so amazingly worked!

answered Oct 20 '20 at 18:28

WildSaoFeng

17
3

score 0 · Answer 46 · answered May 05 '21 at 16:20

None of these solutions worked for me. After a painful few hours, it turned out that the issue was caused by the way I imported the project.

Context: importing freshly generated Spring Initializr project with Web & Kafka dependencies.

Issue: plugin dependency was "Not found" and IntelliJ couldn't compile the app, even though mvn clean compile ran fine on the console.

The bad way: Importing it using the "New > Project from Existing Sources..." option.

The good way: Importing it using the "Open..." option.

Solution to go from the bad to the good: remove the project, delete and re-clone the repo from version control to make sure all gitignored IntelliJ files are removed, and import it into IntelliJ with the "Open..." option.

novice151 · Answer 47 · 2022-06-15T13:53:11.263

You must add the dependency

This question is old, but I hope my answer will help those who find it

Reference [link] https://mvnrepository.com/artifact/org.apache.maven.plugins/maven-dependency-plugin/3.1.1

<!-- https://mvnrepository.com/artifact/org.apache.maven.plugins/maven-dependency-plugin -->
<dependency>
    <groupId>org.apache.maven.plugins</groupId>
    <artifactId>maven-dependency-plugin</artifactId>
    <version>3.1.1</version>
</dependency>

score 0 · Answer 48 · answered Nov 18 '22 at 08:16

I put the dependency in dependencies, and solved my problem:

<dependencies>
    <dependency>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-project-info-reports-plugin</artifactId>
        <version>3.0.0</version>
    </dependency>
</dependencies>

I neglected the <pluginManagement>, it's as <dependencyManagement> which is different from <dependencies>:

dependencyManagement only declares dependencies, it does not introduce them.

So whether I clean all items in my repository folder or type mvn clean install -e -U, both don't work.

score 0 · Answer 49 · answered Dec 23 '22 at 11:58

If you already tried to clear your .m2 folder, used "Invalidate Caches" and "Restart, double-checked the plugin declarations in your POM file, then:

1. Check the IntelliJ Maven configuration

Ctrl+Shift+A
Type "Maven Settings"
Tick "Use plugin registry"
Double-check your "Maven home path" and "User settings file"
Try to get additional logs: set "Output level" to "Debug" and click "Apply"

2. Check the IntelliJ Java configuration

Ctrl+Shift+A
Type "Importing"
Double-check the JDK used in "JDK for importer"

3. Update your cacerts keystore file

Make sure you trust the TLS server certificate of the remote Maven repository. For that, add the public certificate(s) to the cacerts keystore under /path/to/jdk/jre/lib/security/ (for instance by using https://keystore-explorer.org/) - default password is "changeit"

If you can't edit the file:

Ctrl+Shift+A
Type "Importing"
Update "VM options for importer" with -Djavax.net.ssl.trustStore=/path/to/cacerts -Djavax.net.ssl.trustStorePassword=changeit and click "Apply"

score 0 · Answer 50 · edited Jul 28 '23 at 10:24

0

I also had this error for a long time until this solution solved my problem:

Try deleting the maven-site-plugin directory from your local repository (located at ~/.m2/repository/org/apache/maven/plugins/maven-site-plugin) and running mvn clean install again.

edited Jul 28 '23 at 10:24

banan3'14

3,810
3
24
47

answered Jul 10 '23 at 10:42

sorour

1

does it add anything to this answer: https://stackoverflow.com/a/65332786/7769052? – banan3'14 Jul 28 '23 at 10:26

banan3'14 · Answer 51 · 2023-07-28T10:37:20.500

What worked for me was to delete the following build plugin:

    <plugins>
        <plugin>
            <groupId>org.springframework.boot</groupId>
            <artifactId>spring-boot-maven-plugin</artifactId>
        </plugin>
    </plugins>

and I added the following taken from https://intellij-support.jetbrains.com/hc/en-us/community/posts/360010178219-Cannot-resolve-plugin-org-apache-maven-plugins-

<build>
    <pluginManagement>
        <plugins>
            <plugin>
                <artifactId>maven-clean-plugin</artifactId>
                <version>3.1.0</version>
            </plugin>
            <plugin>
                <artifactId>maven-site-plugin</artifactId>
                <version>3.7.1</version>
            </plugin>
            <plugin>
                <artifactId>maven-jar-plugin</artifactId>
                <version>3.2.0</version>
            </plugin>
            <plugin>
                <artifactId>maven-deploy-plugin</artifactId>
                <version>3.0.0-M1</version>
            </plugin>
            <plugin>
                <artifactId>maven-surefire-plugin</artifactId>
                <version>3.0.0-M5</version>
            </plugin>

            <plugin>
                <artifactId>maven-project-info-reports-plugin</artifactId>
                <version>3.0.0</version>
            </plugin>
        </plugins>
    </pluginManagement>
</build>

score 0 · Answer 52 · answered Aug 04 '23 at 07:56

Another possible solution (which worked for me): as only IDEA fails, but Maven CLI works, the issue must be completely on the IDE side. To have an homogeneous behavior, go to

Build, Execution, Deployment → Built Tools → Maven

and set the Maven home path to the system installation (so to not use the bundled version).

Maven plugins can not be found in IntelliJ

52 Answers52

Linked

Related