Tuesday, October 28, 2014

Gradle support updated

After a long delay I have made a few changes to pick up Android SDK updates and newer version of Gradle plugin.

I received an interesting patch for new project wizard but it needs some polishing before it gets integrated.

Monday, July 28, 2014

Android plugin for Gradle 0.11/0.12

NBAndroid plugin version 1.249 bundles newer version of SDK tools and Gradle support that makes it working with Android plugin for Gradle 0.11 and 0.12. It also means that older version 0.10 won't be supported anymore.

Friday, May 16, 2014

Testing with flavors

Real feedback from users is always the best and helps to focus on things that actually matter. Better support for Gradle projects using flavors is one of them and there is a few bugs reported recently. The first fix is ability to run tests in these projects corectly. Actually there are two parts to this:

  • NBAndroid now correctly builds only the APK for current build variant with its test.
  • Gradle projects let you use custom instrumentation test runner like Ant-based projects.
The change is part of 1.245 version.

Friday, May 2, 2014

Android plugin 0.10

Another version of Gradle plugin is out and as usual it is followed by an update in NBAndroid. Personally I like that all Gradle versions starting with 1.10 are supported including recently released 1.12.

Sunday, April 27, 2014

Gradle with dependency on Java library project

Let me repeat it again: Gradle project are the future build system if you're developing Android applications. At the moment the trend is also visible in a reported usage of Gradle plugin.

Latest release (1.239) brings another improvement - it fixes classpath resolving if you have a multi-project setup where Android project depends on non-Android Java library. Classes from that library were not recognized in editor and related IDE parts. Thanks for the bug report.

Wednesday, April 9, 2014

Documentation updates

I've made some changes to a wiki describing NBAndroid and NBAndroid extensions based on the feedback that I'm receiving continually. The goal is to move documentation into one place and make it simpler to find the content there. This effort is based mostly on an input from the feedback form filled by users who asked for NBAndroid Extension evaluation key.

Sunday, March 16, 2014

Gradle plugin 0.9.0

Recently published version 0.9.0 of Gradle plugin for Android development brings some incompatible changes again. Most important one that affects all projects is rename of instrumentTest sourceTest to androidTest. Please check the documentation to see how to update your projects. The good news is that it now supports Gradle versions 1.10 and 1.11. And of course it is now supported in NBAndroid.

Monday, February 24, 2014

Layout preview improvements

The problem with layout rendering is the most popular bug in issues tracker at BitBucket. I am well aware of that and recently I made a few changes to again make it more robust and basically attempted to be able to render a layout with some reasonable defaults without manual setting. Still there are assumptions like:
it expects that the project is built (to load identifiers from generated R.java and possibly project/library widgets), it needs to be able to parse AndroidManifest.xml from project, it will guess what is the best target platform to use for rendering and will use a default device (Nexus 4), its state (PORTRAIT), theme and so on. You can give it another try. Reminder: the AUC link is now http://nbandroid.org/updates/updates.xml.

Unrelated to that is that I was able to improve tests to run multiple times again different versions of Android target platforms. This is nice as it helps to make sure that new updates do not break existing functionality. This is done using AbstractMultiTestRunner from Gradle project - pretty smart class.

Friday, February 14, 2014

Instrumentation test runner

I am surprised that there were no other complaints sooner but for a long time it was not possible to specify instrumentation test runner and our plugin always used the default one. Well, this is changed now and you can customize this for your Android Test projects in a 'Run' tab of project customizer.

Future improvements are possible but at least the simple support is now enabled. Adding suggestion based on AndroidManifest.xml parsing can be added. I also have to thank Rob Smith for his input on this.

Note: the updated version is available from an update center announced in previous post.

Thursday, February 13, 2014

Java 7 is required now

There are several important changes in the latest update of NBAndroid plugin:

  • Java 7 is now required as JDK used to run NetBeans. If you use NetBeans 7.4 or newer then there is no other way. If you are using NetBeans 7.3 (or 7.2) make sure your IDE is running with Java 7.
  • NetBeans 7.3 is used as base for building the plugin. It is possible that some builds will remain compatible with NetBeans 7.2 but sooner or later some dependency will break this. Version 8.0 is already in beta so you should upgrade.
  • Related to these news is a change in AutoUpdate URL. Please update your settings in Plugin Manager to use link http://nbandroid.org/updates/updates.xml 

Sunday, January 26, 2014

Gradle 1.10 and Android plugin 0.8

This update is very similar to previous one - NBAndroid is following the work done by Android SDK team and the latest update (1.226) uses Gradle plugin for android development 0.8. This version also requires Gradle 1.10 which is the latest and greatest of released Gradle versions.

Needless to say that this update was the smoothest so far and makes me feel that the Gradle support is getting more mature and stable.

There are a few bugs and RFE filled recently in our bugtracker that I am going to address soon. In addition to that it is likely that NBAndroid will drop support for NetBeans 7.2. It gives us a chance to migrate to Java 7 and use some new improvements in NetBeans APIs.