first build triggers ECJ copy and breaks EXT deploy #9
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The second commit is related to the issue due to possibility of non-existent build.$USER.properties file. |
|
Hey @psporysz, One thing we've been meaning to do is create a separate EXT recipe, instead of including that functionality in the default recipe. If everything here looks good, I'm not sure if we want to merge it now, or wait until after we have the EXT recipe created and ask you to resubmit it. I'll let @einsty or @hkastler3w chime in. |
|
Hi @psporysz -- Does adding javac.compiler=modern to your build file resolve the ECJ issue? --Henry |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
At first time instead of building ext, ECJ jar is copied which breaks further steps.