Journal

Week 2

• Started work on API with Spring @ResponseBody.
• Stack-Overflow with JPA-Entities, @JsonBackReference and @JsonManagedReference solved it.
• iOS App which uses our API to display the users stream and implements PullToRefresh.
• Added Like/Unlike to activities.

Week 1

• We now have our own Maven repository for urbanairship-java: http://maven.farnsworth.ch/
• Auto deploy WAR after successful build

Week 52

• Rather big problems with GitHub and Xcode. Changes are only committed locally

Week 51

• Added an Architecture overview
• Updated to Spring 3.1
• Refactoring of Controller tests

Week 50

• Added Privacy Settings
• Added asking for Friendship
• Tomcat now running in the Internet: http://social.farnsworth.ch/
• Started working on a iOS App

Week 49

• Get the Activities from you as well as from your friends
• Refined the profile page
• Some refactoring(incect the current user via a listener)
• Added OpenSessionPerView Pattern

Week 48

• Started work on new design of application.
• Proposed usage of Pull Requests for unexperienced team members.
• Added profile information, incl. profile picture!

Week 47

• Started to implement the ERM with JPA
• Many-to-many relationships with extra columns in the mapping table are hard to implement with JPA
• Added custom CSS for nicer Javadocs.
• Discussions about the ERM - everyone agreed on a first draft.
• JavaDocs for multiple classes updated.
• Installed Jenkins over the weekend.
• Getting code coverage running was harder than expected, as we hit a Jenkins bug.
• mvn clean before every test run was the solution.
• changed the pom.xml to generate javadoc. Configure Jenkis was once again harder than expected.
• Controller's are now testable too. We are using the mock objects from org.springframework.mock.web.
• Code coverage is a great tool to discover dead code.
• Worried about the rating criteria in the first week - we don't have much code yet which applies to Patterns and Code-Design (one class and one test with DI).
• Maven caused problems once again, solution was to use the default configuration of maven-war-plugin.
• Starting with the implementation of the registration page.
• Proud of the implementation for hibernate. Very clean approach.
• Tests for DAO objects are using HLSQLDB.
• Lots of problem with Roger's environment in his VirtualBox.
• Start of the project, setup of all tools and documentations.
• Finding a proper task management tool which meets our requirements wasn't easy.
• Pivotal Tracker was a bit confusing in configuration, but it was easy to fill with the prepared User Stories.
• Setting up the whole project structure with maven and spring wasn't easy but it's worthwhile the time.