-
Notifications
You must be signed in to change notification settings - Fork 275
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
Intellij source folder should be marked as generated #222
Comments
I guess this is why you have a TODO in the code : |
Yeah, that is still marked as "incubating" in the gradle doc. Simple workaround is add it yourself in your gradle build:
|
Right, the only reason they are not marked as generated is because that API is unstable. Out of curiosity, is this causing any issues for your IDE workflow? |
quick ping on this issue. having to mark individual source folders is difficult for a large project w/ multiple proto sources. |
Would it be possible to add an option to protobuf plugin to optionally use this incubating API? |
@zpencer: As of Gradle 5.0 this is no longer an incubating API, would you consider checking Gradle version and switching to generated sources? As for UI reasons, it does not break anything per se, but generated sources are shown/sorted differently in UI. It makes it easier to distinguish between "real" application code and "generated". |
I don't have cycles to work on this plugin at the moment but PRs are welcome as usual :) |
@zpencer Would it be ok to just enable it? Or do you want me to check Gradle version and only enable it if 5.x is detected? |
I think the safest way is to make sure the gradle version is at least 5.0. There may be users of the plugin at lower versions. |
Closing, this should have been fixed by #477. |
Currently source folders in the Intellij configuration are not set as generated :
<sourceFolder url="file://$MODULE_DIR$/src/generated-sources/main/java" isTestSource="false"/>
See https://www.jetbrains.com/help/idea/creating-and-managing-modules.html#folder-categories for context
The text was updated successfully, but these errors were encountered: