I'm not sure where they develop the standards, but there's an osgi-dev mailing list (where I found this posted today): https://www.osgi.org/community/mail-lists/
I don't see Apache on this list despite being the foundation behind most of the open source OSGi projects out there: https://www.osgi.org/about-us/members/ However, there are many companies on that list who directly contribute to said Apache projects. I can't find any info on their site about how to offer feedback. This is just as (if not more) convoluted than the JCP. On 6 April 2017 at 19:41, Gary Gregory <garydgreg...@gmail.com> wrote: > A quick review of the document appears to have SLF4J as a requirement. > Shame about that. > > Gary > > On Thu, Apr 6, 2017 at 5:34 PM, Ralph Goers <ralph.go...@dslextreme.com> > wrote: > >> Where does one comment on these? >> >> The problem is that they mention Java 8 support, but SLF4J doesn’t take >> advantage of any Java 8 features yet. No support for Lamda’s. From what I >> am seeing the next release will support running in Java 9 and will leverage >> StackWalker and support Java modules but Ceki hasn’t mentioned if he is >> going to add to the API to support things users have been asking for. >> >> I’d hate to see them base their standard on what was then the current >> release of SLF4J and then for it to be enhanced and they are stuck with a >> limited API. >> >> I wonder how much input, if any, Ceki had in this. >> >> As a side note, he also changed the binding mechanism and I am not sure >> if it is backward compatible, soI have a feeling log4j-slf4j-impl will need >> changes to support that version. >> >> Ralph >> >> >> On Apr 6, 2017, at 4:00 PM, Remko Popma <remko.po...@gmail.com> wrote: >> >> Good find. I noticed that the document points to Apache Sling and says >> "uses the most common parts today used for logging: SLF4J for clients and >> logback for processing." Seems like Sling decided that in 2013 and never >> looked back. Which is fine, but I believe Log4j2 has changed the landscape >> the last 4 years. >> >> Sent from my iPhone >> >> On Apr 7, 2017, at 6:08, Matt Sicker <boa...@gmail.com> wrote: >> >> OSGi is looking at updating their logging API: >> >> https://github.com/osgi/design/blob/master/rfcs/rfc0219/rfc- >> 0219-LogService-Update.pdf >> >> We might want to provide feedback. >> >> -- >> Matt Sicker <boa...@gmail.com> >> >> >> > > > -- > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org > Java Persistence with Hibernate, Second Edition > <https://www.amazon.com/gp/product/1617290459/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1617290459&linkCode=as2&tag=garygregory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8> > > <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459> > JUnit in Action, Second Edition > <https://www.amazon.com/gp/product/1935182021/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22> > > <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021> > Spring Batch in Action > <https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring+Batch+in+Action> > <http:////ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951> > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory > -- Matt Sicker <boa...@gmail.com>
