-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
DefaultAggregatorBuildContext test doesn't actually test if output is removed #15
Comments
Are you asking about recreation of deleted aggregate output or about aggregate output cleanup when there is nothing to aggregate? I don't have strong opinion about recreation of deleted aggregate outputs. If you feel strongly about it, please provide a unit test for the behaviour you expect. Empty aggregate output cleanup, I am not sure either. Currently aggregate outputs are always created, but maybe there should be a flag to specify this. DefaultAggregatorBuildContextTest.java:93 is a typo, need to change the comment to "removed input". |
…15) Adding output files preemptively to processed/modified output files list would cause "No such file or directory" exceptions, if the file is not at all going to be created after the builder execution. Signed-off-by: Saravanakumar A. Srinivasan <[email protected]>
…15) Adding output files preemptively to processed/modified output files list would cause "No such file or directory" exceptions, if the file is not at all going to be created after the builder execution. Signed-off-by: Saravanakumar A. Srinivasan <[email protected]>
See DefaultAggregatorBuildContextTest.java:93. It claims to remove the output file, but it actually removes an input file.
Removing an output file does work, but it's worth noting that it doesn't look like you have anything that actually tests it explicitly for the aggregator.
The text was updated successfully, but these errors were encountered: