I'm learning how debug a clojure app...I've tried several tools and no one has convinced me..now I'm trying swank-cdt which is based in CDT...I've read the instruction here:
http://georgejahad.com/clojure/swank-cdt.html
I've added my dev-dependencies to my lein project (in my case clojure-source "1.2.1" because I'm using clojure 1.2.1...)
I've run lein deps..and lein install...elein swank for use repl, and slime-connect for connect my repl...so far so good...I've used (use 'debugproject.core) run well...
now..when try (use 'swank.cdt) I get in my stacktrace:
com.sun.jdi.Bootstrap
[Thrown class java.lang.ClassNotFoundException]
and inside my repl :
warning: unabled to add tools.jar to classpath. This may cause CDT initialization to fail.
what am I doing wrong!??
thanks for your patience and for read all my post :D
and many thanks if you can help me
Swank-clojure 1.4.0, released yesterday, automatically sets up the tools.jar crap for you. You don't need to symlink or copy anything.
I've copied tools.jar into lib/dev
Related
Summary
I've been trying to get Eclipse's JDT LS (JLS) working with vim-lsp (in Neovim), but have been unsuccessful in synchronising the JLS with a Gradle project. I am, unfortunately, constrained to Windows.
The Problem
Using this configuration (commit #d1c7a25 at the time of posting), I cannot synchronise the JLS with a Gradle project "due to an error configuring Eclipse" because of an "invalid project description" (see log).
Trawling through Google and the GitHub issues of both the JLS and vim-lsp plugin has gotten me nowhere.
Remarks
I feel like it's most likely an issue with my configuration. If anyone has got this working with other LSP plugins aside from YouCompleteMe (such as CoC or LanguageClient) those setups are also welcome, but vim-lsp is preferred.
To reiterate, and just in case:
Windows 10 Pro (v1803 build 17134.407)
Neovim (v0.3.1) with plugin vim-lsp
Gradle wrapper (v4.10.2)
Eclipse JDT LS (v0.28.0 build 201811140630) [.tar.gz]
using this configuration (originally #d1c7a25)
Thanks!
Figured it out.
The workspace directory for the JLS (specified by the command line argument -data) can't be nested under the project's own directory.
*bashes head on desk*
I am using IntelliJ Idea 2017.3 and on any Gradle project (even for simple 'hello world' from GitHub) I always got next error:
"Unable to start the daemon process.
This problem might be caused by incorrect configuration of the daemon.
For example, an unrecognized jvm option is used.
Please refer to the user guide chapter on the daemon at https://docs.gradle.org/3.5-rc-2/userguide/gradle_daemon.html
Please read the following process output to find out more:
-----------------------
Error: Could not find or load main class 1.8"
Meanwhile, if I run an application with Gradle wrapper (gradlew.bat in my case) everything works perfectly. For me it looks like misconfiguration issue, but I cannot find what I am doing wrongly in Idea configuration or any other place. I appreciate any help with it or clue where to dig.
The issue was resolved and I would like to share this knowledge with all those who encounter a similar problem.
In my case, I had to delete two configuration files gradle.experimental.xml and gradle.settings.xml from IDEA configuration directory %IDEA_HOME%\config\options. I suppose they were created at the time when I installed Gradle globally on my PC. Somehow these settings were persisted, even after I removed globally installed Gradle and started to use Gradle's wrapper.
I am unable to debug remote applications due to: No executable code at line
I am running ultimate edition of Intellij, version 14.0.3. My application is running inside tomcat 8 and i'm building it from the command line using Maven. This problem appeared after i switched from the community edition to the ultimate edition.
Project sources are the same and I am able to connect to tomcat for remote debugging. The only issue is that all my breakpoints are invalidated.
Please advice on how to fix this issue.
Cheers.
Remove all IDEA related project files and open the project by the .pom file.
I've had the same problem. Simply compile the directory that the class resides, and the debugger will pick up the break point.
I had the same problem and I implemented a similar solution.
Remove all IDEA related project files and open the project by the .pom file.
I use Gradle for my projecto, so i removed the project from intellij and then reimported it.
I hope others could read it and helps them
if you are developing an Atlassian plug-in and connected to the server via remote debug, run atlas-package to sync deployed plug-in and your source code.
If you are running a maven project execute the following commands in cmd prompt.
mvn clean install
mvn compile
This will resolve the problem.
The solution that worked for me is much more embarrassing. I put the breakpoint on the wrong line.
You see two breakpoints, first one is working and the second one is complaining about "no executable code ...".
It turns out there really is no executable code, just a string.
Is it possible to import the Apache Storm Incubator (0.9.3) Into Eclipse (Kepler), or should i just stop wasting my time?
I have tried the following, with the following results:
Attempt 1:
Clone (git clone ...).
Import as maven project into eclipse
A few hundred "LocalCluster could not be resolved to a type" and "LocalDRPC cannot be resolved to a type" errors follow. I assume that this is something to do with the clojure plugin not found/supported within eclipse, and the fact that Localcluster etc are written in clojure, but I have no idea where to even start to resolve that one.
Attempt 2:
Clone.
mvn eclipse:eclipse
Import project into eclipse
This provides the confusing:
"Project 'storm-core' is missing required source folder: '/home/dev/gitprojects/incubator-storm'"
This is confusing because it is the directory of the project I just imported, so I'm having a hard time seeing how it could be missing. I can remove it from the build path, but then I get to a few hundred "LocalCluster could not be resolved to a type" errors.
This is just a soul-destroying and/or demoralizing waste of my time right now. Is there any way of actually importing the incubator project so that it actually works? Any update I can make to Eclipse to make it work? Any help would be welcomed.
Thanks.
Dave
I saw the light and install the joda-time plugin for grails.
However, when I tried to commit my changes to source control I realised that grails had located the files in:
C:\Users\Steve\.grails\1.1.1\plugins
instead of somewhere under the project directory of:
f:\grails\projects\myproject
Yeah I'm using windows :-\
So now when someone pulls down my changes from source control they are missing all the joda-time plugin lovelyness and they are wanting to spank me :)
What should I be setting so that grails doesn't put anything under my user directory?
(It isn't installed as a global plugin - just as a project one - at least I think so, I ran "grails install-plugin joda-time" )
Many thanks in advance.
P.S. Currently listening to Plug In Baby by Muse....how coincidental :D
The plugin is listed in application.properties, so when someone gets your code Grails will install missing plugins the first time they run 'grails run-app' or other commands.
If you want to revert to 1.0.x behavior just create grails-app/conf/BuildConfig.groovy with the line
grails.project.plugins.dir='plugins'
and your plugins will be in with the rest of the project files.