I just moved from eclipse to IntelliJ.
I have a spring boot project, that runs perfectly in eclipse. but when I tried to run it on IntelliJ, I'm getting "Process finished with exit code 1"
I've tried all the next solutions:
https://stackoverflow.com/search?q=eclipse+intellij+spring+boot
but nothing workes. any advice?
spring boot config
It seems like your application is failing on startup, probably due to missing configuration.
Put your correct spring boot profile in "active profiles".
For example, this might be "dev" or "dev,integration-tests" or whatever :)
I was finally able to solve the problem by deleting the contents of the folder .m2\repository\org\apache\maven\plugins\maven-site-plugin.
and reimport maven projects.
Related
I want to create a beans.xml but I could not find "spring beans configuration file"
when I try to install Spring IDE in Eclipse Marketplace, it doesn't appear there.
what is the reason ? and how to install spring IDE ?
I am beginner. Please tell me clearly
sorry man, but actually i don't know how to use Spring in eclipse, but, you can use STS https://spring.io/tools.
STS have the same UI of eclipse, but work specifically of Spring.
I have to work with Eclipse due to some reasons which is fresh to me.I created a simple dynamic web project using Maven,then I try to run this project with plugin called tomcat7-maven-plugin,but each time I run it with command tomcat7:run,the console shows build success but the project is automatically terminated.This really confused me,because when I deploy it on my
local tomcat, nothing happened.
from the snippet, I guess the reason is that it tells:
Skipping non-war project
This basically means that your maven project does not produce a WAR (packaging=war) hence tomcat plugin has nothing to run.
I think also that it's not really related to Eclipse here (try to run it from the command line and the results will be the same)
Please restart the eclipse and clean the project. hopefully it will work.
I'm facing a rather odd issue which is I've set the necessary dependencies a mentioned in Spring documentation but once I add the #EnableConfigServer annotation Eclipse says it cannot be resolved. I checked the Maven dependencies folder and the necessary Spring Cloud Config *.jars were there. I tried deleting .m2 directory and rebuilding project nothing seemed to work. Any idea on this would be great.
Looks like this is the pure eclipse issue.
Try cleaning the project once and check.
I have a Spring Boot Gradle application with apply plugin: 'war'. I run the application on STS by right click > Run As > Spring Boot App. It runs fine. Now I make a change to the code and I want to redeploy (and better automatically). The only way I know now is to stop the server and run again. Is there any faster solution?
Spring-boot provide something called devtools which is a very neat feature.
Include this starter on your gradle build
compile("org.springframework.boot:spring-boot-devtools")
This will automatically restart whenever files on the classpath changes. So you don't have to manually stop and start server.
you can see more details here.
We have a multi-module Maven project: project-war depends on project-api.
I have imported the modules into IntelliJ, and I would like to use tomcat7:run to run run the project-war application in Tomcat. I do so, the application runs fine.
I make a change to project-api, stop Tomcat, restart Tomcat. The project-war application runs again fine, but the changes to project-api are not reflected as expected.
How to get the transitive changes from my workspace to be reflected when running tomcat7:run?
I've tried "Resolve Workspace artifacts". It didn't help. In fact, I don't get this setting at all.
I've tried "Before launch:" "Make". It does what appears to be a build (compile) but it didn't help either.
I think what I"m looking for is pretty much what m2e/Eclipse calls workspace resolution. Can't get it to work in IntelliJ. Your help much appreciated!
This is a good repository to test this out.
As it turns out, this problem existed using IntelliJ 12.1.7, but not anymore using IntelliJ 13.1.5.
Workspace resolution works with a combination of the described configuration:
Resolve Workspace Artifacts
Before launch: Make