I have been using Linux for less than 24 hours, so please, if there is anymore information I should provide, do be quite specific about how to get that information.
I've been trying to install Node.js, express.js and eclipse. As you can see, ubuntu does recognise both node.js and express as installed on my system (I think!) and I got the Nodeclipse-extension for eclipse, but still Eclipse doesn't seem to recognise either node.js or express (see my image below). I also want to add that the time occurrence of the error, I was trying to build a Node.js Express Project.
At this point, how do I go about debugging the situation? The folder location shown in the image does not fully exist. I can only go as far as [...]/bin/ - I have been looking at error messages similar to mine, and it seems like people are getting such errors because they're lacking an installation, however, from my screenshot provided, I would think everything is installed as needed.
I am using a native 64-bit windows laptop with Linux (Ubuntu) installed through a virtualbox. Ubuntu is 14.04 LTS and just 32-bit, as I don't have spare 2 gb ram to give the 64-bit version. Sadness.
I'd appreciate any help!
In Eclipse Windows -> Preferences -> Nodeclipse
check what is configured for Node and Express
Read more on http://www.nodeclipse.org/
I found a solution, which worked for me:
WINDOWS:
I did double installations of the needed modules. They were both located in C:/Users/X/AppData/Roaming, in the Eclipse directories and finally in C:/Program Files/nodejs. When I deleted all the node_modules, besides critical ones for nodejs to function and then ran Eclipse with Nodeclipse, it seemed to function and Eclipse automaticly defined folders in its own subdirectory, in which Express were located.
UBUNTU:
Delete all node_modules files and run Eclipse with Nodeclipse. See the windows explanation for a more detailed overview. Same problem and solution seemed to be present for both systems. Do note that the file directories are of course not completely interchangeable. You'll need to locate your instances of node_module.
Related
Until yesterday I had the following dev environment perfectly working:
Ubuntu LTS 20.04
Eclipse (in Snap)
JavaFX (JARs and *.so's in local Folder, --module-path configured in project)
Yesterday "snap" came up and said: stop the app to let updates be installed ... I think, it was talking about Eclipse.
After having Eclipse restarted, my JFx application complained about "glass not being in Java Lib Path". I know this error from Ubuntu LTS 22.04 and could not fix it a month ago (when repairing all paths, you'll end up by some lib ONLY accepting a glibc 2.33, but I already have 2.35) ... that's why I rolled back to 20.04 a month ago :-/
Now this bug hits me again in 20.04 via snap updates.
I drilled the behavior down to having a project's debug commandline, that shows above error. It starts to work as soon as I change that cmd line to NOT use Eclipse's build-in JRE located in Eclipse's snap path. Result: it only works outside of Eclipse now.
Question: does anybody know, how to find the connection in Eclipse's config, that causes Eclipse's Java to use the (obviously freshly installed) snap-version of openjfx (19+11) instead of a working and properly configured (old) local JFx version?
That version seems buggy and does NOT work for Ubuntu 22.04 also in an out-of-the-box installation.
^5
Synopsis
//EDIT: in case this matters ... just saw, that in /snap/eclipse there are TWO versions (60 and 61), with current pointing to 61, BUT the debug-commandline path, showed by Eclipse, uses 60 (not "current and not 61). When I manually launch the Eclipse in 61, it appears completely fresh, without default workspace path and without any plugins.
So when using (on commandline) the java from there, it also works, having no JavaFX plugin under Eclipse dir "61".
I don't reaaly get the idea of a "current" that is unconfigured and all paths pointing to old dir 60 ... obviously my lack of knowledge about snap :-/
I found a workaround: I added an external Java Execution Environment (the system owned JRE) and configured the project to use that.
Now it works again from within Eclipse using the old JFX in my home dir - even the debugger is working fine :-)
But this is no clean solution. I want to have in MY influence, what stuff the internal Java Environments of Eclipse are using. I cannot accept, that the internal JREs are magically connected to some magically appearing snap-app (openjfx 19/11) without even a notice to me or better the option to say "no" to either new snaps or snap updates.
well ... talking to myself :-)
LAST update: some background rollback appears to have sent me to the Test-VM with Ubuntu 22.04 instead of my active VM with Ubuntu 20.04.
So my posted workaround can be regarded as working for those that desparately try to get JavaFX working under 22.04 :-)
So the "problem" I thought to see concerning 20.04 does not exist ... sorry.
I have found out that Eclipse workspaces contain configuration information in addition to project code and compiler products, and that is why I cannot share them between OS's. I don't want to get fancy (Version control systems) because it's just me using them on one machine.
Is it possible to symbolic-link each source file from the Windows workspace to the Linux workspace? Has anyone done this and created a script already? I would probably write it run each time Linux logs in. Any problems in doing this that I don't see?
I was able to run Eclipse until I tried to install another compiler, suggested by a online tutorial for C++. Now I'm getting the 'No virtual machine was found error'. I know I'm suppose to match the versions of the programs but I can't seem to figure it out. I thought I had downloaded 64 bit version of each program in Eclipse and JDK but I don't know how to verify it. I go to each file and try to get the info but I must be looking in the wrong places. I have copied the file location of JDK and pasted it in the Advanced System Settings in Environment Variables. In the Systems Variables for User on the variable line I typed "path", on the value line I pasted the location: C:\Program Files\Java\jdk1.8.0_05\bin. I have even uninstalled both programs several times and reinstalled them. I've been at it for several hours now with no success. Any suggestions, anybody. Thank you.
The instructions how to install GoClipse have been followed.
I'm not getting any autocomplete stuff happening at all, either for local packages that I write, for built in stuff, or for GAE stuff (I have downloaded Go src to the SDK folder as the wiki states).
Are there any settings that I can check to ensure it is set up correctly? Is autocomplete supposed to work in the current version?
As the GoClipse with AppEngine article you linked to says:
We assume the reader has a working copy of GoClipse running in their Eclipse environment.
so that’s not the article you want to refer to. Instead, check for GoClipse.
The auto completion is named content assist in eclipse. The GoClipse features state:
Now delivered with content assist via Gocode for Windows, OS X 64bit, and Linux 64bit.
Gocode is an auto-completion daemon. So you will also have to install and run that one besides your eclipse + GoClipse.
There is a bug in the current version of Goclipse for the Linux platform. It currently delivers a prebuilt version of gocode for Windows, 64 bit OS X, and 64 bit Linux. I have only been able to test it locally with limited resources, so I really depend on users to report the problems they find at:
http://code.google.com/p/goclipse/issues/list
If you are having problems, I urge you to download and install gocode into your $GOROOT/bin directory and see if that helps. Otherwise, the fix will come in the next release in a few days.
Also, sorry for causing you any trouble and thank you for trying Goclipse.
If you are not using a gocode upstream (but the one shipped with Eclipse) on Linux you are also no be able to build your application with CRTL+F11, although just clicking in Run->Run is going to work.
So, I strongly recommend to update your gocode on Linux, as simple as:
$ sudo GOPATH=/opt/go/ go get -u github.com/nsf/gocode
I've manually installed the latest Eclipse on our debian server and wanted to configure it so all users share the same configuration. It turned out less obvious than I thought: I don't seem to be able to install packages for all users. If I run it myself, all configuration data is saved under my own home directory. If I run Eclipse using sudo, everything is saved under the root directory but is not accessible for other users when they run Eclipse.
I've been browsing the manual of Eclipse and some forums, but apart from a "yes, you can" I couldn't find any information on how that should be done. The biggest problem is installing plugins for all users to be found. Any help is greatly appreciated.
Eclipse : 3.6.1 classic, installed using this procedure.
Server uname: GNU/Linux *** 2.6.26-2-amd64
Server is accessed using Putty, and Gnome desktop through realVNC. Just mentioning it if that is of any importance. Our sysadmin is on "prolonged leave" (working in Spain and never replaced), so I'm stuck without help here.
EDIT:
I've found a list of variables that could be set in the launcher.ini or config.ini regarding configuration : osgi.configuration.area, osgi.configuration.area.default, osgi.sharedConfiguration.area, osgi.configuration.cascaded, ... But I can't figure out exaclty how to set these correctly.
-- I asked this question also on Serverfault, but I am far from certain where this belongs. Feel free to merge both questions in the appropriate place. --
For plugins, you could add in eclipse.ini (for all Eclispe you install) a common path for "shared dropins directory".
All plugins copied in that directory will be detected when Eclipse is launched.