Tag Archive: Eclipse


Evidently someone forked one of the not-updated in  a while mylyn connectors for Bitbucket and fixed it. Installation Instructions are at here.

Have you seen that dreaded aapt error? if you have an older machine and only 4 gig ram and run Linux you will see this error when Eclipse attempts to fork to do the aapt process. Some solutions have you mess with certain process flags or swap, but my solution is easier and no side-effects.  Just switch from using Chrome to the Mozilla browser.  Several tabs open only takes up 200 megs or less memory and do not add any other 3rd party plug-ins to the install.

Eclipse EGIT/Github Trick

Is not that extra project folder annoying? Yes, they changed egit again as you can no longer store the repo in the eclipse workspace. To get the .git metadata folder in the project folder root like github expects uncheck default location at project setup and add an extra folder above the project name. For example:

home/fredgrott/git/github/projectname

This will than allow you to store the .git metadata folder in the proper place as its not crating the repo in the workspace which is not allowed.

xGherkin-Cucumber plugin

There is a new XGherkin Cucumber Eclipse plugin based on xtext. Update site link is in the readme.

Weird eclipse ANtstuff

many developers when developing ant build scripts do not realize that the Ant standalone and the IDE ant install have different antclassloaders. Thus, when using Eclipse you cannot use the basedir variable as a value for dirname property as in the ant standalone it will work but in the Ant install in the Eclipse IDE it will not as it will default to the workspace while in the ant standalone default to the project folder.

Eclipse Log4j.properties trick

If you are moving towards using agile in developing ant build scripts and need to use Log4j to log build errors(see Log4nt) than you run into the problem of how to enable the eclipse AntClassLoader to pick up the log4j.properties file.  There is a trick to it.

Take and make a global log4j.properties file for all your projects and save it. Now zip that file. Now rename the zipped file to a jar. Now in Eclipse ant preferences run-time add the external jar into the same place as where the ant plugin is showing all the lib entries. Now when you run ant builds that use Log4j.properties and Log4j it will execute correctly and pick up the log4j.properties file to have Eclipse AntClassLoader recognize the log4 appender.

Can I shoot the M’Fers?

Yes, I really am saying that …Can I shoot you M’Fers? Do a search on java techniques and android. For example, search for aspectj and android. Now, notice how many howtos state that in an ant build you run acj or iacj after the android javac compile step. Now pick up the damn gun and shoot your M’fer ass! Why?

Because lack of knowledge of advance java techniques and java tools is a sign that you should not claim that you are a java developer. Okay, for those that do not know you set the iacj to run in the javac task or just use ant4eclipse ant task adapter to make the process easier as there is no need to run two effing compiles on the main project or a test project when using aspectj in an android project!

And really if you are already using an ant build or the IDE builder running an ant build than by god dammit the ecj is an incremental builder which can sped up an android build especially if you are using instrumental testing. Also you can set more verbose feedback options using ecj instead of the javac that comes with the Oracle JDK.

Obviously, the other component of Agile development in systems that have broken or very decoupled anti-patterns such as android is in fact Aspect Oriented Programming due to the fact that you can separate concerns, etc. Specifically TDD and BDD only affect the agility or speed of development in the test process itself not the full development process itself. Dependency Injection also affects agility of the full development process rather than just testing if you apply it to the full project rather than just testing.

Unfortunately, most firms get stuck with java developers who happen to be android developers that replace java expertise and agile expertise with knowing only  the TDD/BDD buzz words.Please can I shoot those MF’ers? Yes, there is even on the market right now one Android Developer Testing Book that makes all these mistakes. Yes, really one publisher got their head up the ass and actually gave someone money to produce such  trash.

I have put some directions on how to get Androidmock working with adt14 on-wards with eclipse here. Not too hard, you have to change two folder locations to bin/classes in your annotation processor settings in eclipse and make sure if using Android Project Libraries to add the source(bin/classes) as an extra source input in the sources tab. You should have no changes with the sdk supplied build.xml except making sure that AndroidMockRuntime.jar is in the test project bin/classes folder.

For those of us that do use the adt-addons-api-analysis plugin it has been updated for the preview of adt14.

Easy Eclipse Install

Many in the android developer world that are new to Eclipse claim that Eclipse is hard to install. Want to know a secret?  Here are the steps to an easy eclipse install.

 

1. Download the SrpringSource ToolSuite. Why? Because once the is installed, most of Eclipse is already pre-installed in that install.

2. Now, do not touch the Indigo install or use it, remember most Eclipse is already pre-installed by the STS installer.

3. For android other than installing the ADT plugin if you need something like Eclipse CDT install it.

 

That is basically it, not too hard is it? Oh and the STS 2.7.1 does eliminate the 3004 error some of you might have seen on 32-bit systems.