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
Gradle instrument plugin does not support other jvm languages #731
Comments
@IzzelAliz feel free to send in a PR to close this |
@IzzelAliz is there more than making the classes dir of the plugin configurable? |
@ipolevoy, I would offer a PR. I.e. making the classes dir configurable. Or is @yanchevsky going to fix this? |
@cschabl go ahead, I think @yanchevsky is buried in work now . |
@ipolevoy, @IzzelAliz, there is nothing to change in the gradle plugin. With some Gradle scripting you can tell the ActiveJDBC gradle plugin to instrument your Scala classes:
The ActiveJDBC plugin doesn't support both Java and Scala model classes, because it supports a single classes directory. |
@cschabl the Gradle plugin migrated to https://github.com/cschabl/activejdbc-gradle-plugin, does it make sense to migrate this issue as well? |
@ipolevoy , as for support of Scala you can close this issue with "won't fix" and link to the migrated Gradle plugin, because it supports Scala. But it doesn't support Kotlin like the Maven plugin, so far. |
@cschabl makes sense, closing. For those interested in Scala support, use https://github.com/cschabl/activejdbc-gradle-plugin |
The plugin will use java's output dir as default dir, and the compiled scala classes cannot be instrumented.
The text was updated successfully, but these errors were encountered: