1.3.0: @PluginMain does not work on subclasses of JavaPlugin
See original GitHub issueThere is a bug in 1.3.0
where the plugin fails to find the correct main class annotated wit @PluginMain
if it is not a direct subclass of JavaPlugin
.
This works:
@kr.entree.spigradle.PluginMain
public class ExamplePlugin extends JavaPlugin {
}
This does not work, but worked in the version before 1.3.0
:
@kr.entree.spigradle.PluginMain
public class ExamplePlugin extends BasePlugin {}
public class BasePlugin extends JavaPlugin {}
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
The Java Plugin - Gradle User Manual
As indicated above, this plugin adds basic building blocks for working with JVM projects. Its feature set has been superseded by other plugins, ......
Read more >JavaPlugin cannot be resolved to a type - Stack Overflow
import org.bukkit.plugin.java.JavaPlugin;. Everything I've googled has said to put the spigot jar in project properties > build path > libraries ...
Read more >Java Plugin appears but does not do anything - Image.sc Forum
Dear all, I wrote a little plugin in IntelliJ and imported the .class file. The name of the plugin shows up in the...
Read more >cf-cli-java-plugin/cf_cli_java_plugin.go at master - GitHub
The JavaPlugin is a cf cli plugin that supports taking heap and thread ... Run(....) is the entry point when the core CLI...
Read more >Spigradle - GithubHelp
dependsOn shadowJar and the tasks run fine but in the spigot/paper plugins folder I only ... 1.3.0: @PluginMain does not work on subclasses...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
🎉 This issue has been resolved in version 2.0.1 🎉
The release is available on:
v2.0.1
Your semantic-release bot 📦🚀
Yes that fixed it. Thanks!