I try in stall luaEclipse on Eclipse follow the instruciton
http://luaeclipse.luaforge.net/manual.html#installation
but I try to add new lua file to a lua project, it reported:
Errors occurred during the build.
Errors running builder 'Lua Project Builder' on project 'testLua'.
Could not initialize class org.keplerproject.luajava.LuaState
Welcome any comment
If you need to use Eclipse, I'd advise using Koneki Lua Development Tools instead, it's more up to date and, last time I checked, works just fine with the latest Eclipse 3.7.
Go to
Help>Eclipse Marketplace
and in search bar search "lua"
You will get "Lua Development Tools" install it restart your Eclipse
Enjoy
Related
I have just reinstalled my OS and made a clean install of Eclipse.
I want to import my previous projects made on a previous version of Eclipse and that is no problem. However when I try to run it then it says: "The selection cannot be run on any server".
I read around I need to go into Properties => Build Path and do something there.
Only problem is my Properties menu does not have a Build Path option. I have searched around Eclipse for a long time now to find Build Path but stil no luck.
Does anyone now where og why my Build Path is no where to be found?
By Chance i found the solution myself.
I originally installed the Eclipse Php Mars version of Eclipse which i still can't get to work. But install the Eclipse Jee Mars (Java EE IDE) version instead solves the problem.
First time you run the code though you might have to run it through the main menu in the top and not by the convenient Run icon botton.
I have no clue why this is but now i can continue my work.
I am currently working on eclipse plug-in that involves many modules, and I would like to debug and run this eclipse plug-in from IntelliJ.I open this project in IntelliJ to edit code but when I have to run/debug this project I have to open eclipse IDE and start it from there. How can I use IntelliJ to do this?
I haven't actually tried this ... but you could try launching the RCP application stand alone but with the remote debug parameters specified for in your application's .ini file.
Then just point IntelliJ to the appropriate source and attach it's debugger to the running app.
Why do you want to do that? Eclipse has multiple tools for the plugin development that you will miss in IntelliJ. Also you need to build your plugin as product headless and then attach a debugger to it.
In my opinion it doesn't worth the effort. I would install Eclipse and devolop with eclipse.
I have an Eclipse plugin that was originally written (not by me, and I don't have access to the original developer) that I'm trying to update for Eclipse Luna, because it stopped working when my team updated to Eclipse 4.4.
I downloaded the Luna Plugin development version, cleared a few warnings, updated some broken code, fixed a few bugs, and tested with "Run As -> Eclipse Application
This worked fine: all the views showed up, the preferences pages, etc.
So then I tried to export the plugin so I could test on a fresh installation of vanilla Eclipse Luna. I did that by using the Export Wizard:
And generated a deployable set of jars with said wizard:
I copied the generated folder (which contains all the jars appropriately) into the dropins folder of my fresh vanilla Eclipse Luna and started it up.
Unfortunately, I got the following error:
Which led me to this SO question and this Eclipse bug report, which explains that I have a 2.x style plugin that uses the plugin.xml instead of an OSGi style manifest.mf. Continuing my search, I found this SO question, which was directed at a 3.x version of Eclipse, but I used the 4.x equivalent:
Which I used with the following options checked:
And I accepted all the changes in the previous pane after the (long-running) changeset. However, upon deploying to my vanilla install, I got the same error about the plugin converter. That led me back to this SO question, which recommending installing the Eclipse 2.0 plugin support package. I did so and restarted Eclipse. The error in my error log did stop showing up, however the view/preferences/etc for my plugin are still not showing up. The plugin does show up under Help -> Installation Details -> Plug-ins, but doesn't seem to be interacting at all.
The text of the plugin.xml can be found here at Pastebin. The text of the MANIFEST.MF can by found at this other Pastebin link
Any suggestions for getting my plugin to work through the manual export so the other developers on my team can test my changes before I try releasing the update to the world?
I checked in eclipse/java plugin project from svn repository.
Eclipse automatically builds the code to show hundreds of errors.
It seems like that eclipse doesn't properly link to the plugin libraries. Googling to find this site that I need dependencies and other tabs in plugin.xml.
What might be wrong? I use Indogo(3.7) on Mac OS X 10.7.4
I used Indigo (3.7) for my Mac, but it happened so that the plugin was built on Helios (3.6). When I run the plugin using Helios, I got the project compiled without errors.
It seems like that some of the plugins are (heavily) version dependent.
Looks like you got the base XML editor instead of the plugin.xml editor.
This is probably caused by your not having the eclipse plugin development environment (PDE) enabled in a new workspace.
Try creating a new plugin project (this will enable the necessary plugin tools), or go to the preferences and enable the "correct" capability. Since the capabilities seem to change from release to release, I always use the first method and then delete the new project.
I'm using Ubuntu 12.04, and to install Eclipse Juno I downloaded it from the official site (I don't use apt-get nor software center)
After updating it from help > check for updates menu, my Eclipse cannot make new project. When I hover File > New, there isn't any menu to select (as the usual Java Project, C++ Project etc.), only an unselectable text like this:
< No Applicable Items >
Anyone know what causes this?
nitind's answer above helped solve my problem. I was using eclipse java ide juno on windows and i could not see any items under File -> New or under Window -> Show View. I noticed eclipse had defaulted to using the Java-EE perspective. Following nitind's suggestion I changed it to the Java perspective and can now see all the menu items. thank you!
I had the same error when i first started the program, but i looked into it, and I saw that the workspace already had .cpp and compiled files in it which i had compiled earlier with a different program. To fix the error, I just changed the workspace to the default, and it worked fine.
I was using eclipse CDT Kepler with java 1.6.0_27. I then tried it with java 1.7.0_25 and eclipse Juno and this method resolved the error in any of these instances.
Try using the default workspace and it should work.
Regards,
Nikita