Exclude org.jenkins-ci:task-reactor from enforceBytecodeVersion

[jglick]

After jenkinsci/lib-task-reactor#2 in 2.105, plugins using java.level=7 need this in order to build.

@reviewbybees

[daniel-beck]

@jglick Is there a real use case to be java.level=7 when you're 2.105+?

[oleg-nenashev]

@jglick Do you mean the build on CI when you specify jenkinsVersions? If yes, my suggestion would be to to modify Pipeline Library a bit to automatically set java.level according to the target version. Modifying Plugin POM just to workaround it seems to be lame

[oleg-nenashev]

🐛 if I understand the use-case correctly. Instead of that, java.level should be defined accordingly to the Jenkins core. We could just add a profile to plugin-pom, which bumps java.level if jenkins.version is beyond 2.54

[oleg-nenashev]

Well, there is no trivial way to implement my suggestion above, will think about non-trivial ones

[jglick]

there is no trivial way to implement my suggestion above

No, there is not. This is the only practical solution. And it is harmless—the dep is picked up from core, so the plugin cannot be doing anything wrong.

See #91.

[oleg-nenashev]

🐝 since there is no quick ways to do what I propose