I created a small Java project in NetBeans. When I run it, there appears no compiler log.
I'd like to see the compiler output even when I decide to run the project. How can I enable it?
In NetBeans Menu/Window/Output
Related
I was developing a plugin, using Eclipse IDE for java developers (Version: 2021-09 (4.21.0)
Build id: 20210910-1417)
During development, when I run it as an eclipse application, it opens a runtime-Eclipse application where the plug-in is present. In my setup this new runtime-eclips app opened from a folder next to the workspace, where C codes were present. (and my progrem would get the tests run in C , and get the results from it's exe)
Then I downloaded the Eclipse IDE for committers, which is a newer version. I downloaded it as a zip and after unpacking I run the eclipse.exe. My program had problems opening the runtime-Eclipse application in C there, so i went back to the older one which is installed on my computer.
After opening the original eclipse, on which I was working and had no problems, I was hoping everything will be fine. It opens the IDE for java developers (same version, same build) but I have the same problems with the runtime-eclipse application as the one I run as an eclipse.exe , (not recognising the C code?? I don't understand).
When i try to run the plug-in I get this error.
And when the runtime-app opens i get this error.
I cannot create C projects anymore on the runtime-app. I don't know the reason behind this.
Also I have billion of these
["java.net.UnknownHostException: downdload.eclipse.ort"]
[" org.eclipse.equinox.p2.core.ProvisionException: Unknown Host: http://downdload.eclipse.ort/eclipse/updates/4.2/content.xml "]
Thank you in advance!
I don't know if it is possible or not, since seemingly it did not update the older eclipse IDE. If it can be restored the way it was before i run the eclipse.exe, I would be happy.
eclipse.ort is obviously a typo, it should be eclipse.org, I don't know where it is coming from - but its possible you enter it yourself as update site
the runtime error means eclipse cannot resolve all dependencies, which means it could not load bunch of plugins including yours, you need to figure out why on your own, its not possible to debug this remotely, its best to start from the scratch in the new workspace
The solution was easier than expected. The run configuration was modified by the other eclipse version. It was not launched with every plugin. only a selected handful
I have an Eclipse Maven project that uses selenium and Junit to run some tests.
It currently works fine when I run it as Junit Test.
I want to try out the ide from visual studio code but I can't get it to work. I am getting the following message:
ConfigError: The project 'CopaSelfWebCheckIn' is not a valid java project.
I know there is no main folder. I rather run it from where it is right now.
Can someone explain me how to set this up. Thanks.
Make sure you have all the required java extension installed on your VS-Code
Mainly
Test Runner for Java
Language Support for Java(TM) by Red Hat
Maven for Java (if you have any dependencies)
Debugger for Java
Project Manager for Java
All these extensions are packed with a single extension Extension Pack for Java
if you have installed proper dependencies and extensions your vscode will look similar to the below picture
Trying to get a lift project to run on windows, I've installed maven on my computer, then tried to use
mvn archetype:generate from cmd, then chose the lift basic one , but it always failed on the jetty:run part. Before that, I had to change a lot of the pom.xml file to even get a successful build (since the tutorial I was using was obsolete and it couldn't find the dependencies).
So I've decided to try with the eclipse plugin, thinking it should be easier.
I've installed the maven plugin for eclipse and created a project with the lift archetype.
The project was succesfully created, but I have all kinds of errors in the editor for missing ; and so on (I have scala ide installed on eclipse also and creating a normal scala project works and compiles/runs fine). I have also tried to include the scala-library.jar in the buildpath, with no change.
The odd part is that I can run the cmd and go to the project folder, then run mvn jetty:run and it will actually work (?!) Trying to run in eclipse with jetty:run as goal will give me ClassNotFoundException on the HelloWorld snippet.
So what might be wrong with my settings?
UPDATE: no luck whatsoever, after trying 3 different eclipse versions, installing the maven for scala plugin and following every tutorial I could find. It just simply feels all is outdated on the instructions:
this is how it looks after I include the scala libraries for eclipse on every project (after I create it from an archetype):
is this "mvn archetype:generate" up to date? I don't know if anybody guarantees it will work at all..
Anyway, the default way to at least try Lift and see it working is the following: https://github.com/lift/lift_25_sbt
It uses "Simple Build Tool" instead of maven, but maven should work, too. Also, you can easily read "build.sbt" to get all the dependencies.
Plugins for creating eclipse/intellij project definitions are included. (See the README of the demo project.)
The target to create eclipse project is "eclipse" or "eclipse with-sources=true".
The target to launch the app is "container:start".
I have built an executable jar file using netbeans IDE, it works fine in my system but yesterday I gave it to my friend and he is complaining that the file is not running, it just show the splash screen and then closes, he has JRE 6 installed.
I am unable to resolve the issue. Can someone help?
The problem is, you build the jar using JDK7 and you want to run it on JDK6. It will become error. Try to downgrade and build jar again using JDK6.
Right-Click on your project properties and select Libraries and change the Java Platform.
If the JDK6 didn't come out, please make sure to add it from Tools > Java Platforms and Add Platform...
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.