Looks great.
Names of repos inside the organization are a little long, but if that was
standard on the java.net side to keep them in sync, why not. JSR 354 (just
in the Final ballot phase these days) also made some good experience with a
Spec using Asciidoc.
At DWX in June (the same week as DevoXX UK btw.) Andres will also give a
talk about Asciidoc. Maybe he'd mention some of the recent JSRs that
succesfully use it?;-)
Cheers,
Werner
On Wed, Apr 29, 2015 at 9:37 AM, Jean-Louis Monteiro <
jlmonteiro_at_tomitribe.com> wrote:
> That's awesome Alex.
>
> Also useful to have them both in the same place as you can use code
> snipets without copy/paste. You can just mention them in the asciidoc
> document.
>
> --
> Jean-Louis Monteiro
> http://twitter.com/jlouismonteiro
> http://www.tomitribe.com
>
> On Wed, Apr 29, 2015 at 7:00 AM, Alex Kosowski <alex.kosowski_at_oracle.com>
> wrote:
>
>> Hi,
>>
>> I have been assembling a Maven project for creating the spec document,
>> api, and JavaDoc. This will provide a framework to move toward the Early
>> Draft version of the spec. I am using AsciiDoc as the spec format, as it is
>> well supported and seems suitable for collaborative spec development.
>>
>> Also, I am following the CDI JSR model, and storing the API Java and
>> AsciiDoc spec in the same repo, with the ability to build the latest
>> version of both with one Maven command.
>>
>> I expect to have this in the repo in the next day or two.
>>
>> With regards,
>> Alex
>>
>>
>