Build jps-builder using only Java 1.6 compatible .classes #323
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #290
Fixes #293
Fixes #295
Fixes #302
Fixes #313
Changelog
Bug Fixes
In IntelliJ 14.1, all of
openapi.jar
targets Java 1.6 (withMAJOR.MINOR
50.0
), but in IntelliJ 2016.1, some ofopenapi.jar
targets only Java 1.8 (withMAJOR.MINOR
52.0
), sincejps-builders
require parts ofopenapi.jar
and must target Java 1.6 even for IntelliJ 2016.1, the52.0
.class
es needed to be ported intoorg.elixir_lang.jps.builder
, so that the52.0
version inopenapi.jar
wouldn't be attempted to be loaded.This ended up being 5 classes:
ExecutionException
GeneralCommandLine
ParametersList
ParamsGroup
ProcessNotCreatedException
Only
GeneralCommandLine
was used directly, all others are dependencies of it.Thanks
Thanks to @cedriessen for pointing that all the weird loading bugs were related to ignatov/intellij-erlang#727 and then @ignatov, @deadok22, and @chashnikov for helping from that issue.