I am used to using the Eclipse Gradle plugin by Pivotal in Luna, but now that Mars was released I am trying to use Buildship. However, I have not yet figured out how to refresh my project's dependencies.
I know that the project is set up correctly because it worked perfectly fine in Luna with the other plugin, but although importing into Mars was simple, I am getting errors because none of the dependencies have been downloaded. Am I misunderstanding the purpose of Buildship and I should switch back to the plugin by Pivotal, or am I overlooking something?
Related
I have upgraded my eclipse from Indigo to Luna that time i am getting so many errors regarding plugins not imported. Please let me know if any one have idea about how to add the below plugins in Eclipse Luna.
I am unable to add any plugins in Eclipse Luna. Can any one provide suggestions to resolve these imports?
org.eclipse.jface.viewers.*;
org.eclipse.jface.wizard.*;
org.eclipse.jdt.core.*;
orgeclipse.jdt.internal.core.*;
org.eclipse.jdt.internal.ui.text.java.*;
org.eclipse.dt.core.search.*;
org.eclipse.swt.SWT;
org.eclipse.swt.events.*;
org.eclipse.draw2d*;
org.eclipse.core.runtime.*;
org.eclipse.ui.internal.*;
org.eclipse.ui.IEditorPart;
In past releases of Eclipse the eclipse development plugins were only available via the build path when you enabled the plugin development environment, and there were several ways to do that. When I went to a new release that enabled state was reset and I'd get the same kind of errors you're getting. I found the easiest way to re-enable the plugins was to create a dummy plugin project as that has the side affect of enabling the plugin development environment. I'd just delete the dummy project and rebuild the entire workspace.
For some reason everything related to maven has disappeared from my eclipse kepler installation. I can't update the project or build it, I can't start a new maven project and there is no trace of any maven related menu.
Any idea how to solve it?
Thanks.
Try in the Eclipse MarketPlace to see if the Maven Integration for Eclipse is installed. If not, maybe you can install it. If it is installed, I can not help you, but my recomendation would be to get a new Eclipse from their web.
I've installed the Websphere Development tools in STS 3.3.0 (Juno 3.8.2 version) as well as the m2e wtp connectors. I'm now having issues with building in Maven. I'm getting the following exception when updating the Project using maven.
java.lang.NoClassDefFoundError: org.eclipse.m2e.wtp.WTPProjectsUtil
at com.ibm.etools.maven.javaee.core.configurators.Utils.isJPAProject(Utils.java:43)
at com.ibm.etools.maven.javaee.core.configurators.JPAProjectConfiguratorDelegate.configureProject(JPAProjectConfiguratorDelegate.java:46)
at com.ibm.etools.maven.javaee.core.configurators.JPAProjectConfigurator.configure(JPAProjectConfigurator.java:45)
at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:109)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:472)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:137)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:465)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration0(ProjectConfigurationManager.java:403)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:316)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$2.call(ProjectConfigurationManager.java:1)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:137)
at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:89)
at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1301)
at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:313)
at org.eclipse.m2e.core.ui.internal.UpdateMavenProjectJob.runInWorkspace(UpdateMavenProjectJob.java:77)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
However when I look in the plugins directory I can see the jar file org.eclipse.m2e.wtp_1.0.0.20130613-0136.jar which contains the class in question. How do I work out what the eclipse classpath is and is there a way to add this library to the classpath?
This answer is a temporary fix / hack.
Same problem for me since WDT upgrade :
"Web Development Tools" version 8.5.1002.v20130402_2058
with "m2e-wtp" version 1.0.0.20130613-0136
Root cause : Versioning rules for plugins dependencies
Solution :
Open file eclipse\plugins\com.ibm.etools.maven.javaee.core_1.0.0.v20121205_2240.jar
Edit META-INF\MANIFEST.MF
Change in Require-Bundle section
org.eclipse.m2e.wtp;bundle-version="[0.16.0,1.0.0)"
By
org.eclipse.m2e.wtp;bundle-version="[0.16.0,2.0.0)"
Or something like that greater than 1.0.0.xx ... and without change number of characters in column
Save file, jar and restart Eclipse with -clean option.
m2e v1.0.0 and wdt 8.5.1 (not 002) were working fine, but com.ibm.etools.maven.javaee.core-xx.jar was not in this version ... so the only sustainable solution is a WDT update (dependencies range upgrade), perhaps in v8.5.1003.
It turned out that I was using the wrong version of Juno and should have been using Juno 4.2. Once that was installed along with Websphere 8.5.5 plugin I just needed to update the m2e WTP plugin to the latest 1.x.x plugin.
It took me a long time to figure out the issue. What I did to fix the issue was, I uninstall the maven juno integration plug in and install the other maven plug in(m2e-wtp) and that did the trick and I am back on my eclipse workspace without any issues. Hope this will help.
Before we started using Gradle, a multi-project (10-12) development effort within Eclipse successfully deployed, via a WTP project, to one of the internal Tomcat 7 servers. We find this very useful for development.
With Gradle up and running the dependent project's jar files are no longer being copied to the ../WEB-INF/lib directory. I don't believe this has anything to do with gradle as it is completely out of the picture later on, but it is different, so I am mentioning it. Building the standalone war file works perfectly as does "gradle jettyRun".
If I add the project facet "Utility Module" to the dependent projects within Eclipse then it works. However, I don't recall that this was ever done initially. Ok, this also really complicates the generation of the eclipse projects from gradle as well!
I can live with it, but was wondering if anyone knew if it has to be this way or if there is some alternative.
Thanks - versions: eclipse Indigo SR2, Java 1.7, Gradle 1.2
I've run into this problem as well: An Eclipse WTP project that depends on other projects won't deploy those projects' dependencies unless they are WTP projects as well.
This is far from an ideal solution, but in my own build scripts, I work around this by using the eclipse-wtp plugin instead of the eclipse plugin:
allprojects {
apply plugin: 'eclipse-wtp'
}
There are a couple of bugs related to this: GRADLE-1880 and STS-2192.
Hello I'm trying to install maven plugin with eclipse and I have a following problem, more in picture below :
So my question is, is this supposed to take this long or I did something wrong?
I'm using eclipse galileo , I went to the window-> install new software -> typed in
http://m2eclipse.sonatype.org/update/ website and name maven
Pressed next then finish, did I do something wrong, or is there another way to get maven working with eclipse? I need it for my project . thank you
First, update site url you pasted is url for stable version builds. According this document stable version of m2eclipse works with Eclipse 3.2, 3.3 or 3.4.
To work with Galileo version (Eclipse 3.5) try update from stable development builds site. I work with this version and I'm happy with it. It has a lot more features than stable one.
You could use maven-eclipse-plugin instead of m2eclipse.
With maven-eclipse-plugin you just add some configuration to pom.xml, execute mvn eclipse:eclipse and refresh project in Eclipse and you are done.
You will lose UI to handle dependencies etc. directly from IDE (that would be provided by m2eclipse) but I have not seen much benefit from that. You can manually edit pom.xml just fine.