Hi, I'm using tinylog version 2.0.0 on Android and it worked great. However I recently released my new app and I found out that the log file never gets created. So I started to investigate the issue. What I found out is that as soon as I enable proguard on my release build I receive following output on the logcat when I log something

LOGGER WARN: No logging framework implementation found in classpath. Add tinylog-impl.jar for outputting log entries.

My tinylog.properties file looks like this

writer=rolling file
writer.file=/data/data/test.grill.com/files/test_logs/test_log.txt
writer.level=info
writer.policies=size: 5mb
writer.format={date: HH:mm:ss.SSS} [{thread}] {level}:\n{message}

and it is located in my resources folder. Everything is working when I'm not enabling proguard. Are there some proguard rules which needs to be added when using tinylog with proguard?

Edit: seems that the ServiceLoader could not get anyResourses

classLoader.getResources(name);

returns an empty Enumeration when enabling proguard.

Running SharedFileWriterTest on Linux I get test failures as described here: https://github.com/jotomo/tinylog/commit/0b41014894d5986d163e266411d993abaa1ca9ee, indicating a problem when writing to a log file concurrently. @pmwmedia I'm assuming you're running Windows. TravisCI would run the tests on Linux - I've seen you tested TravisCI but dropped it again. Remember why?

Updated: running a Linux system natively, or a Linux VM on a Linux hosts, there are intermittend build failures in tests that inherit from AbstractTimeBasedPolicy (mostly in WeeklyPolicyTest). These failures occur 1-3 times out of 10 on an Arch Linux system (as December 2015). It seems that the SystemTimeMock is not thread-safe and occassionally returns the actual system time, leading to test failures.

Description

Linked issue: #194

Definition of Done

• [x] There are no TODOs left in the code
• [x] Code style follows the tinylog standard
• [x] All classes and methods have Javadoc
• [x] Changes are covered by JUnit tests including corner cases, errors, and exception handling
• [x] Maven build works including compiling, tests, and checks (mvn verify)
• [x] Changes are committed by a verified email address that is assigned to the GitHub account (https://github.com/settings/emails)

Documentation

Additions or amendments for the public documentation:

Writer | Property Value | Description :------------------------------------------ |:-------------- |:------------ ... JSON Writer | json | Writes log entries to a json file

...

JSON Writer

The JSON writer writes log entries to a defined json file. It supports custom field configuration with the syntax writer.field.FIELDNAME = FORMAT. With appending mode off, the file is reset with new log entries. The format can be configured like in other writers. Example:

writer         = json
writer.file    = log.json
writer.charset = UTF-8 
writer.append  = true
writer.field.message = message
writer.field.date = date
writer.field.lvl = level

Agreements

• [x] I agree that my changes will be published under the terms of the Apache License 2.0
• [x] I agree that my GitHub user name will be published in the release notes

I don't know why this exception throw when i adds via gradle collect dependencies and in bundle i have all impl module classes.

I also noticed that many have the same problem.

Gradle dependencies:

Embed configuration:

Jar configuration:

Hello, have you thinking about providing module-info.java module descriptor then TinyLog to be compatible with Java Platform Module System and make possible creating of runtime image with jlink ?

Describe the issue Currently, the writer leaves the ] out and keeps the last , which is invalid json. I think we should let the json log file always stay in a syntactic correct state. One would not be able to parse the file while it does not match JSON spec.

Currently the close method performs the last steps needed to bring it in that state by calling postProcess. Maybe we could handle the logic of postProcess everytime we write an entry. The new close method should then only handle writer.flush() and writer.close()

The file currently looks like this:

[
	{
           ...
	},

To Reproduce

1. configure properties to use json writer
2. start application
3. write any entry
4. use the json for anything other while application is running

Environment tinylog version: 2.4 Java version: 15

Description

The Java property configuration loader is made more generic and as service so that user loaders (YAML, JSON) become possible. Besides the ConfigurationLoader interface and its implementation this requires public access to some classes and methods.

Linked issue: #114

Definition of Done

• [x] There are no TODOs left in the code
• [x] Code style follows the tinylog standard
• [x] All classes and methods have Javadoc
• [x] Changes are covered by JUnit tests including corner cases, errors, and exception handling
• [x] Maven build works including compiling, tests, and checks (mvn verify)
• [x] Changes are committed by a verified email address that is assigned to the GitHub account (https://github.com/settings/emails)

Documentation

Additions or amendments for the public documentation:

It has API effect with the new configuration loader service.

Agreements

• [x] I agree that my changes will be published under the terms of the Apache License 2.0
• [x] I agree that my GitHub user name will be published in the release notes

Describe the bug When using slf4j-tinylog the correct class is not logged

To Reproduce Steps to reproduce the behavior:

1. Use tinylog, tinylog-api and slf4j-tinylog
2. Run an application that uses slf4j e.g. Flyway
3. It runs and logs incorrectly, e.g.

2021-01-01 15:33:23 [io-executor-thread-1] org.flywaydb.core.internal.logging.slf4j.Slf4jLog.info() INFO: Flyway Community Edition 7.3.1 by Redgate 2021-01-01 15:33:23 [io-executor-thread-1] org.flywaydb.core.internal.logging.slf4j.Slf4jLog.info() INFO: Database: jdbc:postgresql://127.0.0.1:6432/test (PostgreSQL 13.1) 2021-01-01 15:33:23 [io-executor-thread-1] org.flywaydb.core.internal.logging.slf4j.Slf4jLog.info() INFO: Current version of schema "public": 1.1

Where these entries belong to different classes, e.g. the first is run from a class called VersionPrinter.

Environment tinylog version: 2.2.1 Java version: 15

Description

Linked issue: #159

Definition of Done

• [x] There are no TODOs left in the code
• [x] Code style follows the tinylog standard
• [x] All classes and methods have Javadoc
• [x] Changes are covered by JUnit tests including corner cases, errors, and exception handling
• [x] Maven build works including compiling, tests, and checks (mvn verify)
• [x] Changes are committed by a verified email address that is assigned to the GitHub account (https://github.com/settings/emails)

Documentation

Additions or amendments for the public documentation:

Agreements

• [x] I agree that my changes will be published under the terms of the Apache License 2.0
• [x] I agree that my GitHub user name will be published in the release notes

see https://github.com/pmwmedia/tinylog/issues/149

I'm not sure how to implement the assertions in the test. The build is not working on my machine (javac 11.0.7)

tinylog/tinylog-api/src/main/java/org/tinylog/runtime/LegacyJavaRuntime.java:[58,43] cannot find symbol
[ERROR]   symbol:   class Reflection
[ERROR]   location: package sun.reflect

If you find the idea acceptable, could you please help me with this part? Thank you!

Description

Linked issue: #201

This change allows a single TaggedLogger to log to multiple tags, instead of having to create individual logger for each tag.

Definition of Done

• [x] I read contributing.md
• [x] There are no TODOs left in the code
• [x] Code style follows the tinylog standard
• [x] All classes and methods have Javadoc
• [x] Changes are covered by JUnit tests including edge cases, errors, and exception handling
• [x] Maven build works including compiling, tests, and checks (mvn verify)
• [x] Changes are committed by a verified email address that is assigned to the GitHub account (https://github.com/settings/emails)

Documentation

Additions or amendments for the public documentation:

• Tags will need to be updated with the addition of the new tags method.

Agreements

• [x] I agree that my changes will be published under the terms of the Apache License 2.0 (mandatory)
• [x] I agree that my GitHub user name will be published in the release notes (optional)

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

This repository currently has no open or pending branches.

Detected dependencies

• [ ] Check this box to trigger a request for Renovate to run again on this repository

I would like to have a core library.

It doesn't contain too much features.

Only core features.

Tinylog is still too fat.

Don't add features,It immediately becomes Log4j2.

I'd love to see a possibility to set the severity levels for packages or classes for each writers individually.

In our use-case we'd like to filter a little bit of logs from the console, but still keep it all in the file - unfortunately it's not possible with the current impl because the level@package property works globally and affects all writes. Ofc I can filter this using a custom writer, but I think it might be a better idea if it would work like that out of the box. In the end, in most of the use-cases if we'd like to get rid of some logs at the given level, we're mostly thinking about a specific writer that is quite annoying, not the whole logging system.

Please implement a feature for getting the current used log file name. Maybe a listener that could automatically inform users about a rollover event and provide the new file name. Thanks

Hi,

in my case, i have to reasign a system property value on runtime and i would like to see the new value in my log file. Is there a way to achive that easily?

tinylog.properties (System property -> app.namespace)

writer2			= rolling file
writer2.level		= info
writer2.format		= {date} {level} [ns: #{app.namespace}] [th: {thread}] {class}.{method}:\n{message}
writer2.file	...

Custom logger

public class MyLogger {

    private static final LoggingProvider provider = ProviderRegistry.getLoggingProvider();

    private static final int minimumLevel = provider.getMinimumLevel(null).ordinal();
    private static final boolean infoEnabled = minimumLevel <= Level.INFO.ordinal();
    private static final boolean errorEnabled = minimumLevel <= Level.ERROR.ordinal();

    public static void info(String message) {
        if (infoEnabled) {
            provider.log(2, null, Level.INFO, null, null, message);
        }
    }

    public static void error(Throwable exception) {
        if (errorEnabled) {
            provider.log(2, null, Level.ERROR, exception, null, null);
        }
    }

}

The default configuration in ProviderRegistry.getLoggingProvider(); loads all properies once and does a mapping (tinylog / system properties) -> so my logging format is fix.