-
Notifications
You must be signed in to change notification settings - Fork 40
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
Generated class files are breaking IntelliJ #576
Comments
@andreaTP do I understand correctly that If so:
|
Thanks a lot for having a look @bashor !
|
I guess IJ doesn't resolve classes in the output dir of the same module. You can try to put generated files into a separate module and depend on it. Or generate class files into a separate folder and add it to dependencies. |
Thanks for getting back and the suggestion @bashor , it was my very first attempt, but, unfortunately it doesn't work, you can reproduce on this branch That said, even if we get this setup to work, I hope we can narrow down the root cause. |
Well, adding the directory to dependencies manually via |
Thanks a lot for the effort and your help on this @bashor . Thanks! |
IDK, it's a different team, and I am not aware of their process. |
Steps to reproduce:
git clone https://github.com/dylibso/chicory.git cd chicory mvn -Dquickly
machine-tests/target/generated-sources/chicory-aot/com/dylibso/chicory/wabt/Wat2WasmMachineFactory.java
You can notice that
Wat2Wasm
is not recognized by the IDE.The current workaround to generate a source file
Wat2WasmMachineFactory
to wrap the generated code masks the issue to the users, but still, it should be great to have a working setup.Everything works as expected with plain Maven commands.
I attempted to ask for help at the IntelliJ boot at Devoxx, but haven't received a contact back so far.
The issue is completely reproducible, but I have no clue where to start to debug/narrow it down.
Attempting to summon @bashor for guidance on how to progress with this 🙏
The text was updated successfully, but these errors were encountered: