I have a Spring project that I am running in Tomcat in Eclipse. This was working till yesterday. All of a sudden it does not look like Tomcat is loading the project although it shows as published and synchronized. I see no errors in Tomcat logs. Any insights on why this is happening?
For anybody who might run into this issue. I right clicked on project, click on properties, go to Deployment Assembly and added "Build Maven dependencies". I added them before and the project was loaded with no issues. When I checked it after this issue started happening, the "Maven dependencies entry in "Deployment Assembly" disappeared.
Related
Eclipse project-> properties-> targated runtime(missing)
Unable to see the option targated runtime in Eclipse project properties for integration of project with tomcat
1) First Add the server to your project in Eclipse.
2) Right-click on the project to properties will get even if you not getting targeted runtime update eclipse.
refer to the below Screenshot.
When I starting the project the following error appears:
The project TestProject.Android needs to be deployed before it can be started. Verify the project is selected to be deployed in the Solution Configuration Manager.
In the Configuration Manager Build and Deploy configurations enabled for Any CPU.
Note: reproduce only on Visual Studio 2019. On the previous version (2017)
all works as expected.
You can simply change the settings in your Solution as:
right-click the Solution -->then go to "Configuration Manager" -->then check "deploy" for your required platform project.
Hope!! It will work..
I am trying to introduce MUnit unit tests to an existing Mule project which is using Maven for builds and dependency management.
However I am unable to run the tests visually through Mule Anypoint Studio, when I try to debug them I get the error:
MUnit test could not be run, The Archive
C:/pathtomyuserfolder/.m2/commons-logging/1.2/commons-logging-1.2.jar which is
referenced by the classpath, does not exist.
I can however run the test using Maven using the command "mvn test" but this is not ideal as I want to be able to debug the test, pausing at breakpoints etc.
I can reproduce this problem using the Mule Anypoint Exchange sample here: https://www.mulesoft.com/exchange/#!/munit-example. When I open this project I can debug the tests with no problems, but if I then right click on the project and select Maven Support In Studio -> Mavenize. I am then unable to debug the tests in Studio.
What am I doing wrong? Is this behavior supported?
This turned out to be a problem with the build path on my machine and nothing to do with MUnit.
The clue was in the actual error message above - that the path was missing the /repository folder under my /.m2 folder. I'm not sure how it happened by my M2_REPO was pointing to the wrong level.
The strange thing is that the two projects I tried would still actually run ok, so that's why I thought it was just a problem with MUnit. Sorry for the confusion and thanks to #Ryan and #Dds for your comments. I should have first tried to fix the problems highlighted in Mule Studio before posting.
I tried lot of different solutions but none of them is working and still getting error
Gradle 'MyApplication' project refresh failed
Error:Error:No cached version listing for com.android.tools.build:gradle:0.12.+ available for offline mode.
I tried:
Uninstall/install android studio
Remove .gradle folder from user directory
Change 0.12 to 1.12. in gradle properties
Enable Use local gradle distribution in gradle settings.
any suggestions how can I fix this.
I also tried various solutions mentioned in stackoverflow but none of them is working.
Fixed the issue, please follow these steps
Goto "File->Settings" in the settings window choose "Gradle" and under the "Globle Gradle Settings" unchecked the "offline work" check box and click "Apply" & "ok".
Do Gradle sync or restart the IDE.
Once Gradle build is success, can check the "offline work" again.
I'm trying out the next version of Eclipse using the latest milestone build and I'm having an issue getting my Maven project deployed to Tomcat.
Previously in Eclipse 3.6, my project was automatically enabled as a web project when checked out from SVN. I've checked out my project in 3.7 but get nothing indicating it's runnable as a web project (e.g. trying to run the project doesn't give me the usual "Run on Server" option).
What I've installed is Indigo RC4 "Eclipse IDE for Java EE Developers" version. I then added the latest M2E milestone from here. This enabled me to get up and running, check out my project and I seem to be able to build the project fine (which does create my .war file for remote deployment). Still no "Run On Server" options though.
Does anyone have any clues on what I could be missing? I'm guessing it's a Maven & WTP integration plugin but I haven't spotted the right one yet.
Before m2e became an eclipse project the WTP integration shipped with the core module. Now the core module is an eclipse module and the WTP integration is shipped separately. The current Indigo snapshots of m2eclipse-wtp can be found here. I was unable to get any artifacts from this update site however, even though it's listed in the corresponding JIRA issue.
Fortunately, today m2e-wtp was made available through the m2e Marketplace. Just open the eclipse preferences, go to 'Maven' -> 'Discovery' -> 'Open Catalog' and install it. .
It will work with the lastet version, it's just the .project that is not right.
Simply go into the project properties, make the projet faceted.. tick Dynamic Web Module and you'll get run on server as an option after that.
This will enable the "Run on Server" option, however your problems don't finish there as when you then run it, you'll get a 404.
To fix this, go back into project properties, Deployment assembly.
Delete the WebContent entry (and you can delete the folder in the project later too), and make sure you have the src-main-webapp & src-main-resource folders added.
Bingo.. run the app and it should be fine.