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

jul-to-slf4j bridge #87

Open
bertfrees opened this issue Sep 29, 2015 · 7 comments
Open

jul-to-slf4j bridge #87

bertfrees opened this issue Sep 29, 2015 · 7 comments

Comments

@bertfrees
Copy link
Member

@rdeltour We include jul-to-slf4j but does it actually work? @joeha480 can't find any Dotify info messages in the detailed log (Dotify uses java.util.logging).

@rdeltour
Copy link
Member

AFAIK it should work out of the box, and I dont see anything in the config file that would silent dotify. @capitancambio any idea?

@joeha480
Copy link
Member

I get some information when running from xprocspec, but not from within the GUI

@bertfrees
Copy link
Member Author

Ah really? That's interesting. Do you mean the Dotify information that is printed to STDOUT? Do you get the same messages on STDOUT when you run bin/pipeline2.bat? In the xprocspec tests we're not including the jul-to-slf4j bundle (see e.g. DotifyCalabashTest.java and org/daisy/pipeline/pax/exam/Options.java)

@joeha480
Copy link
Member

Yes, I can see it on STDOUT when running pipeline2.bat. What does that mean?

@bertfrees
Copy link
Member Author

I guess it means the bridge doesn't work.

@bertfrees bertfrees added the bug label Oct 15, 2015
bertfrees added a commit to daisy/pipeline-framework that referenced this issue Oct 19, 2015
bertfrees added a commit to daisy/pipeline-mod-braille that referenced this issue Oct 19, 2015
bertfrees added a commit to daisy/pipeline-framework that referenced this issue Dec 9, 2015
bertfrees added a commit to daisy/pipeline-mod-braille that referenced this issue Dec 17, 2015
@bertfrees
Copy link
Member Author

Fixed in 1.9.8

@bertfrees
Copy link
Member Author

It looks like this is another startup issue. If bundles are started in the right order, it works, otherwise not.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants