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

[MCOMPILER-501] compileSourceRoots parameter should be writable #159

Merged
merged 1 commit into from
Dec 9, 2022

Conversation

gnodet
Copy link
Contributor

@gnodet gnodet commented Dec 9, 2022

JIRA: https://issues.apache.org/jira/browse/MCOMPILER-501

When using multi-release JARs, the way is to configure the plugin, see https://github.com/apache/maven-compiler-plugin/blob/master/src/it/multirelease-patterns/singleproject-runtime/pom.xml#L92-L111

This causes a warning because the parameter is set as read-only.

Copy link
Member

@slawekjaranowski slawekjaranowski left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Make compileSourceRoots read/write so that it can be used in multi-release jars without issuing a warning
@gnodet gnodet changed the title Make compileSourceRoots read/write so that it can be used in multi-release jars without issuing a warning [MCOMPILER-501] compileSourceRoots parameter should be writable Dec 9, 2022
@gnodet gnodet merged commit 5be3163 into apache:master Dec 9, 2022
@gnodet gnodet deleted the remove-warning branch December 9, 2022 17:32
@norrisjeremy
Copy link

When will there be a new release with this change applied?
The new Maven 3.9.0 release causes builds that include compileSourceRoots configurations to issue bogus warnings now.

@slawekjaranowski
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants