When this scope isn't set, Apache Maven will include the API into the final JAR file, which creates unnecessarily large file sizes.
The reason I think this behavior is intended, is because the ProtocolLib plugin needs to be installed on the same server as the plugin including ProtocolLib as a dependency in order for ProtocolLib to function. Beside that, the Gradle example specifies the compileOnly option which is essentially the same as the provided scope in Apache Maven.
When this scope isn't set, Apache Maven will include the API into the final JAR file, which creates unnecessarily large file sizes.
The reason I think this behavior is intended, is because the ProtocolLib plugin needs to be installed on the same server as the plugin including ProtocolLib as a dependency in order for ProtocolLib to function. Beside that, the Gradle example specifies the
compileOnly
option which is essentially the same as theprovided
scope in Apache Maven.