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.
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
add [sbt-test] [java-codegen-app] #35
add [sbt-test] [java-codegen-app] #35
Changes from 1 commit
78a3535
97ed70a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be
managedSourceDirectories in Compile
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't have context on why this construct was chosen, but as managed seems to be the way to go, considering the linked issue, probably yes.
As this is just in the scripted tests, I wonder what the actual impact is -- maybe accumulating cruft when folks run the scripted tests locally?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The reason I questioned it is because I saw it from the linked issue and it confused me as I was trying to figure out what to do in my own project. I wanted to make sure there wasn't a reason for doing it this way
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I saw your contribution to the thread -- I must admit I don't really understand the distinction myself. I'm really only drawn into sbt-guardrail when something actively breaks, as there's still much to do in the primary repo.
Looking at sbt/sbt#4654, it seems as though
managedSourceDirectories
really is the correct thing to do, though due to the simplicity of these tests (not integrating with any other plugins) I don't think there's a huge material difference to these tests.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, I hadn't realized this was test code, but as long as the tests are passing it doesn't matter. For reference, "managed" means it's generated code whereas "unmanaged" is just regular user-written code
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In that case, it should be changed for correctness, thanks for bringing it up!