|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
- [mojo-dev] [jira] (MCASSANDRA-25) Logging configur... Mikhail Mazursky (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-25) Logging con... Stephen Connolly (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-25) Logging con... Mikhail Mazursky (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-25) Logging con... Mikhail Mazursky (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-25) Logging con... Mikhail Mazursky (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-25) Logging con... Olivier Lamy (JIRA)
- [mojo-dev] [jira] (MCASSANDRA-25) Logging con... Olivier Lamy (JIRA)

I think both this issue and MCASSANDRA-16 can be solved by excluding log4j binding and configuration and allowing user to specify them. This just needs to be documented with examples. Also, the same technique can be used to do C* version updates - you can just specify explicitly C* artifact version to use. This will work as long as classes from C* that are used in this plugin stay binary compatible. WDYT?