Android string and layout editors in Eclipse-ADT frequently crash - eclipse

I recently started programming for Android using the Eclipse ADT. What I am frequently observing is, that when I open some Android .xml file (e.g. res/strings.xml or some res/layout/<...>.xml file) that there are NullPointerExceptions.
One can then still edit the file in source mode, but the convenient Resources-tab or the Layout-tab, resp., remain empty. That's especially happening when opening .xml files created by others. E.g. I downloaded and imported the eclipse project found here (http://www.designerandroid.com/?cat=4) and imported the downloaded eclipse project into Eclipse (Helios).
When I open the strings.xml file or any of the layout files, none of the special views (Resources or Layout, resp.) works! Are these ADT views really so brittle or is my setup somehow false or corrupted?
Michael

It is a defect of ADT. See here:
http://code.google.com/p/android/issues/detail?id=8173
I got the same problem when upgrading my WST to a newer version than the one ADT was using.
BTW, Helios is quite new for ADT. The official Android developer site recommends that you should stick with Eclipse 3.4 or 3.5 for now.

Related

Problems creating a project with CodenameOne in Netbeans

Install Netbeans 12.6 on a Windows 10 machine. I was able to install the CodenameOne plugin with no problem. When creating a project I get the following error message:
Cannot invoke "org.openide.filesystems.FileObject.getFileObject(String)" because "folder" is null
I've been surfing the internet and can't find a way to fix it.
Thank you for your support.
This approach is no longer supported. The plugin is only used for legacy applications and no longer works in newer IDEs due to breaking changes in almost all IDEs.
Starting with Codename One 7.x we moved to maven projects which don't require the plugin and can be created in https://start.codenameone.com/
I have followed the instructions in the manual and it mentions as important:
"Before opening the project in NetBeans, you need to copy the contents of the tools/netbeans directory into the root project directory. These files are required by NetBeans to build, run, and debug the project correctly. "
But I can't find this folder in netbeans version 12.6.

Update Eclipse plugin from 2.x style to 4.x style (plugin.xml to manifest.mf/osgi bundle)

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?

Missing "New Haxe Project" in FDT Free

I've just downloaded the FDT IDE Free version from its website. I wanted to use it for Haxe development so at first startup I chose to develop Haxe projects only. However in the "New FDT Project" window I cannot find the Haxe project templates:
I added the Haxe and Neko paths in the preferences but it didn't solved it. I also tried to add them in the "Installed SDKs" tab but I got an error stating that it couldn't find SDKs in that given folder. My last desperate try was to extract a new FDT application and set it that I want to develop AS and Flex applications too but no luck. I still cannot create Haxe projects.
However what is wierd that the version of FDT is around 1.x.x.x:
But as far as I know the latest version is 5.5. Does the free version have separate versioning or I managed to download an outdated version? If the last is true then I don't really know where could I get the latest release since as mentioned above, I downloaded it from the official site.
The same goes for using FDT as a plug-in in an Eclipse Juno installation. Haxe projects are missing there too.
Checked the AppData folder of FDT, and there are Haxe project templates but no Haxe project type:
I originally downloaded the win64 version, but already tried the win32 version and still no Haxe project.
Chatted with tech support at FDT. Apparently, minor bug in the project template configuration files that will be fixed with an upcoming release.
Unsure where they are on non OSX platforms, but for the mac, they are in:
~/Library/Application Support/FDT/projectTemplates2/haxe/*/description.xml
Edit the files and change the 'version' tag from 2.7 to 2.8. Then relaunch FDT and the Haxe project templates will display.

AbstractUIPlugin error and Missing tabs in plugin.xml from eclipse

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.

what is the correct version of Eclipse for Coldfusion?

Usually when one wants to create a new file in the Eclipse IDE , Java, Javascript, Colsdfusion PHP etc are provided as the options for the new files.
I recently downloaded Eclipse for Coldfusion 8 and excecuted the file "software/dw/java/europa/J2EE-SDK-Europa-33-win32.zip" .
Now when I want to create a New File "only JAVA " option is available. There is no coldfusion or HTML!
So can any one provide me the Exact/correct link for Codfusion related Eclipse?
(On the Eclipse website there are many Eclipse related downloads but I am not sure which one is specific for Coldfusion.)
There's CFEclipse, a free, open-source Eclipse plug-in for working with CFML. And of course there's Adobe's ColdFusion Builder, a commercial product that works as either a plug-in for an existing Eclipse installation, or as a full stand-alone product (with Eclipse already baked in).
CFEclipse 1.3.6, the current stable version, works with Eclipse 3.4.x or 3.5.x. Here's the CFEclipse wiki.
The stated Eclipse versions required for ColdFusion Builder are 3.4.2 or 3.5. Here's Adobe's requirements page.
If you're using one of these as a plug-in and you don't need a lot of the other Eclipse features, the J2EE version of Eclipse is probably overkill (it's the biggest package). You can try out a more minimal Eclipse install, then update and add plug-ins as you need them. Try the Eclipse Platform Binary, for example.
There's also Adobe's ColdFusion Builder IDE specially created for this purpose. It proposes some features not available in CFEclipse, but not free (though there's a trial version available).
In addition to Ken's answer please note that you can already use preview builds of CFEclipse with latest Eclipse 3.6 Helios. I am using this configuration on daily basis and it is pretty stable and more efficient than previous version for me.
If you will expierience problems with preview builds, feel free to post them into the CFEclipse groups, developers usually react pretty quickly.
One more hint for you. Sometimes after installing the plugin via Add Sofware further updates do not work correcly. I've experienced this issue few times so it can be useful to know the solution.
To fix this check the Preferences > Install/Update > Available Software Sites. If needed entry missing -- create it manually using the same update URL as for installation.
Also there's an Eclipse-based version of Adobe CF manual available, see this help page for details.
Hope this helps.