Meeting Scheduling (Java, Quarkus, Maven)

Assign timeslots and rooms for meetings to produce a better schedule.

Constraints

Name	Level	Description
Room conflict	Hard	Two meetings cannot be held in the same room at the same time.
Avoid overtime	Hard	Meetings should not be scheduled outside working hours.
Required attendance conflict	Hard	A required attendee cannot be in two meetings at the same time.
Required room capacity	Hard	The room must be large enough for all required attendees.
Start and end on same day	Hard	A meeting must start and end on the same day.
Required and preferred attendance conflict	Medium	Avoid scheduling a required and preferred attendee in conflicting meetings.
Preferred attendance conflict	Medium	Avoid scheduling a preferred attendee in two meetings at the same time.
Do meetings as soon as possible	Soft	Schedule meetings as early as possible in the day.
One break between consecutive meetings	Soft	There should be a break between consecutive meetings for an attendee.
Overlapping meetings	Soft	Minimize overlapping meetings for attendees.
Assign larger rooms first	Soft	Assign the largest available room to each meeting.
Room stability	Soft	An attendee's consecutive meetings should be in the same room.

Install Java and Maven, for example with Sdkman:
```
$ sdk install java
$ sdk install maven
```

Git clone the timefold-quickstarts repo and navigate to this directory:

$ git clone https://github.com/TimefoldAI/timefold-quickstarts.git
...
$ cd timefold-quickstarts/java/meeting-scheduling

(Optional) If you want to run a licensed edition (Plus / Enterprise), set up your license key first. See the Timefold license tool for instructions.
Start the application with Maven:
1. Community Edition
```
$ mvn quarkus:dev
```
2. Plus / Enterprise Edition: The profile sets up the correct Maven artifacts to run the licensed version. See the pom.xml for the implementation details.
```
$ mvn quarkus:dev -Denterprise
```
Visit http://localhost:8080 in your browser.
Click on the Solve button.

Then try live coding:

Notice that those changes are immediately in effect.

When you're done iterating in quarkus:dev mode, package the application to run as a conventional jar file.

Build it with Maven:
```
$ mvn package
```
Run the Maven output:
```
$ java -jar ./target/quarkus-app/quarkus-run.jar
```
Note To run it on port 8081 instead, add -Dquarkus.http.port=8081.
Visit http://localhost:8080 in your browser.
Click on the Solve button.

Run a container:

$ docker run -p 8080:8080 --rm $USER/meeting-scheduling:1.0-SNAPSHOT

To increase startup performance for serverless deployments, build the application as a native executable: