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

prevents "bootstrap class path not set in conjunction with -source 8" #206

Closed
wants to merge 1 commit into from

Conversation

JerryShea
Copy link
Contributor

No description provided.

@@ -644,6 +644,16 @@
<mockito.version>5.5.0</mockito.version>
</properties>
</profile>
<profile>
<!-- prevents "bootstrap class path not set in conjunction with -source 8" -->
<id>set-compiler-release</id>
Copy link
Contributor Author

@JerryShea JerryShea Dec 28, 2023

Choose a reason for hiding this comment

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

please see the profile above this ("java11") created by @peter-lawrey

@peter-lawrey I don't understand the purpose of the above profile so need you to review this change. I have made my change next to yours, but please see below.

Why are we not affecting maven-compiler-plugin in a profile in java-parent-pom?

Copy link
Member

Choose a reason for hiding this comment

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

I suspect the line you are overriding should just be removed instead. Testing this locally.

Copy link
Contributor

Choose a reason for hiding this comment

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

If we include JDK11 in this new profile then the existing above should be changed to <jdk>(11,</jdk> at least ?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@peter-lawrey I tested this change with one of the demos and it worked like a charm. I am keen to get this merged

Copy link
Member

Choose a reason for hiding this comment

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

This was solved in x.26 by setting -Xlint:-options

Copy link
Contributor Author

@JerryShea JerryShea Mar 29, 2024

Choose a reason for hiding this comment

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

Why have -options when instead we can do this and fix it properly, and we dont have to wait for x26?

Some projects have -Xlint:all and we should be aiming for this for all projects right?

@JerryShea JerryShea changed the base branch from develop to maven-target-profiles April 1, 2024 03:49
@JerryShea
Copy link
Contributor Author

@yevgenp your #222 PR supersedes this but basically just moves the compiler release stanzas to root-parent-pom?

@JerryShea
Copy link
Contributor Author

#228 solves these problems with -Xlint:-options

@JerryShea JerryShea closed this May 13, 2024
@JerryShea JerryShea deleted the feature/set-compiler-releae branch May 13, 2024 07:59
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 this pull request may close these issues.

None yet

3 participants