Simple dummy Mail Server for development

Every now and then, you come across developing an application, that sends email. How to simple test this application? It’s easy, if you have an own mail server. For Windows, there is the very simple smtp4dev application, that listens on localhost port 25 and displays all emails that would have been transmitted. A similar but cross-platform tool is FakeSMTP. For a server, fakemail might be worth a look at.


Some experiences in Android programming

I recently started developing an app for Android. The app is nothing complicated. A few screens which display data from a webservice. The data are events like “having dinner together” and you can register to join the event. As being new in Android programming (and this time, I wanted to create a “real” native Android app, not a PhoneGap / cordova based app), it’s quiet a learning experience necessary.


Branching and merging with git in PMD

This post is about, how your git history might look like, if you consequently fix bugs on branches and merge this bugfix-branches into the release branches. In this case, I used the method described earlier in “Roadmap and source code branches” in New PMD Release 5.4.0: Always create a new branch, that can be merged in the release branches, determined by git merge-base. Then, after the bugfix, merge this branch into the release branches, avoiding a fast-forward merge by using git merge --no-ff.


Sharing PMD rulesets across projects

You are using PMD in your project. After a while, you start customizing your ruleset as described in best practices and how to make a ruleset. But the project grows and grows and it soon consists of several sub modules or event separate projects maybe even living in separate source repositories. The how can you share the ruleset, so that it can be applied to each project?


Andreas Dangel | subscribe via RSS | adangel | .onion © Copyright 2019. (11 May 2019)