Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[#244] drop explicit dependency on jboss-logging #245

Merged
merged 1 commit into from
Jan 6, 2025

Conversation

simkam
Copy link
Collaborator

@simkam simkam commented Sep 16, 2024

fixes #244

this is candidate for minor Creaper version bump to 2.1

It attempts to fix issue due to current dependecy situation:

Let's bring in jboss-logging transitivitely from wildfly-core to keep version aligned.


Originally jboss-logging dependency was added with this commit message

OnlineManagementClient and OfflineManagementClient now log all commands
and operations they are performing. Operations (online only) are logged
on the DEBUG level, commands are logged on INFO. Also, commands are now
advised to provide a toString() method that is used for logging.

The logging framework that is used in Creaper is JBoss Logging, because:

1. It is not actually a logging framework, it's only a facade that delegates
   the logging work to some logging framework that appears to be used.
2. It can detect all commonly used logging frameworks (Logback, Log4j, JUL)
   and one uncommon too (JBoss LogManager).
3. Creaper already depended on it transitively. Avoiding new dependencies
   is good.
4. It has a really small and nice API.

@simkam simkam marked this pull request as draft September 16, 2024 15:04
@simkam simkam mentioned this pull request Jan 2, 2025
@simkam simkam force-pushed the jboss-logging-out branch from 159ebb1 to 05c7661 Compare January 3, 2025 14:57
@simkam simkam marked this pull request as ready for review January 3, 2025 14:57
@simkam simkam requested a review from jbliznak January 3, 2025 14:58
README.md Outdated Show resolved Hide resolved
fixes wildfly-extras#244

It attempts to fix issue due to current dependecy situation:
* creaper has explicit dependency on jboss-logging 3.3.0.Final
* jboss-logging added new methods in 3.6.0
* wildfly-core uses new methods from jboss-logging 3.6.x since 26.0.0.Beta3 which means WildFly 34
* it results in wildfly-extras#244

Let's bring in jboss-logging transitivitely from wildfly-core to keep version aligned.

----

Originally jboss-logging dependency was added with this commit message

```
OnlineManagementClient and OfflineManagementClient now log all commands
and operations they are performing. Operations (online only) are logged
on the DEBUG level, commands are logged on INFO. Also, commands are now
advised to provide a toString() method that is used for logging.

The logging framework that is used in Creaper is JBoss Logging, because:

1. It is not actually a logging framework, it's only a facade that delegates
   the logging work to some logging framework that appears to be used.
2. It can detect all commonly used logging frameworks (Logback, Log4j, JUL)
   and one uncommon too (JBoss LogManager).
3. Creaper already depended on it transitively. Avoiding new dependencies
   is good.
4. It has a really small and nice API.
```
@simkam simkam force-pushed the jboss-logging-out branch from 05c7661 to d181377 Compare January 6, 2025 11:08
@jbliznak jbliznak merged commit 2ecc28f into wildfly-extras:main Jan 6, 2025
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Deal with wildfly-core upgrade to jboss-logging 3.6.x
3 participants