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.
Related
The option runAs->TestNG on xml file is missing somehow on my eclipse,
I tried to install the eclipse from scratch and now I have Version: 2018-12 (4.10.0).
Also I have latest JDK and JRE testNG is installed as far as I see and when I want to install them again I have a problem.
All the threads that i saw till now nothing helped me and i tried all the solution as i wrote maybe you have any idea
the only solution i founded till now is that i need to install eclipse from scratch and convert the same project again to TestNG and to copy the old XML to the new one, if its the latest eclipse than to download the beta version of TestNG
There is an issue with the TestNG plugin and Eclipse 2018-12 (https://github.com/cbeust/testng-eclipse/issues/408). You can use the current beta version from https://github.com/cbeust/testng-eclipse.
If the picture above of your installed software is the current state of your Eclipse 2018-12 setup, it cannot be a clean install. The version 6.14.x of the TestNG plugin is not compatible with 2018-12. It is not possible to install the plugin with Eclipse. Either the existing Eclipse directories are reused or the plugin directories have been added manually. It is important to remove them. After that, it should be possible to install the version 7 beta of the TestNG plugin.
It should look like this:
With this setup, you will get your context menu entry for TestNG:
Eclipse Luna 4.4.2 with Java JDK 1.7
I installed
Spring IDE plugin version 3.7.3
Pivotal Software Spring Tool Suite(STS 3.7.3)
plugins successfully, have no problem with switching to the Spring perspective and my File->new->projects has several spring related selections.
I have been building using maven with no problems. My maven version is 3.3.3. Checking the Help->Installation Details dialog shows eclipse m2e-workspace 0.3.1
When accessing the Eclipse Marketplace, the dialog shows Maven Integration for Eclipse(Luna and newer) 1.5 and the update button is greyed out and there is an uninstall button, so I have that installed.
When selecting Spring Starter Project, I get the creation dialog box with an error message at the top reading --
Can not import using Maven because Can not use Maven: M2E (Eclipse
Maven Tooling) is not installed
I have also lost my maven sub-menu when I right click on pom.xml. Its no longer there.
Any ideas on a solution before I start removing things/changing things and possibly making things worse? Explanations also welcome.
Thanks
When installing the Spring IDE plugin into Eclipse that already has the maven plugin installed results in a serious conflict as Spring IDE also installs maven. It may be resolvable, but I was unable to find a solution.
I did uninstall the Spring IDE, but the problem was not cleared on Eclipse restart. I deleted the corrupted eclipse installation, while keep its workspace intact.
I finally installed STS w/eclipse and pointed it at my previous workspace.
I had the same issue and I have no idea of how to fix that.
To turnaround the this problem, I downloaded the Spring Tool Suite™ by the url: http://spring.io/tools/sts/all
This Suite have all the tools to build any Spring project that you'll want.
Hope this work for you.
I am going to start with GeoTools. Maven in installed correctly as cmd prompt says the version 3.0.4. But in Netbeans 6.5, Maven Category does not appear to create a new project. What should I go through now?
Please follow the link i given..it is given correct explanation about NetBeans IDE and Maven Repositories
Maven Repositories in NetBean IDE
If your system has enough resource, consider upgrading Netbeans to latest version 7.2. It has inbuilt maven plugin or the blow link may help you.
How-to: Install Maven For Netbeans 6.5.x
I'm trying to install m2e plugin to enable maven integration but it looks like plugin is not installed:
What I do:
Maven is already installed in the system and 'mvn --version' works
Help -> Install New Software -> Indigo->General Purpose Tools - m2e
Eclipse restart of course
There is no mention of Maven in eclipse. Not in Window->Preferences, not when creating new project. Nowhere.
Tried different plugin repositories, tried Eclipse Marketplace - nada.
When running Eclipse I get these errors:
org.eclipse.m2e.logback.configuration: SLF4J logger factory is not an instance of LoggerContext: org.slf4j.impl.SimpleLoggerFactory
2 [org.eclipse.jdt.internal.ui.text.JavaReconciler] INFO org.mortbay.log - Logging to org.slf4j.impl.SimpleLogger(org.mortbay.log) via org.mortbay.log.Slf4jLog
Not sure what to do at this point.
Would be grateful for any help!
Leonty
I don't recall what it is called in Indigo. I recently updated to Juno and imported my plugins with no issue. Below is a full list of plugins that I have installed. I'd recommend you uninstall what you have, then search for "Maven Integration". Install that and any other related plugins you will need (i.e. SCM clients).
It is builtin with Indingo, no !?
(Or maybe Indigo WTP)
I am quite sure because I had to re-install Indigo WTP several times
I am installing Eclipse for RCP and RAP Developers. My old copy went rogue and decided to act up.
So clean install time! Yay! I downloaded the new version, copied it to the opt folder, extracted it, and ran it.
For some reason, I can't install any plugins due to some crap error*, and it doesn't have a list of default plugins. I deleted my workspace and the original Eclipse install.
Is there another file that is helping Eclipse keep data from previous installs? I am seeing update sites I added when I was constantly trying to get past this issue.
Also, why can't I install new plugins?
I need a clean install so I can't use the Ubuntu installer.
Any tips are appreciated.
*Cannot complete the install because one or more required items could not be found.
Software being installed: Maven Integration for Eclipse (Required) 0.10.2.20100623-1649 (org.maven.ide.eclipse.feature.feature.group 0.10.2.20100623-1649)
Missing requirement: Maven Integration for Eclipse (Editors) 0.10.2.20100623-1649 (org.maven.ide.eclipse.editor 0.10.2.20100623-1649) requires 'bundle org.eclipse.zest.core 0.0.0' but it could not be found
Cannot satisfy dependency:
From: Maven Integration for Eclipse (Required) 0.10.2.20100623-1649 (org.maven.ide.eclipse.feature.feature.group 0.10.2.20100623-1649)
To: org.maven.ide.eclipse.editor [0.10.2.20100623-1649]
I had the same problem when doing a fresh install of Java EE eclipse (helios, galileo, win32 and win64).
The solution for me was to explicitly open the Java perspective, and doing the install after this. This time the installation worked fine.
I suspect the reason is that after a fresh install not all bundles are loaded (although they are present on disk; a feature of eclipse) so that the dependencies cannot be resolved. Opening the Java perspective or creating a dummy Java project will force to load these bundles. Once a bundle is loaded, its existence is persisted, so this only has to happen once.
This issue was mentioned a number of time on the official websites, but always closed or neglected, probably because the reproducer did not do a fresh install.
Download Eclipse 2018-19 (4.9.0) version as an updated eclipse version and install it! Maven dependency will presented inbuild thing in that model, Right click on project -> properties -> on left pane, Maven will display ! Change your setting there to overcome this error and you can add external JAR'S there