Hello Guys, How are you all? Hope You all Are Fine. Today I am facing weird error Plugin ‘org.springframework.boot:s in java. So Here I am Explain to you all the possible solutions here.
Without wasting your time, Let’s start This Article to Solve This Error.
Contents
- How Plugin ‘org.springframework.boot:spring-boot-maven-plugin:’ not found Error Occurs ?
- How To Solve Plugin ‘org.springframework.boot:spring-boot-maven-plugin:’ not found Error ?
- Solution 1: Just add the version of the plugin in the pom.xml
- Solution 2: add this line pom.xml
- Summary
I am facing weird error.
Plugin 'org.springframework.boot:spring-boot-maven-plugin:' not found
How To Solve Plugin ‘org.springframework.boot:spring-boot-maven-plugin:’ not found Error ?
- How To Solve Plugin ‘org.springframework.boot:spring-boot-maven-plugin:’ not found Error?
To Solve Plugin ‘org.springframework.boot:spring-boot-maven-plugin:’ not found Error Here To resolve this error you need to add the version of the plugin in the pom.xml. Just like this: ${project.parent.version} Second solution is By adding a version of the plugin in the pom.xml my issue was resolved.
- Plugin ‘org.springframework.boot:spring-boot-maven-plugin:’ not found
To Solve Plugin ‘org.springframework.boot:spring-boot-maven-plugin:’ not found Error Here To resolve this error you need to add the version of the plugin in the pom.xml. Just like this: ${project.parent.version} Second solution is By adding a version of the plugin in the pom.xml my issue was resolved.
Solution 1: Just add the version of the plugin in the pom.xml
Here To resolve this error you need to add the version of the plugin in the pom.xml. Just like this.
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>${project.parent.version}</version>
Now your error will be solved.
Solution 2: add this line pom.xml
By adding a version of the plugin in the pom.xml my issue was resolved.
<version>2.4.3</version>
Summary
It’s all About this issue. Hope all solution helped you a lot. Comment below Your thoughts and your queries. Also, Comment below which solution worked for you?
Also, Read
- Error: “chromedriver” cannot be opened because the developer cannot be verified. Unable to launch the chrome browser
Today We are Going To Solve Plugin ‘org.springframework.boot:spring-boot-maven-plugin:’ not found in Java. Here we will Discuss All Possible Solutions and How this error Occurs So let’s get started with this Article.
Contents
- 1 How to Fix Plugin ‘org.springframework.boot:spring-boot-maven-plugin:’ not found Error?
- 1.1 Solution 1 : Configure your pom
- 1.2 Solution 2 : Add version of the spring-boot-starter-parent
- 1.3 Solution 3 : Add the version of the plugin in the pom.xml
- 2 Conclusion
- 2.1 Also Read These Solutions
- How to Fix Plugin ‘org.springframework.boot:spring-boot-maven-plugin:’ not found Error?
To Fix Plugin ‘org.springframework.boot:spring-boot-maven-plugin:’ not found Error just Configure your pom. Here you have to do is just configure your pom like in the given below code. By doing this you can solve your error.
<groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> <version>${project.parent.version}</version>
- Plugin ‘org.springframework.boot:spring-boot-maven-plugin:’ not found
To Fix Plugin ‘org.springframework.boot:spring-boot-maven-plugin:’ not found Error just Add version of the spring-boot-starter-parent. You have to just add version of the spring-boot-starter-parent in the plugin section just like below and you can solve your issue.
<plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> <version>2.3.5.RELEASE</version> </plugin>
Solution 1 : Configure your pom
Here you have to do is just configure your pom like in the given below code. By doing this you can solve your error.
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>${project.parent.version}</version>
Solution 2 : Add version of the spring-boot-starter-parent
You have to just add version of the spring-boot-starter-parent in the plugin section just like below and you can solve your issue.
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>2.3.5.RELEASE</version>
</plugin>
Solution 3 : Add the version of the plugin in the pom.xml
Just add the version of the plugin in the pom.xml It will help you.
<version>2.4.3</version>
Conclusion
So these were all possible solutions to this error. I hope your error has been solved by this article. In the comments, tell us which solution worked? If you liked our article, please share it on your social media and comment on your suggestions. Thank you.
Also Read These Solutions
- ImportError: cannot import name ‘force_text’ from ‘django.utils.encoding’
- java.lang.IllegalArgumentException: Could not resolve placeholder
- Excel file format cannot be determined, you must specify an engine manually
- General error during semantic analysis: Unsupported class file major version 60
- Command CompileSwiftSources failed with a nonzero exit code xcode 13
Problem
When we build spring boot applications with gradle, sometimes we get this error :
Build file '/Users/bswen/private/bw/bswen-github/bswen-project/spring-boot-23/build.gradle' line: 2
Plugin [id: 'org.springframework.boot', version: '2.3.2.RELEASE'] was not found in any of the following sources:
* What went wrong:
Plugin [id: 'org.springframework.boot', version: '2.3.2.RELEASE'] was not found in any of the following sources:
- Gradle Core Plugins (plugin is not in 'org.gradle' namespace)
- Plugin Repositories (could not resolve plugin artifact 'org.springframework.boot:org.springframework.boot.gradle.plugin:2.3.2.RELEASE')
Searched in the following repositories:
Gradle Central Plugin Repository
Environments
The environments are as follows:
- java version: jdk 1.8
- spring boot version: 2.3.2.RELEASE
The build.gradle
The build.gradle of this spring boot application is as follows:
plugins {
id 'org.springframework.boot' version '2.3.2.RELEASE'
id 'io.spring.dependency-management' version '1.0.8.RELEASE'
id 'java'
}
group 'com.bswen'
version '1.0-SNAPSHOT'
sourceCompatibility = 1.8
repositories {
mavenLocal()
maven { url 'https://maven.aliyun.com/repository/google/' }
maven { url 'https://maven.aliyun.com/repository/public/' }
maven { url 'https://maven.aliyun.com/repository/spring/' }
maven { url 'https://maven.aliyun.com/repository/gradle-plugin/' }
maven { url 'https://maven.aliyun.com/repository/spring-plugin/' }
mavenCentral()
}
dependencies {
testCompile group: 'junit', name: 'junit', version: '4.12'
}
How to solve the problem
This error is caused by the incorrectly configured build.gradle in the project. You should add buildscript block to the build.gradle, this buildscript block is required by the build.gradle script own.
According to this post (by Peter Niederwieser):
The buildScript block determines which plugins, task classes, and other classes are available for use in the rest of the build script. Without a buildScript block, you can use everything that ships with Gradle out-of-the-box. If you additionally want to use third-party plugins, task classes, or other classes (in the build script!), you have to specify the corresponding dependencies in the buildScript block
You must use a buildScript block because Gradle needs this information in order to understand the rest of the build script. That’s why you have to provide this information in a separate channel (the buildScript block). Technically speaking, Gradle needs this information in order to compile and evaluate the rest of the build script. What happens under the hood is that Gradle separates the build script into two scripts (the buildScript block and everything else) so that it can process them separately
and this comment by Ashish:
- The global level dependencies and repositories sections list dependencies that required for building your source and running your source etc.
- The buildscript is for the build.gradle file itself. So, this would contain dependencies for say creating RPMs, Dockerfile, and any other dependencies for running the tasks in all the dependent build.gradle
please do as follows:
open the build.gradle ,add the lines:
buildscript {
repositories {
mavenLocal()
maven { url 'https://maven.aliyun.com/repository/google/' }
maven { url 'https://maven.aliyun.com/repository/public/' }
maven { url 'https://maven.aliyun.com/repository/spring/' }
maven { url 'https://maven.aliyun.com/repository/gradle-plugin/' }
maven { url 'https://maven.aliyun.com/repository/spring-plugin/' }
mavenCentral()
}
dependencies {
classpath("org.springframework.boot:spring-boot-gradle-plugin:2.3.2.RELEASE")
}
}
After this change, the whole build.gradle file is as follows:
buildscript {
repositories {
mavenLocal()
maven { url 'https://maven.aliyun.com/repository/google/' }
maven { url 'https://maven.aliyun.com/repository/public/' }
maven { url 'https://maven.aliyun.com/repository/spring/' }
maven { url 'https://maven.aliyun.com/repository/gradle-plugin/' }
maven { url 'https://maven.aliyun.com/repository/spring-plugin/' }
mavenCentral()
}
dependencies {
classpath("org.springframework.boot:spring-boot-gradle-plugin:2.3.2.RELEASE")
}
}
plugins {
id 'org.springframework.boot' version '2.3.2.RELEASE'
id 'io.spring.dependency-management' version '1.0.8.RELEASE'
id 'java'
}
group 'com.bswen'
version '1.0-SNAPSHOT'
sourceCompatibility = 1.8
repositories {
mavenLocal()
maven { url 'https://maven.aliyun.com/repository/google/' }
maven { url 'https://maven.aliyun.com/repository/public/' }
maven { url 'https://maven.aliyun.com/repository/spring/' }
maven { url 'https://maven.aliyun.com/repository/gradle-plugin/' }
maven { url 'https://maven.aliyun.com/repository/spring-plugin/' }
mavenCentral()
}
dependencies {
testCompile group: 'junit', name: 'junit', version: '4.12'
}
The code base of this example is uploaded to github.com, you can click this web url to download the code.
References
You can view some references as follows:
- spring boot and gradle
I have a new error in my project that is in the pom.xml file. How can I fix it?
The error below shown in IntelliJ idea:
Plugin 'org.springframework.boot:spring-boot-maven-plugin:' not found
peterh
11.4k17 gold badges85 silver badges104 bronze badges
asked Aug 18, 2020 at 12:07
2
From the Preferences in Intelli J, navigate to «Build, Execution, Deployment > Build Tools > Maven», check the «Use plugin registry», and click «OK».
Then «File > Invalidate Caches / Restart» to reload Intelli J. The error will go away automatically.
answered Apr 8, 2021 at 8:22
4
Add following code
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>${parent.version}</version>
</plugin>
and then click on the icon as shown in screenshot, to load Maven changes in pom.xml file
answered Aug 15, 2021 at 12:33
Vivek SinghVivek Singh
8796 silver badges10 bronze badges
3
I had the same problem. This summer Intellij suddenly started throwing this error but build went through. I just had to specify version of plugin and it stopped throwing this error.
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>2.3.4.RELEASE</version>
</plugin>
answered Oct 17, 2020 at 13:06
mixnixmixnix
4493 silver badges12 bronze badges
3
I had the same problem using IntelliJ version 2020.2.4. The solution was to edit the pom.xml file and specify the version of the Spring-Boot Maven plugin, with the following syntax:
<plugin>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-maven-plugin</artifactId>
<version>2.4.0</version>
</plugin>
This Intelli-J release does not recognize the «RELEASE» keyword after the version number, as suggested in the previous answer.
answered Dec 8, 2020 at 22:38
John GoodJohn Good
1511 silver badge2 bronze badges
4
What worked for me after long tries is updating the indices of the remote maven repository:
Settings > Build, Execution, Deployment > Build Tools > Maven > Repositories.
Then select the remote repository and then update.
This must work.
answered May 4, 2021 at 13:42
ab2311ab2311
791 silver badge1 bronze badge
If you try to update your IDE. It will fix the issue permanently. As, Apparently there was some bug in the IDE which got fixed in build No: Build #IU-211.7142.45, built on April 30, 2021.
answered May 31, 2021 at 10:20
This error comes when you are using a milestone or snapshot release. It will be resolved after adding appropriate pluginRepository
elements.
You can read more about it here: https://docs.spring.io/spring-boot/docs/current/maven-plugin/reference/htmlsingle/#getting-started
<pluginRepositories>
<pluginRepository>
<id>spring-snapshots</id>
<url>https://repo.spring.io/snapshot</url>
</pluginRepository>
<pluginRepository>
<id>spring-milestones</id>
<url>https://repo.spring.io/milestone</url>
</pluginRepository>
</pluginRepositories>
PS: Above answers worked because they explicitly mentioned a different version, which is not milestone or snapshot. IMO that’s not the ideal solution.
answered Feb 13, 2021 at 13:56
kulsinkulsin
3885 silver badges18 bronze badges
By default my configured snapshot project inherited from the spring-boot-starter-parent and set the parent. I added version number and it now as follows:
<parent>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-parent</artifactId>
<version>2.5.4</version>
</parent>
As docs suggests:
«You should need to specify only the Spring Boot version number on this dependency. If you import additional starters, you can safely omit the version number. »
https://docs.spring.io/spring-boot/docs/current/maven-plugin/reference/htmlsingle/
answered Sep 9, 2021 at 6:21
To add to anyone coming across this problem, I am on WSL and my project was in the linux part of wsl (i.e, outside of the mnt folder). What DID fix the problem for me (after countrless tries to update the remote repository, invalidate caches, mvn clean compile
and other similar things) was the following :
to cut one random dependency from my pom.xml
file, click on the icon shown on Vivek Singh’s answer and afterwards repaste that dependency and reclick on the icon.
Hope it helps someone.
answered May 20, 2022 at 13:35
After so many unsuccessful tries I just clicked on the Event Log on the bottom right of the IDE then found out that my pom file had become a non managed then chose to Add as a maven project and then the maven window reappeared
answered Aug 14, 2022 at 13:01
imdondoimdondo
1322 silver badges12 bronze badges
Just started type version from scratch and IDE suggested
mopversion
answered Nov 16, 2022 at 14:46