alternative fix bug #921 Duplicity in package-info.java when templates are used #934
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.
@monperrus Hi Martin, here is the alternative PR for #932 as you suggested.
It is variant, which uses non abstract
JDTBatchCompiler
.FactoryCompiler
andFileCompiler
does not inherit fromJDTBatchCompiler
and they were renamed toFactoryCompilerConfig
andFileCompilerConfig
, because they are now used to configure theJDTBatchCompiler
.CompilationTest
file and folder filtering tests are commented for now. There is no support for filtering by overwriting ofcreateBatchCompiler
. I suggest to discuss how to implement it later.ExtendedStringLiteralTest
was updated. It should be OK.InputType
was changed fromenum
tointerface
. The change is compiler compatible so source code of the clients does not have to be changed. Just recompiled. Implementation of theInputType
can configureJDTBatchCompiler
before the compilation is started.So we have standard defaults, but now they can extend and use different configurations if needed. I use it internally instead of InputType.UNIT, I am using