When we were making Struts 1 an OSGi bundle, we wrote to the Apache Felix Development Team and asked for help. We didn't know what we were doing (right or wrong!), and they helped us a lot getting the manifest right. I recommend putting a "shout out" to them and get their assistance.
On Thu, Apr 11, 2013 at 9:34 AM, Gary Gregory <[email protected]>wrote: > At work, we use the 1.x JDBC and JMS appenders as well as a custom JDBC > and JMS Appenders. So it would be nice to have those in 2.x. > > Gary > > > On Thu, Apr 11, 2013 at 2:28 AM, Ralph Goers > <[email protected]>wrote: > >> To me, the feature set we have is fine for a 2.0 release. However, we >> need to be happy with the public API and be fairly confident in the quality. >> >> I'm not strong on OSGi and people have mentioned problems with Eclipse. I >> would love to have someone with more OSGi experience provide guidance on >> what we need to do there. >> >> If you go through the Jira issues you will see some that relate to >> general features or qualities Log4j 2 should have. These are still open >> because they either have some feature that should be implemented or haven't >> clearly demonstrated the ability to meet the quality. Others are bugs or >> feature requests where no patch has been supplied. The others are bugs or >> features with patches. I try to apply valid patches as quickly as I can. >> The other stuff generally has fallen behind the requirements of my day job. >> >> I'm sure I could think of things for a 2.1 release but I am still focused >> on just getting 2.0 done. >> >> Ralph >> >> >> On Apr 10, 2013, at 3:50 AM, Remko Popma wrote: >> >> > Maybe it's too early to raise this, but I'm wondering, is there a todo >> list for the new features/improvements that we'd like to get done before >> releasing (the non-beta version of) Log4J 2.0? >> > >> > I know about JMX, but are there any other new features planned for the >> first release? >> > >> > Are all outstanding Jira tickets in scope for 2.0? >> > Any Jira tickets or new features that could go in a 2.1 release? >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [email protected] >> > For additional commands, e-mail: [email protected] >> > >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > > -- > E-Mail: [email protected] | [email protected] > JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0 > Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory >
