advantages:

• have a running, current version of jetty
• better Vaadin integration with the Vaadin plugin for Maven

all current features of the build.gradle can be covered with a Maven pom.xml

When issue #77 is finished implement the logic behind the button. It should open a dialog to choose a csv-file with student data. With the information of that file a list of student objects should be created and that list should be persisted in the database.
When the process is finished a successfull / error message should appear on the screen.

@davherrmann please assign @davvitt to this issue

The .project and .classpath files are changed quite often by eclipse - prevent the accidental commit of the files.

The view should contain all possible fields of a material and a button to save the material

see comment in styles.scss

The list which indicates how many books of a specific type are needed

If this issue is included in one of the others, I'm sorry but I couldn't find it.

@davherrmann please assign me

If this issue is included in one of the others, I'm sorry but I couldn't find it.

@davherrmann please assign me

After issue #81 has been resolved the table of the lending view should be populated with all students who have that flag.

When I use the category builder with "Bücher" as the name parameter the corresponding id (1) is not saved in the category, it is 0. You have to manually set the id to 1 to successfully insert a book into the database.
@davherrmann @davvitt

Add Home, Return, Lend, Manage Books and dunning screens.

Due to not using a special widgetset, we can use the com.vaadin.DefaultWidgetSet which comes pre-compiled. The advantage is a shorter build time.

necessary for comparing entities of the same type

follow-up question: What fields are really identifying for the entity, e.g. a Student? It can't be just the id?

Though the fields don't need to be initialised when loading an entity via Hibernate, they still need to be initialised when instantiating an entity.

assign to me.

add this line at the beginning of your class (replace CLASSNAME with actual class name):

private final static Logger LOG = LoggerFactory.getLogger(CLASSNAME.class);

Then you can call LOG.debug(...), LOG.info(...), etc.

use the builder pattern to implement builders for the rather complex entities

nested static Builder classes inside the entities

several files don't use UTF-8 encoding which leads to Maven build errors

With the buttons it should be possible to actually create a list (material list, student list and all student lists of a class). You should be able to print the generated list from the browser

The view should consists of an explaining text what happens after pressing import and an import button.
@davherrmann please assign henningmu for this issue

logback dependencies are already included, configuration still has to be done (simple logging on the command line would be enough at the moment)

See issue #82. This should use them same code / classes.

See issue #79 it should probably use the same code / classes to resolve this issue.

@davherrmann assign me please

@Junkern
When changing the views over the navbar, they shift towards the top of the browser and overlap the header

simple implementation of some views and the navigation system

build errors - hotfix: delete all classes referring to old implementation

Add ViewModel and add a PopupView with an input form to add and edit teachingMaterials

Assign me.

start and stop persist filter
bind DAOs in guice configuration module

performance and memory issues may occur when using ViewModelComposer as an eager bound singleton

@Junkern:
Build the basic main screen with header, navigation, footer and the replacable content.

Two possibilities to implement this:

1. When issue #85 is resolved use this view to edit books and save the changes with the button. Process: a table row is selected and after the click of a button the information will be passed between the views.
2. When you double click into a cell of the table it gets editable. after clicking somewhere else a dialog asks the user if he wants to save the changes made in the cell.
   A short error / success message should be shown in both cases.

The asignee should state in the comment section which solution will be implemented and open a second issue, since we need both possibilities implemented.

When issue #85 is resolved the functionality of the view has to be implemented. When you press the save button all fields should be persisted in the database and a short error / success message should be shown.

At the moment everything is done manually with string constants in the MainUI. It would be nice to have a solution where you only have to change a single file. Maybe we can use guices MapBinder or something similar.

Since the code is almost the same build a parent class / component for it.
Instead of showing a popup use the discussed animation / accordeon style for it.

When a student did not receive / return all his books this view is used to choose the one the student got / returned.
Two possibilities:

1. implement it as an additional view showing the student and its books
2. implement it as a "tree" inside the table. You show all books of the student + checkboxes in the same row of the table in the lending / return screen.

the database password should be encrypted. The last group got something like that. I have to figure out if we can copy that.

@davherrmann assign me please

A common interface simplifies handling a Student or a Parent when you only need the data concerning the actual person, e.g. the address when printing the address.

Create a loginView to show when the user is not logged in and update MainUI to make the login work.