I'm serious. I installed the Blackberry web developer thing for eclipse (being stupid, and not seeing the 'web' part). Then, when I realized my mistake, I went and got the JDE for Eclipse. I went through the install process....open up Eclipse...and I'm lost. I don't know how to run code...or the simulator, or anything.
All the tutorials I'm finding are referencing an older "beta" version of the Eclipse plugin, which apparently had a "Blackberry" menu option. I'm not seeing that.
I found some sample code, which gives the helpful instructions:
"1. Extract HelloWorld_incomplete.zip
2. In the IDE, open the helloworld.jdw workspace
3. Open the helloworld.java source file.
"
...I've never seen a .jdw file before. If I try opening it in Eclipse, I get a not-very-useful text file. Since they say it's a workspace, I try the "Switch Workspace" option in Eclipse, which lets me pick a folder, rather than a file.
I'm pretty sure "Import Project" isn't right, either.
So, I figure I'll deal with that later, so I open up the source code (a standard .java file, with a main, etc). I try running it, but it asks for an Ant build file.
I can run standard Java files just fine (that is, I know Java is in my path).
I don't know if maybe I don't have the Blackberry part right...or if it's on the eclipse side where I'm failing.
Does anyone have any ideas?
-Jenny
Edit: Just to be sure, I tried downloading the plugin through eclipse with their provided link (http://www.blackberry.com/go/eclipseUpdate), but eclipse says that it got a .jar file when it was expecting a .zip file, and so it errored. Can you even unzip a jar file (like Eclipse is trying to do?)
It sounds like you have the wrong package.
I installed it yesterday from the "Download Now" button at http://na.blackberry.com/eng/developers/javaappdev/javaeclipseplug.jsp
and it had both the menu option and the Blackberry project type.
It should have an installer if you get the correct one. I would post a direct link, but RIM likes to ask for your info before allowing the download.
Try installing it to a different directory and using a new workspace. It could be that the old install is interfering somehow.
-Hope that helps
if you want to know step by step to install the jde plugin in eclipse you can visit http://learn.virtue-software.com/2011/05/quick-start-creating-blackberry-application-with-eclipse/
Related
Recently I pulled a project form Github. The language I'm working with is C. When I try to run it, it will say "The selection cannot be launched, and there are no recent launches." I can't compile either. So what I did was search the internet for how to fix this. And the mighty internet said I shall change my run configurations and select my project and then run that. This is what I tried - I opened the configurator and browsed for my project, but it wasn't displayed. I can see the project in the navigator and I can commit/push/pull as well. Still, I can't choose it in the run configurator. Any ideas what I could do?
Thank you very much!
PS: I already saw this post (Can't run project in Eclipse imported from Git) but there is no maven option when importing.
I am trying to learn about native Android, using NDK.
I find some sample projects in NDK folder and on the Internet. After much configuration, they are runnable.
But, my problem is: when I open a .c or .h file in JNI folder with Eclipse (just want to see what it is), Eclipse shows many error in this file. For example, it don't know what is JNIEnv, jobject, jstring.
I haven't made any change in the project, just opening it. Errors mean I can't rerun it again except if I delete it from the workspace then reimport it.
Eclipse does not work well with C/C++ files. At least, for me it did not.
After some search, I have managed to configure Code::Blocks to support NDK, please see this answer to the question:
Need a simple Linux C++ IDE (Android NDK) .
I'm trying to get the GNATbench plugin to work with Eclipse. I put the plugin and feature files in the correct places. I restart Eclipse and I am now given the option to create a new Ada project but when I try to do it I get this error:
The selected wizard could not be started. Plug-in com.adacore.gnatbench.cdt was unable to load class
com.adacore.gnatbench.ui.internal.wizards.NewAdaProject. An error
occurred while automatically activating bundle
com.adacore.gnatbench.ui (235).
Any idea what is causing this?
This is the issue you'll see if you attempt to use GNATbench with the 64-bit version of Eclipse. As the system requirements note in the readme, it's only compatible with the 32-bit version. I just did a quick test, which confirmed the issue.
I checked the README file of this plugin, it says this is required:
"C/C++ Development Tools (CDT) plug-in for Eclipse 3.5.x or 3.6.x"
Have you installed that?
The other important thing is that the downloaded archive file is actually a P2 repository installable file. In this case I would unzip a new eclipse (or remove manually the related plugins you copied over, this is the hard way), start it, click on help/install new software, click add, select archive, point to your downloaded GNATbench zip file, select the 2 features appearing on the avail "software" list and continue the wizard normally (next, finish...). If there is a version problem the wizard should "validate" it.
There was a plugin for Ada called Hibachi, IIRC... I'm not sure where it stands on development or completeness though.
I'm trying to use IntelliJ IDEA for GWT development on Mac OS X, and checked out a project from subversion a coworker created on Windows. The Project file came with paths to GWT ("C:..."), which obviously don't work for me.
When I change the GWT facet path in the Module Settings dialog it complains that the directory i've chosen isn't a valid GWT SDK folder because it's missing gwt-dev-mac.jar
But I can't find such a file anywhere on my machine.
When I rename "gwt-dev.jar" to "gwt-dev-mac.jar" and try to run the project, I get the error: "Unknown argument: -style" when it tries to run GWTShell.
I read this link, but I'm not sure what to do about it: http://youtrack.jetbrains.net/issue/IDEA-26017
What's going on here?
I'm dumb... when I updated IntelliJ I dragged the new application into my applications folder and assumed it would replace the old one.
It appeared with the typical greyed-out look because I hadn't started it yet... so I was still using IntelliJ 8.something. and not noticing.
Problem solved with version 9 with the addition of the "Fix" and "Create Artifact" features that appear where the error used to.
I downloaded Eclipse Classic off of the Eclipse website then the Lua Eclipse IDE plugin. I followed the install instructions but Eclipse doesn't seem to recognize or be able to understand lua files. Can someone help?
Sounds like your file types aren't associated. Click on Window/Preferences and select General/Editors/File Associations.
Add more information
Which installation guide did you follow? (Lua Eclipse Installation?)
Which OS (version)?
Which java version? (Which implementation)
Which eclipse version?
I love these kind of questions because they provide an opportunity to do a test I postponed until now...
So I downloaded the plugin package, and followed the instructions: closed Eclipse, put two jar files in the plugin folder, put the open-ldb.exe elsewhere, restarted Eclipse.
I created a generic project, added a generic file linked to an existing Lua file. When I opened the file, it was automatically identified as such, with a moon icon and correct syntax highlighting.
Using Eclipse 3.5.1 on Windows XP, BTW.
Now, I have an issue, the debugger won't start for me, I get a
Unable to connect to PDA VM
Connection refused: connect
error, not sure why (path to exe file is correct, I have another error when it is wrong).
But at least I have the Lua files recognized without problem.
I think you might want to check that in Preferences > General > Editors > File Associations, *.lua is defined and associated to the Lua editor.
Instead of opening a File you have to do the following:
Open a new LUA project.
Then import using 'File System' all files (resources and LUA files) into the project.
Now you can see and edit the LUA files. Don't know why it doesn't work by simply opening a LUA file directly.