We Keep Coding

IntelliJ Terminal - updated and no longer able to run scripts from terminal

I am pretty new to coding & working with IDEs. Intellij prompted me for an update, which I allowed. Now I cannot run my scripts from the Intellij terminal.
The error message I receive is
"Error: Could not find or load main class src.MatrixHomework.java"
My pathway hasn't changed... it's still
C:\Users\General_Sherman\IdeaProjects\Assignment3\src\MatrixHomework.java
I updated to IntelliJ IDEA 2019.2.1
Build: IC-192.6262.58
I'm using jdk-11.0.2

This is most likely due to the selected directory configuration. IntelliJ uses the configuration under Tools/Terminal in your settings to select what directory to start in. You haven't provided any screenshots, but if this doesn't work, type pwd into the terminal and share it here, we might be able to see the problem.
Regardless, you shouldn't be running your programs through the integrated terminal, and instead via the "Run" tab in the top right. Remember to edit the configurations and add C:\Users\General_Sherman\IdeaProjects\Assignment3\ as a part of the Working Directory argument. This is what a configuration would look like.

VS Code Java Debugger

I installed VS Code Java Debugger and loaded my Java project.
Add Configuration:
I tried to add configuration by clicking the button as shown in above image.
Activating Extensions:
When I click Add Configuration, I get Activating Extensions like above and that's it.
Sometimes I get "The Language Support for Java crashed 5 times in the last 3 mins."
How do I setup the Java Debugger in VSCode?
Note : I Uninstalled VSCode, deleted the extensions from %Users%/.vscode/extensions and reinstalled VSCode and extensions. The issue still exists.

For me, the following actions fixed this issue:
Un-install all Java related extensions.
Re-install the Java Extension Pack only.
https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-java-pack

I was facing the same kind of error but one day found a solution
https://stackoverflow.com/a/61806765/5108695
Basic idea is to:
Install an extension called Lombok Annotations
https://marketplace.visualstudio.com/items?itemName=GabrielBB.vscode-lombok
After installation of this extension, my Java code is able to run and debug in VSCode.
PS: Make sure you had insalled Java Extension pack
https://marketplace.visualstudio.com/items?itemName=vscjava.vscode-java-pack

Error when try install plugin

I'm trying to install a plugin in Eclipse Luna. I installed Papyrus and am trying to install SWT designer, but before the download/installation is completed I get an error:
An error occurred during the
org.eclipse.equinox.internal.p2.engine.phases.CheckTrust phase.
session context was:(profile=epp.package.standard,
phase=org.eclipse.equinox.internal.p2.engine.phases.CheckTrust,
operand=, action=). Error reading signed content. error in opening zip
file
After this error I can't install anything and the install manager does not work anymore and shows me the same error all the time only one way I delete the current Eclipse directory and extract it again.
This time I install Papyrus, SWT designer and some other, but I get the error between install another plugin again. This is wrong if I get an error on install any of plugin reinstalling Eclipse and the other plugin again.
Is this a bug or a problem?

OK finally i found the solution for solve this problem. I don't know why Eclipse is showing me this error and i don't know if this is the best solution. I solve my problem with delete the artifacts.xml file in Eclipse root directory.
After deleting this file try to install that plugin again but this time after few second everything completes and works perfectly.
UPDATE:
If you get that error again then just go to Eclipses' root directory and search for "artifacts.xml" and delete all the files is in the result ;)

Remove the artifacts.xml from the folder.
Keep a copy of it in some other location (preferably external devices such as pendrive or hard disks etc).
Restart Eclipse.
Install the software plugin you want to install (it will ask for permission again).
After installation paste the artifacts.xml file back into the eclipse folder.
Restart eclipse and set the SDK location.
Code to death!!! ;p

Run Eclipse as an administrator, then try to install the plugin again via help->Install New Software. it worked for me

I installed E4 RCP Patch(bugzillas 445122)(Install new software -> Eclipse 4.4.1 Patches for bug 445122) and this helped me.

I ran across this problem while updating eclipse's internal software. I discovered that the jar file org.eclipse.epp.mpc.help.ui_1.5.2.v20161004-1655.jar (found in the error details) in the eclipse plugins directory was corrupted (7-Zip was unable to inspect its contents). I redownloaded and manually replaced this file with one downloaded from their site, and I was then able to install the software without an issue. Hope this helps :)
(If it was a different JAR file for you, you can click "show directory contents" on this page and download the one you need.)

The reason for this error is typically a damaged jar in the bundle pool. You can fix this without manually editing files:
run the Eclipse installer ("Oomph")
select "Bundle pools" from the menu
hit the "Analyze agent" button
wait until the column "Damaged Artifacts" doesn't show a percent number anymore (scanning has finished)
You can now filter the bottom view to show only damaged artifacts, and choose to either delete or repair them (repair means to download them again from the Internet).

Recently i had this issue & i did a few workaround to make things right,
Drag and dropped from official page, normally eclipse restarts after the download, and a pop-up will ask us to select the svn connectors from list. but that didn't happened to me.
Install svn Plugin. (By drag and drop or install new software or any)
After this goto window->preferences->Team->svn
select Connector Tab and click Get connectors Button then the prompt will appear select any one connector to get it done (i use NativeHL 1.8).

I solved this problem by editing the artifacts.xml.
Close Eclipse.
Edit the artifacts.xml.
Find and delete previous entries related to the plugin you are
trying to install.
Save artifacts.xml.
After this you should be able to start Eclipse normally and install your plugin.

I tried many solution from here including the one which says removing artifacts.xml and try installing with opening software with Run as Administrator also tried to install from the Help option "Install new software" none of this worked for me.
Then I updated to the latest version of JDK and it worked perfectly.
I hope this help you.
Thanks.
Vijay P.

org.aspectj.weaver_1.8.10.201704242114.jar
File will be downloaded for google, and it can be placed in eclipse/plugin/org.aspectj.weaver_1.8.10.201704242114.jar can be replaced with older jar file.........it can be solved for your problem...........

Try this from the Eclipse marketplace
1. Click Help>Eclipse marketPlace (Eclipse marketPlace dialog box will open)
2. Type the name of your plugin (ex: type SWT Designer) in the find edit box, make sure to keep default values for All markets and all categories, and click go button.
3. The page will refresh and display all plugins that have swt designer in their name.
4. Click intsall or update button on the one that fits your needs.
5. The installation or update will be done successfully.
6. Restart your eclipse
7. The installation will be fine.

It's a failure in Eclipse.
Try to uninstall it then download it from: https://www.eclipse.org/downloads/
and install it.

Error launching first test application: Android Packaging Problem?

Conversion to Dalvik format failed: Unable to execute dex:
wrapper was not properly loaded first
[project]
Android Packaging Problem
I've never worked with Java or eclipse before, I'm following this introductory guide and all searches via google return no helpful results. I'm guessing the problem is I have built Android stuff with eclipse properly but I have no idea, I followed this guide to the letter and everything went as it explains it should.
Any ideas what caused this problem, or is it specific to the guide? If so I'll post on their help page.
I have tried doing project -> source -> clean up, but that didn't fix anything.
Edit:
I went to Project -> Android tools -> Dex bytecode and it reported:
DexDump: missing classex.dex for project. Please compile first.
So I guess that's my problem! Not sure how to solve though.

Go to Project -> Clean
It will rebuilt workspace and fix the errors if any.

As I said, I had the same problem so I tried all the different versions and
then I stopped filling in the SDK-version number
and finally it did not complain anymore about the wrapper.
After that it was totally fine to write the SDK-version when I created new projects.
Hope it works out for you too.

Had the same problem (running on Windows 7). I resolved it by running Eclipse with Administrator privileges.

try to run eclipse under administrator permission. Problem may be resolve.
I think you installed the SDK in "Program Files" folder . So for do something inside, must have administrator permission.

One thing that may help is to create a new test Android project.
In Eclipse, select File → New → Android Project.
Set the project name to "Test3", check Android 2.3 for the build target, type "com.example.android.apps.test3" for the package name, and type "Test3Activity" in the "Create Activity:" text box. The form should look like:
Click Finish.
Expand the entry for "Test3" in the Package Explorer. Navigate to res/values/strings.xml. Double click on the entry for strings.xml:
Set the text content of the string element having name "app_name" to "Test3":
Right click on "Test3" in the Package Explorer and select Run As → Android Application. The emulator should open and after a long while, you should see:
If these steps do not work, then you probably have an error in your installation.
Try it out and let me know.

I had the same problem earlier today. Google was largely unhelpful.
I fixed it by removing the project from eclipse, then re-importing it.
According to this bug report the problem is caused by upgrading to version 9 of the SDK.

Had the same HelloWorld problem with Ubuntu 64 Lucid / Eclipse 3.5.2 from Ubuntu repository. Restarting Eclipse did the trick, though I notice it still fusses about API level requirement when HelloWorld is run.

Running it as Administrator has solved this issue for me..

Had the same problem - occurred after I tried downloading Android platform v2.3.3 (was using 3.1 and 3.2 earlier) and it interrupted in the middle - restarted eclipse and cleaned all projects and rebuilt and the problem went away

At what point in this tutorial/guide are you running into this problem and did you make sure to include your package information in each file or ie com.something.somethingelse at the top of your class or classes?
Perhaps a registry error or maybe even a problem with activity implementation.
Please post your code if this did not start you in the right direction.

Here are a few things to check:
Make sure you have the latest version oF Eclipse (Helios)
Make sure that you have the Android SDK plug-in for Eclipse.
Now if you have done that... Make sure that any classes you add (Each screen you view on Android is a class and is called an Activity) are in your androidmanifext.xml file See http://wrenbjor.com/2011/01/12/the-androidmanifest-xml-file/ for help on understanding this process.
otherwise make sure there are no red x's in your code or it wont work.
If you still have problems post some code and we can try to help.

Had the exact same problem the other night. Upgraded to Helios (3.6) and it went away, quite possibly as a side-effect.

Under windows 7, rather than run eclipse as an admin, change the permissions on the eclipse folder so the creator/owner has full control, and do the same with the folder the android SDK is installed into.

I had installed Eclipse using the files provided by Windows' native ZIP extractor. I deleted the files and took them from 7-Zip instead. Now the error is gone. So maybe using another ZIP extraction tool will help.

Recently got this when failing upgrade using adb-manager with eclipse open (win32). As eclipse was open, upgrade failed. Then returning to my project this problem occured.
Was solved by closing eclipse, restart as administrator and cleaned project.

I had the same problem but I resolved it using following steps(using eclipse helios and windows XP ) :-
Right click on eclipse.exe.
click on Run As...
Uncheck the checkbox before "protect my computer from unauthorized activity".
And it is running for me as expected !
hope it will also run for you.

Error: Unable to open class file R.java [duplicate]

This question already has answers here:
Developing for Android in Eclipse: R.java not regenerating
(64 answers)
Closed 9 years ago.
Did a fresh install of Eclipse, JDK and android-sdk.
I am currently receiving this error when creating a new project
[2010-09-26 16:07:56 - Test] ERROR: Unable to open class file C:\workspace\Test\gen\com\example\test\R.java: No such file or directory
What's the reason for this and how do I fix it?
Eclipse Helios 32 bit
java version "1.6.0_21"
Android sdk API 8
P.S. I'm new to Android development.
EDIT: I tried most of your solutions, but nothing worked. So I started using my friend's install of Eclipse Ganymede.

I have had same issue, all what I needed to do, was create project and restart eclipse.
//Edit: Complete collapsing of "Package" tree works as well.

This is a mighty annoying error.
It happens 100% of the time when I create a new android project.
What seems to work for me is to just delete the file (which DOES exist and is accessible by my user), then hit build, and it will regenerate it and stop moaning.
It's clearly a bug as there are too many people getting it simply by filling in the boxes in the new project dialog (like me) without even modifying any code!

Have a look at your console. It is an aapt aborted error. Since aapt is the tool that auto-generates R.java, therefore, R.java was not getting generated.
Since R.java is a auto-generated file that stores information about your drawables you should rebuild your project. Before that have a look at your layout xml files and check them for errors.
Notice that Project -> Build All should be selected. Also try to run your project.

Removing Read Only attribute on Eclipse workspace directory and Project->Clean->Build Project
did the trick for me. I then clicked on the project directory from within Eclipse and did a F5 (Refresh) . R.java was generated in the gen folder.

I had a similar error on the creation of new projects myself. After messing around I tried moving the R.Java file into the same location as my projects java file (the src file). Eclipse then saw I removed the R.Java file from its location and created another and that seemed to clean up the error.....I dont know if it was because eclipse rebuilt the file and then saw it or what but that seemed to work for now.

After creating the Project, Right click the Project Folder within the Project Explorer on the Left Tab of Eclipse.
Click on Source->Format.
The Console will say:
[2010-11-24 11:57:42 - YourProject] R.java was modified manually! Reverting to generated version!
Then you're good to go. Try running your Project and it will compile.

Check your imports. If this has sneaked in, then delete it.
import android.R;

Had a almost identical issue with Eclipse Helios 64 bit on Linux, but I had the "1.6.0" API selected like you. The bizarre thing was I could type;
cat <the path it was moaning about>
in a console it would display correctly.
I created a new AVD which used Android 2.1, the issue magically vanished. Perhaps it's a bug in Android SDK or Eclipse?

Right click on your project name in package explorer. Then click 'Validate'. It will be fine.

Here is how to fix it:
Go to your "workspace" folder and make sure it's not "read-only"

Eclipse Menu > Projects > clean

Had the same issue.I was able to solve it by doing the following:
go to Window/Preferences/Java/Build Path
select 'Folders' and change the output folder to 'gen' (this is where Android looks for the generated java files,but the default in eclipse is 'bin').
restart Eclipse
Windows 7,Eclipse 3.5.2

Configure buildpath.. check android , it worked, of course i followed one of the posts mentioned above window, preferences, java, java build path and selected project,
then created a project, and tried to build same error, then i checked build path and saw android is unchecked, checked it and build again, it works!

I had this exact same problem with no helpful errors. finally, I tried deleting my debug keystore and it worked:
rm ~/.android/debug.keystore
I had seen people mention that, but I figured it wasn't my problem because I wasn't getting any errors relating to the debug keystore. I found the answer here:
"Debug certificate expired" error in Eclipse Android plugins
apparently the debug keystore is only valid for one year.

I would say that once you have created your project and you've mention the R.class error --> just restart the Eclipse IDE and everything will be fine ;)

1.-Open Eclipse
2.-Open Window/Preference
3.-Expand JAVA option
4.-Select Build Path
5.-Check the option "Projec"t and uncheck "folder" options
6.-Click on OK
7.-Restart eclipse IDE
Let's go to code !!

This problem can be solved by merely cleaning and rebuilding the project. How ever there is a link to the latest version of Eclipse for Android.
**Eclipse Java EE IDE for Web Developers.
Build id: 20100218-1602
(c) Copyright Eclipse contributors and others 2005, 2009. All rights reserved.
Visit http://www.eclipse.org/webtools**
Here is a link to Android Tutorial with Eclipse
http://developer.android.com/resources/tutorials/hello-world.html

In mac,
I select Project>Clean
after that, i unchecked Build Automatically
then i run the project and it works :)

Windows 7 64bit, run eclipse as administrator, solved the problem for me.

In my case there was no gen folder after pressing clear...
To solve it, i created a new gen file, then when to Build Path => Configure Path, and pressed ok.
All went smooth after that :-)

Following steps are done as solutions:
1. Collapse the project tree structure
2. Go to the workspace and remove the readonly permission of the workspace.
3. right click "default.properties" and go to properties and uncheck the readonly permission in eclipse.( this is done when the workspace shows build error even though there are no compilation issues)