You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by "Karl Pauls (Jira)" <ji...@apache.org> on 2022/02/15 10:46:00 UTC
[jira] [Resolved] (SLING-11144) Compiler does not create classfiles if compilation of unrelated compilation unit fails
[ https://issues.apache.org/jira/browse/SLING-11144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Karl Pauls resolved SLING-11144.
--------------------------------
Resolution: Fixed
> Compiler does not create classfiles if compilation of unrelated compilation unit fails
> --------------------------------------------------------------------------------------
>
> Key: SLING-11144
> URL: https://issues.apache.org/jira/browse/SLING-11144
> Project: Sling
> Issue Type: Bug
> Components: Commons
> Affects Versions: Commons Compiler 2.4.0
> Reporter: Karl Pauls
> Assignee: Karl Pauls
> Priority: Major
> Fix For: Commons Compiler 2.5.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> SLING-7111 made it so that we (correctly) don't write out classfiles resulting from failing compilations - however, it was too aggressive in that it just stops to write classfiles altogether. That is fine if there was only a single compilation unit to begin with. Otherwise, it is a mistake as now, assuming multiple compilation units, it depends on when the failing compilation unit gets processed.
> We should only not write the classfiles for the compilation unit that failed and proceed for the other compilation units.
--
This message was sent by Atlassian Jira
(v8.20.1#820001)