Apache project since 2007. During these years it has proved to be a solid and valuable solution for building enterprise web applications. Wicket core developers have done a wonderful job with this framework Wicket will always be released under Apache license 2.0 and freely available. • Wicket is a community driven project: The Wicket team supports and promotes the dialogue with the framework’s users through reuse of presentation code and GUI elements building custom components. Even if Wicket already comes with a rich set of ready-to-use components, building custom components is a common practice when working

Apache project since 2007. During these years it has proved to be a solid and valuable solution for building enterprise web applications. Wicket core developers have done a wonderful job with this framework Wicket will always be released under Apache license 2.0 and freely available. • Wicket is a community driven project: The Wicket team supports and promotes the dialogue with the framework’s users through reuse of presentation code and GUI elements building custom components. Even if Wicket already comes with a rich set of ready-to-use components, building custom components is a common practice when working

Apache project since 2007. During these years it has proved to be a solid and valuable solution for building enterprise web applications. Wicket core developers have done a wonderful job with this framework Wicket will always be released under Apache license 2.0 and freely available. • Wicket is a community driven project: The Wicket team supports and promotes the dialogue with the framework’s users through reuse of presentation code and GUI elements building custom components. Even if Wicket already comes with a rich set of ready-to-use components, building custom components is a common practice when working

Apache project since 2007. During these years it has proved to be a solid and valuable solution for building enterprise web applications. Wicket core developers have done a wonderful job with this framework Wicket will always be released under Apache license 2.0 and freely available. • Wicket is a community driven project: The Wicket team supports and promotes the dialogue with the framework’s users through reuse of presentation code and GUI elements building custom components. Even if Wicket already comes with a rich set of ready-to-use components, building custom components is a common practice when working

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 588 15.2.2. Building a Native Image Using Buildpacks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 590 15.2.3. Building a Native Image using Native Build Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . support for building efficient container images. You can read more about it here: • Efficient Container Images: Tips to optimize container images such as Docker images • Dockerfiles: Building container

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523 15.2.2. Building a Native Image Using Buildpacks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 15.2.3. Building a Native Image using Native Build Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . support for building efficient container images. You can read more about it here: • Efficient Container Images: Tips to optimize container images such as Docker images • Dockerfiles: Building container

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 523 15.2.2. Building a Native Image Using Buildpacks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 525 15.2.3. Building a Native Image using Native Build Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . support for building efficient container images. You can read more about it here: • Efficient Container Images: Tips to optimize container images such as Docker images • Dockerfiles: Building container

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 513 15.2.2. Building a Native Image Using Buildpacks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515 15.2.3. Building a Native Image using Native Build Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . support for building efficient container images. You can read more about it here: • Efficient Container Images: Tips to optimize container images such as Docker images • Dockerfiles: Building container

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 512 15.2.2. Building a Native Image Using Buildpacks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 514 15.2.3. Building a Native Image using Native Build Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . support for building efficient container images. You can read more about it here: • Efficient Container Images: Tips to optimize container images such as Docker images • Dockerfiles: Building container

. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 536 15.2.2. Building a Native Image Using Buildpacks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 538 15.2.3. Building a Native Image using Native Build Tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . support for building efficient container images. You can read more about it here: • Efficient Container Images: Tips to optimize container images such as Docker images • Dockerfiles: Building container