I would like to script certain eclipse actions that are too repetitive. An example use case would be: Starting Tomcat, Starting GWT debug, then connecting to GWT debug mode. Best case scenario is if this could be done by shell via an external eclipse interface. But I'd settle for a macro in Eclipse itself as well. Are there any solutions as such?
Thanks!
See my answer at How can I launch more than one debug session in Eclipse from a single click? . The same plugin can work for you as well.
There is a little macro plug-in for Eclipse that seems to work for what you'd want.
Related
Im working on a large project and the build process is slow to Fuse, so Im looking into hot deployment. Ive had a look at JRebel - but cannot see support for Fuse/Karaf - so am wondering if they would work together? Are there alternatives?
JRebel works with Karaf, really the best thing to do is just try it out. Depending on how you're running your app (in the IDE vs command line) you may need to add the JAVA_OPTS yourself. The IDE plugin can generate them for you.
First of all, I would like to say that I don't know if Stack Overflow is the right forum to ask this, but let's give it a try.
I'm a .NET developer, but I'm interested in giving Scala a try in my next project. Developing for .NET is very "simple" in the sense that everything happens "inside" Visual Studio, from coding to installing libraries, to deploying, you get it.
I've stumbled upon the Typesafe Activator tool. My question is for Scala programmers who are using it: is this tool usually used as an IDE for the whole project? Or is it used just to generate the templates, then work in another IDE like Eclipse? What would be a usual "cycle" in web app developing project with Scala?
Thank you very much in advance!
Right now the code editor in Activator is pretty basic. So most users start with Activator for new projects and learning and then open the project in IntelliJ or Eclipse. Then you can continue using Activator alongside an IDE if you want.
I agree with James that it is common to create the project with Activator before then moving to your preferred IDE. I'm not even close to the expert he is, and that has worked for me.
But inconsistently.
For me, as an IntelliJ user on Mac, I have found that JetBrains (the makers of IntelliJ) continues to make so many changes to their Scala, SBT, and Play plugins that there can be inconsistencies. I've found starting from IntelliJ sometimes works; starting with Activator sometimes works; importing an SBT project of any kind sometimes works; and so on. I have yet to uncover any pattern as to why.
You may have better luck than I, but just be ready to try a few approaches. Using Activator first as James suggests is certainly a viable one.
I have started using GWT 2.5 with Eclipse as my IDE. When using the debugger in Chrome, it is onerous to sort through the source file listing to set my breakpoints. It is even worse when I already have the relevant code open in Eclipse, and I have to find it in Chrome now.
Is there a way to set a breakpoint in Eclipse, and make use of that in Chrome?
This seems like a natural concept given the existence of SourceMaps. If it isn't already a part of the SourceMaps specification, perhaps it should be.
That's not possible in Eclipse (yet?)
I've been told JetBrains is working on it for IntelliJ IDEA though.
If you're using Javascript, then why not just add the line
debugger;
to your code?
It should pause execution on that line, and you can do it from eclipse/whatever IDE you're using.
I am working with Eclipse Juno and a JSF 2.1 Project.
Auto-Complete for EL Expressions inside a Facelets file is excruciatingly slow.
Slow to the point where if I try to auto-complete a JSF Bean with 20 or so methods, Eclipse editor will hang for 10-15 seconds until I see the members/properties list.
The way I see it I have 2 solutions, I don't know how to implement neither, so help on any would help. (With preference to the first)
Resolve the slowness problem. My guess is Eclipse is doing a bunch of stuff I don't need when I press ctrl-space and if could disable those that should make it faster. (Educated Guess)
Disable Auto-Complete for El Expressions completely and install JBoss Tools (Which I must say, works flawlessly but when in conjunction with the native auto-complete support, It still hangs on every ctrl-space).
So, either solution would help - Resolve slowness or Disable Auto-Complete all together.
Thanks in Advance!!
Well.. Since no one is answering..
I removed the JSF facet and installed jboss tools.
Works fine since I build my project from outside of eclipse.
There are some caveats like support for certain content but all in all that's the "lesser of evils" solution.
Here is what worked for me :
Window -> Show View -> Error Log
if there are errors about a timeout to find javadoc for the JRE, do this :
Project Properties > Java Build Path > Libraries
remove the JRE, add the JDK
(or maybe you can configure the Java-doc for the JRE)
I come from a background in C++, Python, and Django and I'm trying to expand my horizons and learn Scala and Lift. However, I'm having a really hard time figuring out how to debug Lift applications using eclipse.
I can create projects using some of the lift sbt templates and run them no problem. However, I haven't been able to start the application from within Eclipse because it can't find Jetty, and as a result, I'm not able to use the debugger to step through the Lift code. Weeks of googling haven't helped much.
Could someone share their methods or suggestions? I'm also new to the jvm, so feel free to share best practices or point out important differences that I may be missing.
Ok, I've gotten this figured out.
So I'm not actually launching the application from the Eclipse debugger. I'm starting the application through sbt, and then connecting the Eclipse remote debugger to the sbt vm that's running the webapp.
Here's what I did:
Assuming you have sbt-launch.jar in /bin:
Create the file /bin/sbt_debug with permission to execute and containing this line:
java -Xmx512M -Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005 -jar /bin/sbt-launch.jar "$#"
What this script is doing is starting sbt and instructing the jvm to allow debugging on port 5005
Go to your lift project directory in your terminal and enter sbt_debug. Once you're in the sbt console enter container:start / container:update or ~jetty:start / ~jetty:update depending on which version of sbt you're using.
Next go to Eclipse, click the debug icon and select "Debug Configurations..."
On the left column, click "Remote Java Application" and create a new debug configuration. Set the Port to 5005.
Hit the Debug button and the Eclipse debugger should now be debugging the sbt process you started earlier
Note: This is the first method that has worked for me. If you have one that is better, please share
I've found the most useful tools to be the SBT Eclipse Plugin and the RunJettyRun plugin for Eclipse. The former will allow you to generate Eclipse config files based on your SBT setup and the latter will launch Jetty from Eclipse with the debugger attached. An added bonus is that generating your Eclipse config using "eclipse with-source=true" from the SBT prompt will download and attach src jars as well so you can step through Lift and any other 3rd party libraries you depend on as well as your own code.