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

Overwriting log4j.configuration is bad #15

Closed
sorenvind opened this issue May 24, 2012 · 3 comments
Closed

Overwriting log4j.configuration is bad #15

sorenvind opened this issue May 24, 2012 · 3 comments
Milestone

Comments

@sorenvind
Copy link
Contributor

If using a log4j properties file already, it is overwritten by the EmbeddedCassandraServerHelper. This is probably not the desired behaviour (it makes it difficult to use it embedded anywhere).

@jsevellec
Copy link
Owner

You're right I have to take a look about log4j. On the other hand, I think it's not a good idea to use EmbeddedCassandraServerHelper to embedded it anywhere (like in an application for production).

@sorenvind
Copy link
Contributor Author

It's useful to have the ability to embed it. We're using it in our test framework where we need a (temporary) cassandra server. It's used in this way both for unit testing and for local testing on developer workstations (where a non-broken log4j configuration is essential).

@jsevellec
Copy link
Owner

In this case, i understand.

I think it's not very complicated to do. Do you want to try to implement this feature?

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

No branches or pull requests

2 participants