Fix Slf4j-api module, to better represent the Java 9 compatible module name

[rolaca11]

The currently used slf4j-api version (1.7.26) has not been made with the new modular system of Java 9 in mind. This means that there isn't a module-info.java file in the provided dependency.

To overcome this, in the org.pcap4j.core module, the artifact id of the slf4j-api has been required.

This, however, isn't compatible with the modular version of slf4j-api, which means that users of this (pcap4j) artifact cannot make use of the modular slf4j version, because, during compile, the requires transitive slf4j.api; requirement will not be met by the modular slf4j-api version.

For this reason, I raised the slf4j-api version in the parent POM and made it so that the org.pcap4j.core module requires the intended org.slf4j module instead.

[coveralls]

Coverage increased (+0.02%) to 69.868% when pulling ef97c38 on rolaca11:v1 into 0b4fad8 on kaitoy:v1.

[kaitoy]

logback 1.0.0 that's used for Pcap4J testing doesn't work with SLF4J 1.8.
It seems any released versions of logback don't work with SLF4J 1.8 neither...

[Adito5393]

I encounter the same issue. Could you try using slf4j-api:2.0.0-alpha1?

This contains the module-info with the name org.slf4j that is required here also.

[Adito5393]

There is a newer logback version available that uses SLF4J 2.0:

"Latest STABLE version
The latest stable logback is version 1.2.3.

EXPERIMENTAL/UNSTABLE requiring SLF4J version 2.0.x
The current actively developped version is 1.3.0-alpha5."

@kaitoy Would you be willing to try it out?