-
Notifications
You must be signed in to change notification settings - Fork 62
Log4j config in xebium jar #13
Comments
Fixed. The file was not even used. |
One thing: The SeleniumDriverFixture currently has a static "BasicConfigurator.configure()" statement. I suppose both Xebium and SUT are not executed in the same JVM? |
They sometimes are executed in the same JVM. We have some mixed tests where our Fitnesse fixtures are executing some tasks that are usually executed by a scheduler and we use Xebium to see if the results are visible. |
Xebium is a plugin, not a stand-alone app. It should therefore not change anything at all in the logging configuration IMO. |
Agreed, but if log4j is not given some sort of configuration, you'll end up having only a
message in the log output. What would be wise? Use slf4j or something? Create a fixture call to set up logging (Yuk!)? |
I would indeed migrate to slf4j in the first place so users can decide 2011/5/27 amolenaar
|
Sticking with Log4J, you could use |
I'd use whatever Fitnesse uses. Blend into the host environment. bvklingeren
|
System.out? Dunno, the driver is not using anything AFAICT. Just checked and it works nice with slf4j and slf4j-simple. |
Committed. Please try. |
thanks dude, we'll do 2011/5/27 amolenaar
|
If this works okay now we can do a release. |
Unfortunately I can't test it without a lot of hassle, but I take your Cheers, 2011/5/30 amolenaar
|
I'll close this issue, unless you still face troubles. |
Sorry for the late reply, but the configuration works correctly. Only one remark: please change the scope of the slf4j-simple.jar to test, because it's an implementation wich should be provided by the user, not Xebium. Cheers, |
Done that. Check out 0.4 :) |
Please remove the log4j.properties from the src/main/resources directory for it is packaged with the final jar. This pollutes the logs of software using Xebium.
The text was updated successfully, but these errors were encountered: