After migrating to Android Studio and
getting Android Annotations working, my Android app is ready for deployment as an APK. However, I realized shortly that the signing component didn’t get migrated over and I had to implement it again.
I tried to see if I can find something akin to the maven release plugin and integration with Jenkins, alas to no avail. This means that I would need to create a separate release job or do some extra programmatic configuration to
build.gradle to support this.
At the very least I am able to move the keystore configuration out of the
build.gradle and push it to a configuration file in the build server similar to the Maven settings.xml.
Continue reading Signing an APK in Gradle
One of the main reasons I got the Tassimo system was the larger variety of drinks from espressos, to teas and lattes that can be made from the device. It does not make the second best coffees possible, that title goes to the Nespresso system, but it is limited to just coffees which is why I never bothered with it in the end. Best coffees are brewed by yourself, but spending 5 to 10 minutes on a daily ritual is a chore for me, I prefer to just plop a disk and go.
I like to try out the many different choices they provide, and personally get annoyed that the US Tassimo shopping site has more choices than the Canadian one. However, to balance it out, they are missing my favorite…
Continue reading Tassimo Product Reviews
Android Annotations is one of those rare third party products I use primarily to reduce boiler plate code because at the moment, it hasn’t been standardized enough and gotten incorporated into the Android SDK proper which I think it should. This blog post continues on from migrating from Eclipse ADT to Android Studio.
Continue reading Getting Android Annotations to work with Android Studio and Gradle
Though WordPress comes with a few backup plugins in which I had varying degrees of success, I decided it was better to just do it using some git and mysqldump to do my backups because it is more well controlled and easier to deal with as there is no UI involved. This blog post details the backup strategy for www.trajano.net.
Continue reading Backup WordPress blog to github
So I finally took the time (actually it was probably my third time attempting to do this) to migrate my smallish Android app from Eclipse ADT and Maven to Android Studio and Gradle as a weekend project. The migration finally went successfully this long weekend and I have merged my fork into the main line so I am going to stop using Eclipse/Maven for my Android projects from now on as Android Studio being the official IDE now will likely get the most current updates for a while (at least that is what I am betting on).
However, if asked for my advice, I would definitely not recommend moving over to the new tooling as of yet. The new tooling just stands alone and does not play well with other tools that may have already been established on the enterprise.
Continue reading Migrated from Eclipse to Android Studio
Since code.google.com is going away soon much like the rest of the Google Graveyard there may be some projects trying to vie for a new place to call home.
Continue reading code.google.com going kaput
Sometimes when developing Oracle database apps especially with Curam there may be lingering tables that are actually not being used, but still exist. The best way of going through this is to drop the user and start again from an empty slate to ensure that there aren’t any tables that may be accidentally referenced by custom SQL statements.
Continue reading Really resetting your database
One of the key tenets of enterprise architectures is that it needs to be sustainable. Being agile is not one of the tenets and in most cases goes against sustainability of an architecture at an enterprise level. Agile Enterprise Architecture is a myth and this is where I and Cay Hasselmann host of Critical Enterprise Architecture Netcast agree upon at least on one of his episodes (I don’t know if his POV had changed recently). Enterprises do not have to be agile especially if it is not sustainable.
Delivery on the other hand is better off being agile. Software project delivery methods such as scrum help get projects in a usable business friendly state vs less agile waterfall approaches that require big document up front and heavily access controlled and managed tool sets.
Unfortunately, most large organizations get sold on the idea that everything should be standardized down to the level of the tools. In fact SEI-CMM level 3 which the big service companies promote requires it.
Continue reading Delivery vs enterprise level tooling
The Curam Runtime has two things that it needs to have executed along with WebSphere: xmlserver and batchlauncher. In order to set this up in Windows we use the nssm and the Windows Task Scheduler.
Continue reading Curam Runtime on Windows
When developing using web services, we tend have different endpoint URLs for development, test and production. When developing Java EE apps, the best practice is to separate environment configuration from the application to the deployment process (a pattern I rarely see in practice unless already architected in like Curam).
In terms of facepalm moments is when I see an application try to manage the connections to the web services rather than letting the container do it.
Continue reading Setting the endpoint for web services