Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade to Java 17 #1795

Closed
Tracked by #166
jo-elimu opened this issue Jul 29, 2024 · 0 comments · Fixed by #1800 · May be fixed by #1794
Closed
Tracked by #166

Upgrade to Java 17 #1795

jo-elimu opened this issue Jul 29, 2024 · 0 comments · Fixed by #1800 · May be fixed by #1794
Assignees

Comments

@jo-elimu
Copy link
Member

jo-elimu commented Jul 29, 2024

Upgrade from Java 11 to 17.


@jo-elimu jo-elimu self-assigned this Jul 29, 2024
jo-elimu added a commit that referenced this issue Jul 29, 2024
@jo-elimu jo-elimu linked a pull request Aug 1, 2024 that will close this issue
jo-elimu added a commit that referenced this issue Aug 1, 2024
jo-elimu added a commit that referenced this issue Aug 2, 2024
#1795

Use `maven-war-plugin` 3.4.0 instead of 2.2

Possible fix for build failure:

```java
Error:  Failed to execute goal org.apache.maven.plugins:maven-war-plugin:2.2:war (default-war) on project webapp: Execution default-war of goal org.apache.maven.plugins:maven-war-plugin:2.2:war failed: Unable to load the mojo 'war' in the plugin 'org.apache.maven.plugins:maven-war-plugin:2.2' due to an API incompatibility: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Cannot access defaults field of Properties
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant