4/10/2023 0 Comments Java reflection 1.5![]() ![]() And the code I'm working on is proprietary, so I certainly can't upload it as-is. Even if I did, I wouldn't know how to reproduce the problem, because IDK what the heck is causing it. I don't have time to create a sample project that reproduces the issue. I have a deadline to meet, and suddenly I'm stranded. I've gone back through all the settings, and as far as I can tell, everything is set as it was before. Literally nothing changed except the version of IntelliJ that was installed. IntelliJ can't find the jars for my dependencies, even though maven compiles everything just fine. But now my dependencies aren't being respected properly, either. I got the Java version number to finally be respected, though I'm not sure how. My project was building fine before that. Incidentally, here's some info that might help: My problem recurred when I updated to the latest version, 2019.2, build #IC-192.5728.98. If the POM settings are going to be ignored (as they are, for me, though I can't figure out why) make that clear in the settings, and explain why & how to change that behavior. Make it clear where the settings are coming from, and give a *single* place to control that. This wouldn't be nearly such a problem if controls weren't scattered across multiple places in the settings, the POM, the. Please just put all the controls for java version & language level in one place. I would hate to be forced to move to an inferior product over such a seemingly minor but nonetheless intractable problem. You guys have a great product, but this particular issue frustrates me to no end. The fact is, users are having a negative experience around this. It shouldn't matter whether this is a bug or a "feature". I see the comments have multiplied since my last visit to this page, and debate as to whether it is a bug or not has emerged. Maybe I held my mouth just right when I clicked build? Each time I stumble my way forward until miraculously something works, but I'm never quite sure which combination of actions does the trick. I do wonder if the issue might be triggered under these circumstances. On the speculative side, I've noticed that sometimes, when editing pom files and introducing an XML error - which can easily happen in the middle of editing of a pom file with auto-reload on - IntelliJ will act weird, neither complaining about the error, nor, obviously, loading the configuration. Though IntelliJ _should_ respect plugin configuration, specifying those properties once in the external dependency, if it works, is acceptable, so I'll try that out. We do not have source and target specified by properties, but by plugin. Specifying version in every project is not a fix, it is a contingency workaround IntelliJ not handling maven poms as it should, and an unacceptable one for us. ![]() I believe I have mentioned the issue does seem to happen when the parent of the root pom of a project is an external dependency, so it shouldn't come as news to anyone following this issue. If the fix is pre-2018, it didn't fix it. I can't say for sure it is presently fixed, but people on our company have had trouble with it last year. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |