[Feature Request]: Change examples to a subproject

[Andrew Dey]

Origins of the Feature

In issue #4,

Update logging example to match new API

Is currently not plausible. The current system in place where example is considered a module does not provide a simple/clean solution to having the example module specifically have a configurable dependency on a specific logging framework. As such, and to also promote a better solution to passing main-module code than literally modifying the resource and class path let alone a logging framework dependency, we need to expand it out into its own (sub)project.

The New Feature Idea(s)

These are the features that should be considered:

• Create Gradle subproject examples (this may need debate -- original was example, do we have leeway to change entirely?)
  • this also includes re-vamping the existing example declaration in the current build.gradle
• Remove extra folders by enforcing this structure for the examples subproject:

  examples
    → java
    → kotlin
    → groovy
    → resources

• see #132

Progress in this repo will be tracked on the slf4j branch.

Alternatives

No response

Code of Conduct

• I agree to follow this project's Code of Conduct