Jitter workshop event is a part of Mobile Central Europe Conference. It is a one day event full of attractions. Each workshop is repeated, so you can attend to two different workshops.

So why, you should attend Jitter?

• You can meet cutting edge technology like Emberlight or Wunderbar.

• You can co operate with you new friends to do amazing stuff.

I have an opportunity to take part in “Cardboard Design” workshop, where mentors where Wiesław and his friends. 

We were working in groups. Our goal was to visualise music using arduino, few servomotors and of course cardboards. We totally unleashed our imagination. Effects was amazing. We have used 100% of our creativity.

Besides that, event took place in a film studio. Raw and unpolished style. It give me more energy to work. But, there was a few defects. It was loud and cold, but organisers do everything to minimize those effects.

I am definitely looking forward for next Jitter on next year MCE

There is a time in your project when you start using Gerrit code review system. When you have maven release plugin to make release, you can be very surprised when you see:

1
2
3

[ERROR] The git-push command failed.  
[ERROR] Command output:  
[ERROR] Permission denied (publickey).

This is a situation when we use ssh connections to gerrit. But, when you try to push something to master (ignoring code review), it works! How is that possible?

You probably have in your gitconfig an ssh URL with your user name. But in your project SCM (in pom.xml) you do not have your user name. What user name maven release plugin use? Your computer account name, which is in most cases different than your Gerrit user name.

How to repair it? Define a file in .ssh/config directory with content:

1
2
3
4

Host gerrit  
    HostName YOUR_GERRIT_HOST  
    Port YOUR_GERRIT_PORT  
    User YOUR_GERRIT_USER_NAME

There may be a lot of other reason why you have Premission denied, but this was the hardest I’ve ever seen.

In my team, there is 20% of OS X machines, rest are linuxes. We share one script, that everyone on our team uses.

That script was written by some guy on Ubuntu and guess what? GNU versions of those programs (sed and xpath) are not compatible with BSD versions. The script was failing :(

I was trying to improve the script, but forget about it. Just use GNU programs.

To install gnu sed on osx via homebrew type the following:

1

brew install gnu-sed --with-default-names

To install gnu xpath on osx via homebrew type the following:

1
2
3
4

brew tap concept-not-found/tap  
brew install xpath  
mv /usr/local/bin/xpath /usr/local/bin/osx.xpath  
sudo ln -s /usr/local/Cellar/xpath/1.13-7/bin/xpath /usr/local/bin/xpath