You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 9, 2022. It is now read-only.
Specifically, outputs directories added to the SourceSetOutput should be added to the compile classpath.
Example from reference:
sourceSets {
main {
//let's register an output folder on the main SourceSet:
output.dir(generatedResources, builtBy: 'generateMyResources')
//it is now a part of the 'main' classpath and will be a part of the jar
}
}
In the example above, the folder is never added to Gradle Dependencies.
This seems to work as expected in the latest Eclipse Plugin, but this needs to be run on CLI.
Thanks
Edit: just to help narrow things down: this seems related to "Dependency Management". Turning this off makes it use the Eclipse plugin (if applied) and works nicely.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Sorry I don't really want to create ANOTHER account on another forum for another bug tracker.
It seems that this integration plugin does not handle SourceSetOutput in the same manner as the Gradle Eclipse Plugin.
SourceSetOutput Referennce
Specifically, outputs directories added to the SourceSetOutput should be added to the compile classpath.
Example from reference:
In the example above, the folder is never added to Gradle Dependencies.
This seems to work as expected in the latest Eclipse Plugin, but this needs to be run on CLI.
Thanks
Edit: just to help narrow things down: this seems related to "Dependency Management". Turning this off makes it use the Eclipse plugin (if applied) and works nicely.
The text was updated successfully, but these errors were encountered: