- #Intellij jar opens for a second and closes how to#
- #Intellij jar opens for a second and closes install#
- #Intellij jar opens for a second and closes code#
- #Intellij jar opens for a second and closes download#
So you could change the inspection to only warn if you are also using tCancelled(), but I'm not sure how easy that is to detect. For example for logging all chat messages to a file, the MONITOR priority is perfect, because the message cannot be cancelled anymore and we will never want to cancel the event ourselves. This priority is totally fine, as long as you do not use tCancelled(). There is one inspection I do not fully agree with, and that is the use of EventPriority.MONITOR. Good job creating these inspections, looks like a good way to catch some nasty errors/problems.
TL DR: Even more inspections for IntelliJ (cause there aren't enough already.)
#Intellij jar opens for a second and closes code#
Oh, on a last note: I tested this plugin on my own project (instead of my testing thing) for about a week and it seemed to work fine, but I can't 100% guarantee that it won't make errors with quick fixes, so please double-check the code it generated before actually using it. Also, I probably will make this open source, but it's currently pretty late in the evening for me, so I'll probably do that tomorrow.
Well, that's about it, let me know what you think of it. Then close IntelliJ (if it was open) and start it. Then go to C:\Users\$user$\$ideafolder$\config\plugins and putting it there.
#Intellij jar opens for a second and closes download#
I've attached a file to this post where you can download the plugin.
#Intellij jar opens for a second and closes install#
I haven't published the plugin on IntelliJ's built-in plugin stuff (in case it turns out bad), but you can install it manually. It works the same as with other inspections. You can do so by going to File > Settings, and then Editor > Inspections and then selecting Bukkit/Spigot and opening the menu. tSpawnFlags(world.getAllowMonsters(), false)You can enable/disable all these inspections (entirely, or in different scopes) and change the inspection levels if you want to.
Here's a reference list of all inspections, with their default level type (warning/error) and their fixes (if any): If some of you have good suggestions for some inspections let me know. The inspections are purely for Java, so stuff like the plugin.yml aren't covered (just because I couldn't find a single thing about working with YAML files). I did put my code open for review (on a different site), but already six days have passed and nobody has replied yet, therefore I decided to leave it for now and continue what I already was doing the past weeks.Īt this point, the plugin has eighteen inspections. I wouldn't be surprised if the code isn't that great, but that's part of the learning process.
#Intellij jar opens for a second and closes how to#
With a pretty short section on how to create inspections as documentation, most of this plugin was created by just looking at the source code from other plugins which I've never used. This is my first IntelliJ plugin and it was pretty difficult. I also checked the Wiki for some stuff which you might forget/do wrong. I've looked at YouTube tutorials as well as the Spigot Plugin Development section for mistakes which you can easily make. Skip this paragraph if you don't want to read about the development process Some of them highlight mistakes made if you're new to developing plugins, and should therefore hopefully lower the barrier of getting into making plugins, and a few are just things you easily forget/do wrong. This IntelliJ (no Eclipse, Netbeans etc.) plugin adds more inspections to the tons of already built-in inspections IntelliJ already has, specifically for plugins made with Spigot/Bukkit. Instead of making something directly for Minecraft I decided to make something for the development of Minecraft plugins instead. For the past three weeks or so, I've been working on a small side project.
0 kommentar(er)
