I have installed FindBugs as an Eclipse plugin. When I try to run the tool on a particular project, the following error is thrown by eclipse -
An internal error occurred during: "Finding bugs in (project_name)...".
Could not initialize class edu.umd.cs.findbugs.DetectorFactoryCollection
Any kind of help will be appreciated.
Eclipse version-3.6.2
JDK version-1.6.29
Related
I'm using Eclipse Neon from the release date. Yesterday I got some strange errors in Eclipse and after a reboot of the Eclipse instance everything was gone. I installed Eclipse and my plugins again. Everything is working again but when I launch the Java debugger on one of my project I got the error:
An internal error occurred during: "XXXX".
java.lang.NullPointerException
This error occurs on debugging all my projects also in another workspace. Can someone help me with this? The error is not explaining what the exact problem is.
In the logfile of Eclipse I can found the follow error:
java.lang.NullPointerException
at org.eclipse.jdi.Bootstrap.virtualMachineManager(Bootstrap.java:36)
at org.eclipse.jdt.internal.launching.StandardVMDebugger.getConnector(StandardVMDebugger.java:560)
at org.eclipse.jdt.internal.launching.StandardVMDebugger.run(StandardVMDebugger.java:246)
at org.eclipse.pde.launching.AbstractPDELaunchConfiguration.launch(AbstractPDELaunchConfiguration.java:79)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:885)
at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
I fully removed my previous Eclipse environment. Settings included.
Installed Eclipse environment from a clean install and installed all my plugins again. The problem was fixed.
Debugging a test in Eclipse, I received "Can't recognize runtime TestNG version"
I just upgraded testNG thru Eclipse to 6.9.11
also upgraded Java to 1.7.0_51
Now I receive the following error in Eclipse: Can't recognize runtime TestNG version
Any help would be appreciated.
I also changed my dependency version to 6.14.3 like above comment. (https://mvnrepository.com/artifact/org.testng/testng/6.14.3)for TestNG in pom.xml
from eclipse Marketplace downloaded TestNG plugin(latest version),and error was resolved.
Eclipse : Neon version
Raised an issue on TestNG GitHub, they have reverted back to the previous version 6.9.10 in Eclipse marketplace. It is working now!
Eclipse:
In my case I worked with Maven,retreived dependencies of TestNG with version 7.0.0-beta1 in pom.xml and tried to execute my first program with TestNg,got "failed to get TestNg version from class Javaillegalargumentexception".
I changed my dependency version as 6.14.3 for TestNG in pom.xml and from eclipse Marketplace downloaded TestNG plugin(latest version),got output successfully.
I add sbt eclipse plug-in .First I created the project named hello the in project directory i created a file named plugins.sbt and add this line in it
addSbtPlugin("com.typesafe.sbteclipse" % "sbteclipse-plugin" % "2.5.0")
and after the sbt> I typed eclipse then it created the project for eclipse
when I open eclipse it gives me error message
An error has occurred. See the error log for more details
The org.eclipse.jdt.ui.javaElementFilters plug-in extension "scala.tools.eclipse.javaelements.ScalaElementFilter" specifies a viewer filter class which does not exist.
Plug-in org.scala-ide.sdt.core was unable to load class scala.tools.eclipse.javaelements.ScalaElementFilter.
An error occurred while automatically activating bundle org.scala-ide.sdt.core (806).
please help me to how to resolve this error and when I imported the sbt project eclipse give me another error
Building workspace has encountered a problem
Errors occurred during the build.
Error instantiating builder 'org.scala-ide.sdt.core.scalabuilder'.
Plug-in org.scala-ide.sdt.core was unable to load class scala.tools.eclipse.ScalaBuilder.
An error occurred while automatically activating bundle org.scala-ide.sdt.core (806).
Plug-in org.scala-ide.sdt.core was unable to load class scala.tools.eclipse.ScalaBuilder.
An error occurred while automatically activating bundle org.scala-ide.sdt.core (806).
Please help me
scala version 2.11.1
sbt version 0.13
I added the scala-IDE plugin from this source
http://scala-ide.org/download/current.html
i am using eclipse juno and pasted the following location in install new software
http://download.scala-ide.org/sdk/helium/e38/scala211/stable/site
my project compiles successfully in sbt
Are you using Eclipse Luna for Java Developers (as opposed to Eclipse Classic) AND Scala IDE 4.0 milestone 3? There is a known issue (solved in the nightly builds since then), reported on the mailing list here.
You can "fix" it by either upgrading the Scala plugin to a nightly build (they're pretty stable), or going with Eclipse Classic instead.
I have installed GGTS plugin for eclipse kepler 3.5.1 RELEASE. I created simple grail project. But while building project. Its getting error
Errors occurred during the build.
Errors running builder 'Java Builder' on project 'FirstApp'.
org.codehaus.groovy.runtime.StringGroovyMethods.plus(Ljava/lang/String;Ljava/lang/CharSequence;)Ljava/lang/String;
and if we saw in markers, I found this error
Internal compiler error: java.lang.NoSuchMethodError: org.codehaus.groovy.runtime.StringGroovyMethods.plus(Ljava/lang/String;Ljava/lang/CharSequence;)Ljava/lang/String; at
org.codehaus.groovy.grails.transaction.transform.TransactionalTransform.moveOriginalCodeToNewMethod(TransactionalTransform.groovy:259)
Config.groovy /FirstApp/grails-app/conf line 0 Java Problem
I am using feroda 17. Eclipse Kepler.
We were experiencing the same error today, it turned out that the project created by GGTS had a groovy compiler level of 2.3 but the GGTS plugin only supported up to groovy compiler level 2.1.
The fix was to install the "groovy 2.3 compiler for groovy-eclipse".
The compiler can be found under the "language and support tooling" heading in the extensions browser which is opened by clicking the "IDE extensions" button in the STS dashboard.
Although the compiler states that it will automatically become the default workspace compiler in eclipse this did not happen for us. In fact we needed to set it as the workspace default in "preferrences > groovy > compiler" and then restart eclipse (maybe I restarted twice, cant remember exactly).
we also ended up installing "groovy 2.3 compiler for groovy-eclipse" twice as the first time an eclipse IDE update was installed, I think because our kepler installation was a bit old.
Hope this helps.
I have Eclipse (Juno SR2) with both M2E (1.3), M2E-WTP (0.17) and WebSphere Dev Tools for v.8. The problem started after Websphere Dev tools installation. It says in error dialog : "Validating" "org/eclipse/m2e/wtp/MavenWtpPlugin".
In Eclipse logs it turned out to be NoClassDefFoundError
!MESSAGE An internal error occurred during: "Validating <module name here>".
!STACK 0
java.lang.NoClassDefFoundError: org/eclipse/m2e/wtp/MavenWtpPlugin
Does anyone had some luck in solving this issue?
Thanks!
The missing class is in fact there, plugin org.eclipse.m2e.wtp. Started to dig in the IBM WAS Dev Tools.
The problem originates from com.ibm.etools.maven.javaee.core plugin.
Checked MANIFEST.MF under \plugins\com.ibm.etools.maven.javaee.core_1.1.0.v20130522_1924\ and it turned out there is some strange version range bundle dependency on org.eclipse.m2e.wtp;bundle-version="[1.0.0,2.0.0)";resolution:=optional. The plugin org.eclipse.m2e.wtp version is not even close to version 1.0.0 and resolution is optional, so made some changes to conform the bundle resolution:
...,org.eclipse.m2e.wtp;bundle-version="[0.1.0,2.0.0)";resolution:=optional,...
Started Eclipse with -clean argument, and refreshed all Maven projects in the workspace.
This seems to do the trick for me. You may still get
"Updating Maven Project". Unsupported IClasspathEntry kind=4
but there is a fix for this already here "Updating Maven Project". Unsupported IClasspathEntry kind=4