Coming from Visual Studio, I'm pretty new to the Eclipse IDE.
And finding it very difficult. I seem to get error messages of the type "missing ..." a LOT.
The latest issue I'm having, where I just can't get around is this:
I"m trying to compile & run this sample project: http://code.google.com/p/gwtgae2011/
When I choose "checkout maven projects from SCM" my SCM drop down is empty...
So I just checked it out with Hg manually. No problem.
Trying Import > Existing Maven Project. Seems to read the pom.xml alright, but shows an error:
"No marketplace entries found to handle maven-gae-plugin:0.8.1:unpack in Eclipse. Please see Help for more information."
Since I can't find it through updates or market within eclipse I downloaded maven-gae-plugin (http://code.google.com/p/maven-gae-plugin/downloads/list). I figured just dropping it into the "plugins" or "dropins" folder should be enough. Apparently not so...
Question: How do I fix this error?
(I tried both 3.6 & 3.7)
Links to some good eclipse tutorials covering these kinds of topics are very welcome too!
THANKS!
maven-gae-plugin is in central repo so it should be found.
Did you set the path to your local repo? http://united-coders.com/phillip-steffensen/maven-2-part-3-configuring-eclipse-for-apache-maven-2-projects
I ran into this error, what worked for me was:
Comment the plugin
Import into eclipse
Uncomment the plugin
Discover an error in the plugin XML
Fix error found in the plugin XML
I am not certain, but it seems like this is a unclear error that something about the pom.xml is invalid.
Related
I've faced this problem quite a lot lately but I didn't care in the past and decided to rewrite the whole project I'm getting from GitHub but now when the project is enormous I can't do this anymore.
Here is a picture of the problem:
As you see the classes are already in their places but the import still failing I don't know why. I checked my SDK and it's already added so anyone have an idea why this happening?
If it is a Maven project, open the Maven tab and click Reimport all dependencies button.
Another solution is to use the Terminal, just run mvn clean install command.
I'm getting this error in Spring Tool Suite when I right-click a project and select Maven->Update Project. When I go to ~/.m2/repository/sun/plugin/plugin, here is what I see.
$ ls
m2e-lastUpdated.properties
plugin-1.7-javadoc.jar.lastUpdated
plugin-1.7-sources.jar.lastUpdated
Apparently the plugin-1.7.jar is missing from my Maven repository. This might be because I stupidly deleted ~/.m2/repository yesterday in order to try to fix another problem.
How do I fix this error? How can I install plugin-1.7.jar? It's the plugin-1.7 jar from com.sun, but when I search Google I can't find where to download it.
I just installed Eclipse Neon PDE and try to build a simple plugin project with the "Hello World" template. Unfortunately i get many "The import org.eclipse cannot be resolved" errors straight after creating the plugin project.
This is the project with the errors in code and dependencies:
.
I use Eclipse Neon for RCP and RAP Developers with these plugins:
.
I already tried cleaning the project and fiddled around with the build path but without success.
Can anyone help me with this error? Probably I'm missing the obvious.
Greg is right. Also check your target platform in Windows->Target Platform->Add.
Add default setup there.
Please find more details adding target platform # http://www.vogella.com/tutorials/EclipseTargetPlatform/article.html
You are missing a number of plug-in dependencies.
You need to add at least:
org.eclipse.core.runtime
org.eclipse.core.resources
to your plug-in dependencies list. You will probably have to do a 'Source > Organize Imports' after adding the dependencies to update the imports.
You can always click on the red X at the left of the editor to get possible resolutions of problems - this will often tell you which dependency to add.
I fixed my problem by launching the eclipse with "-clean" arguments.
I'm trying to convert an eclipse Java project to a Maven project. When I convert the project to a Maven project, the pom.xml displays the following error:
Cannot read lifecycle mapping metadata for artifact
org.apache.maven.plugins:maven-jar-plugin:maven-plugin:2.3.2:runtime
Cause: error in opening zip file
When I check the lifecycle file, it's blank. Any idea of why I can't convert this project without getting this error?
Thanks for the assistance!
If that file is empty, it might have been caused by a bad download of the maven artifact. Therefore check your proxy settings in Eclipse as well as in Maven itself (~/.m2/settings.xml)
One thing you can try is deleting the project(from the workspace, not from your computer!) and importing it as a maven project using the deleted project's folder as your source. I've had a lot of trouble in the past with converting projects with m2e, but deleting/re-importing always seems to do the trick.
To import an existing project as a maven project go to file->import and select "Existing Maven Project". Select your project's folder, and import. I realize it's basically the equivalent of "turn it off and turn it on again", but like I said, it has always worked for me in the past. At the very least it will help you narrow your scope.
Hope this helps!
I am trying to build a Grails project in STS and am getting many error messages of the form: Groovy:unable to resolve class org.codehaus.groovy.grails.commons.ConfigurationHolder as well as others like Groovy:unable to resolve class org.grails.plugins.springsecurity.service.AuthenticateService
. I have Grails 1.3.7 selected in the Project Properties, but I don't see an item for 'Grails Depedencies' like I do when I create a sample project. Is this the problem? How can I add it back in?
I don't know why, but here are the steps I took to solve the problem:
Right click on the project and go to Grails Tools -> Enable Dependency Management
Grails Tools -> Refresh Dependencies. This correctly added the 'Grails Dependencies' library.
I still had plugin errors. I for some reason had to uninstall them and then reinstall them for the project to realize they were there.
For anyone who is using Grails >= 2.4
If you are using Grails 2.4 and above, use grails.util.Holders instead of org.codehaus.groovy.grails.commons.ConfigurationHolder.
Read the doc here section 'Static Holder'
Classes The following deprecated classes have been
removed from Grails 2.4.x:
org.codehaus.groovy.grails.commons.ApplicationHolder
org.codehaus.groovy.grails.commons.ConfigurationHolder
org.codehaus.groovy.grails.plugins.PluginManagerHolder
org.codehaus.groovy.grails.web.context.ServletContextHolder
org.codehaus.groovy.grails.compiler.support.GrailsResourceLoaderHolder
If you or any plugins you have installed are using these classes you
will get a compilation error. The problem can be rectified by updating
to new plugins and using grails.util.Holders instead.
If "Refresh Dependencies" has done all it can for you (as you indicate in your comment on the question), try disabling and re-enabling dependencies. You might try refreshing dependencies again afterward if the Acegi plugin still isn't recognized.
there is another way solved me this issue when i moved my workspace from Windows OS to Ubuntu , go to
yourWorkSpace -->yourGrailsProject-->setting folder --> org.grails.ide.eclipse.core.prefs,
then check all the grails paths are correct or not , because in my case all were pointing to windows paths ..
Hope this solve.
I faced a similar issue: "Unable to resolve class GrailsTestCase". I checked Grails Tools of my project and observed Dependency Management was already enabled (IDE - GGTS). I just disabled Dependency Management, refreshed and enabled it again. This solved the issue for me.