-
Notifications
You must be signed in to change notification settings - Fork 20
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
Disable for scala files #12
Comments
Original comment by Brice Dutheil (Bitbucket: bric3, GitHub: bric3): Is that really an issue ? If we could exclude those jars... But it's all So if you have any input or even a PR I'm interested, thx. Note however that if that's not JD-IntelliJ it'll be the IDEA decompiler that will be used anyway. Aside of that it could be interesting to see how scala is compiled, like seeing the @ScalaSignature in the bytecode. Also I don't think you can expect a scala decompiler in the very near future on our side. But who knows, if it happens that we'll work in Scala project. Thx for the feedback, btw |
Original comment by Oleg Aleshko (Bitbucket: olegych, GitHub: olegych): Hi Brice |
Original comment by Brice Dutheil (Bitbucket: bric3, GitHub: bric3): Interesting. Note that I'm not a huge fan of guessing the file type from the presence or not of this annotation ScalaSignature. There might be some other marker though. I know that bytecode allowed to put attributes (they then placed annotation data in these placeholders in Java 1.5), however I don't know if the Scala compiler use this placeholder as well to put reliable data that could identify the source / type of this bytecode. It's not on my priority list though, plus the code is in Scala which makes it difficult to integrate I guess. Anyway if you want to play a bit with the code, and propose something I could integrate it later. Cheers. |
Originally reported by: Oleg Aleshko (Bitbucket: olegych, GitHub: olegych)
The plugin is quite useful for java but messes up resolving in scala files since it can't (yet?) decompile scala.
The text was updated successfully, but these errors were encountered: