-
-
Notifications
You must be signed in to change notification settings - Fork 77
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
[JENKINS-54828] - Support building plugins with java.level=11 #133
Conversation
@oleg-nenashev conflicting now #134 was merged FYI. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand the need for 1.${java.level}
but it might because confusing at some point.. I guess we have no choice but to keep it that way.
ASM 7.0 (and 7.1) have been released by now. |
This seems to have been abandoned. Anyway has it not been superseded by other work? |
No, this PR is still actual. But it is stale indeed
…On Fri, May 24, 2019 at 4:08 PM Jesse Glick ***@***.***> wrote:
This seems to have been abandoned. Anyway has it not been superseded by
other work?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#133?email_source=notifications&email_token=AAW4RICXKLIU7FGIOJWAY6DPW7ZGJA5CNFSM4GGD6VK2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWFPF2Y#issuecomment-495645419>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAW4RIDDXWF4AM3WGJFFRYTPW7ZGJANCNFSM4GGD6VKQ>
.
|
<id>java-level-11</id> | ||
<activation> | ||
<property> | ||
<name>java.level</name> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
you can not activate properties like this. It requires you run maven with mvn -Djava.level=11
as it can only look at system properties - not properties defined in the <properties>
section of the XML
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not a big concern for me (whatever works if it is theoretically supported)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the problem is it doesn't work if you have a reactor with a mix of things - you need to move everything in one to java11 (the reactor may not be the parent and all the plugins could come from different repositories with different release cycles)
Seems to be abandoned. |
Still relevant |
#478 might be more relevant? 😅 |
Might be. AFAICT we still have no consensus |
I think we can just merge #478 as soon as core drops java 8. |
This is obsolete. |
WiP version of the
java.level=11
support for building plugins. So far it does not quite work.Upstream deps/issues:
@jenkinsci/java11-support