Updated: December 25th, 2011
As a developer, I both love and hate Eclipse for its chaotic nature, buggy and sometimes unusable interface, but at the same time incredible usefulness and ability to serve as a single tool for all of my development, be it C++, PHP, Java, Android, Perl, etc.
One of the biggest problems with Eclipse is that there is no clear upgrade path from major versions, for example 3.5->3.6. What I ended up having to do for years is back up the old release, download and unpack the new release, and then try to migrate all the settings by importing and exporting left and right. Not so pleasant.
Turns out, as of Eclipse 3.3 (though I've only tried it with Eclipse 3.5), …
In this article I will describe the problem I've had with Eclipse's handling of XML file formatting as well as the best way to fix it.
I use Eclipse to do my Android development for a few reasons:
- it's the only IDE fully supported by the Android dev team
- it has a visual Layout/Resources builder that transforms XML files into corresponding visual representations
- it's free and open source
- I've been using Eclipse for many years and am very familiar with it
The Problem
However, one thing about Eclipse Android development has bothered me for a while …
beer planet is a blog about technology, programming, computers, and geek life. It is run by Artem Russakovskii - a local San Francisco geek who is currently pursuing his own projects and regularly enjoys hacking Android, PHP, CSS, Javascript, AJAX, Perl, and regular expressions, working on Wordpress plugins and tools, tweaking MySQL queries and server settings, administering Linux machines, blogging, learning new things, and other geeky stuff.
