This is an empty project, with a pre-configured Gradle wrapper. This makes the project buildable without the need of locally installing Gradle. To execute the build, use:

gradle build

To clean up the previous build results and start fresh, use instead:

gradle clean build

You can use the IDE of your choice, but you can also just work

This lab should be performed in groups of 2-4 people, each with her own PC, in order to exercise the basics of teamwork with git. Form a group, and elect a project leader randomly (e.g. using the Scala REPL to throw a random number). Every member of the groups must have a GitHub account.

The project leader should fork this repository. The resulting repository will be the "truth repo". Every other member should fork the "truth repo".

Each member should configure the project for working with git flow and create a develop branch.

Each team member, working on develop, must create a Java class in the src/main/java. There must not be any name clash among team members. Each member must configure the build.gradle file in such a way that gradle clean build will correctly create a build folder with the class files compiled.

Each member must now sign up on Travis CI, connect its GitHub account, and enable the build for the repository. Now, each one must create a valid .travis.yml file, and push it. If the procedure has been performed correctly, a build will start on Travis CI, and complete successfully.

Each member must now create a pull request from their develop branch towards the "truth repository" develop branch. The project leader must comment and ask a change for each of them (add Javadoc, or any other change). The developers must comply, and update their pull request (pushing the changes locally should suffice)

From now on, each developer must pick a feature from the following list, create a feature branch locally, implement it, and contribute back to the develop of the truth repository.

• Add a Scala source code and configure the build.gradle appropriately
• Import tuProlog as a dependency from Maven Central
• Write a Scala class that uses the new tuProlog dependency
• Write a JUnit test, make it fail first, see what happens to the build. Then fix it.
• Write a Java class that uses Guava's Multimap (import Google Guava from Maven Central)
• [Multiple] Write a Scala test using each one of the frameworks presented in the previous lab
• Configure Gradle to generate the Javadocs
• Add a Groovy source and configure the build.gradle appropriately
• Add an Xtend source and configure the build.gradle appropriately
• Configure Gradle for using PMD
• Configure Gradle for using FindBugs
• Configure Gradle for using Checkstyle
• [Advanced] Using the Travis CI, documentation, configure a deployment on .travis.yml to automatically deploy the generated jars to GitHub releases