| Author |
Message |
|
|
The pom.xml for v1.8.1 lists not only slf4j-api but also slf4j-log4j12 as a required dependency.
Is the log4j implementation actually required? Or can a project choose a different slf4j implementation? If it's the latter I'd suggest changing the pom.xml as explained in the slf4j FAQ.
Thanks
Mirko
|
 |
|
|
I already did disable it of course. But I'm disappointed at having to explicitly disable such an unwanted feature. Maybe it's useful for you to collect usage statistics, but for users I think it's actually useless (who's going to notice an INFO line in the server logs?) and potentially dangerous.
It's just not something I'd expect from a reputable software component.
Kind regards
Mirko
|
 |
|
|
Hi, and thanks for your great scheduler.
But would it be possible to know what's the rationale behind the new automatic update check that is enabled by default?
http://jira.opensymphony.com/browse/QUARTZ-842
http://forums.terracotta.org/forums/posts/list/3395.page
https://jira.terracotta.org/jira/browse/QTZ-28
https://jira.jboss.org/jira/browse/JBAS-7988
Honestly I simply don't get it. The last thing I want is for each and single jar library I include in a project to go and make an unrequested HTTP connection at startup, potentially causing unexpected issues for no real reason.
Many thanks
Mirko
|
 |
|
|