I’ll try to do this today or tomorrow.

Ralph

> On Jul 14, 2018, at 10:07 AM, Matt Sicker <[email protected]> wrote:
> 
> Apologies for the delay. I've added shasums to the dist.a.o/../dev release
> area.
> 
> On Mon, 9 Jul 2018 at 16:30, Matt Sicker <[email protected]> wrote:
> 
>> I'll add the sha files.
>> 
>> The example isn't using the release candidate, though. That'd be nice to
>> have for smoke testing.
>> 
>> On Mon, 9 Jul 2018 at 15:32, Raman Gupta <[email protected]> wrote:
>> 
>>> There is a simple example in the source:
>>> 
>>> 
>>> https://github.com/apache/logging-log4j-kotlin/blob/master/log4j-api-kotlin-sample/src/main/kotlin/org/apache/logging/log4j/kotlin/sample/LoggingApp.kt
>>> 
>>> And obviously as the primary author of this, my non-binding vote it +1 :-)
>>> 
>>> Regards,
>>> Raman
>>> 
>>> On Mon, Jul 9, 2018 at 12:17 PM Matt Sicker <[email protected]> wrote:
>>>> 
>>>> I’ll try to put together a sample project to demo how to use this. I’m
>>> not
>>>> sure how many of you use or are familiar with Kotlin. It would also be
>>>> great to get some community votes or feedback.
>>>> 
>>>> On Sat, Jul 7, 2018 at 14:10, Matt Sicker <[email protected]> wrote:
>>>> 
>>>>> Hi all, we have a brand new Log4j API to release, and this is the
>>> first
>>>>> release candidate to work with. Below are links to various pieces of
>>> the
>>>>> release for verification:
>>>>> 
>>>>> GPG keys:
>>>>> https://dist.apache.org/repos/dist/release/logging/KEYS
>>>>> 
>>>>> Signed by Matt Sicker (748F15B2CF9BA8F024155E6ED7C92B70FA1C814D).
>>>>> 
>>>>> Source and binary jars:
>>>>> 
>>> https://repository.apache.org/content/repositories/orgapachelogging-1036/
>>>>> 
>>>>> Website staging:
>>>>> https://jvz.github.io/log4j-api-kotlin-staging/
>>>>> 
>>>>> Actual release artifacts (just the sources):
>>>>> https://dist.apache.org/repos/dist/dev/logging/log4j/kotlin/
>>>>> 
>>>>> Kotlin info:
>>>>> https://kotlinlang.org/
>>>>> 
>>>>> Some notes about this release:
>>>>> 
>>>>> * There is no configuration in the pom to automate the creation of
>>> release
>>>>> notes, rat checks, or source and binary zips/tarballs. Thus, the
>>>>> convenience of providing binary artifacts is only extended to the
>>> Maven
>>>>> repository version for now.
>>>>> * There doesn't appear to be any generated API docs.
>>>>> 
>>>>> --
>>>>> Matt Sicker <[email protected]>
>>>>> 
>>>> --
>>>> Matt Sicker <[email protected]>
>>> 
>> 
>> 
>> --
>> Matt Sicker <[email protected]>
>> 
> 
> 
> -- 
> Matt Sicker <[email protected]>


Reply via email to