> On 05.05.2016, at 22:42, users-request_at_javaee-spec.java.net wrote:
>
> Table of contents:
>
> 1. [javaee-spec users] Re: Migration Java EE regarding java.net shutdown - Bill Shannon <bill.shannon_at_oracle.com>
> 2. [javaee-spec users] Re: Digest for list users_at_javaee-spec.java.net - Adam Bien <abien_at_adam-bien.com>
>
>
> From: Bill Shannon <bill.shannon_at_oracle.com>
> Subject: [javaee-spec users] Re: Migration Java EE regarding java.net shutdown
> Date: 5. Mai 2016 um 02:13:45 MESZ
> To: users_at_javaee-spec.java.net
> Reply-To: users_at_javaee-spec.java.net
>
>
> We've been through this issue several times internally. It comes down to three things:
> • Converting specs to a new format and ensuring no semantics are lost or changed in the process is a large amount of effort.
at this point the community could help. At the end we will have to compare two documents.
> • There's no agreement on which new format would be best, providing enough of the features of the current format.
adoc or markdown — these are the most popular and best integrated with modern tools
> • Spec leads like the tools they're currently using (mostly FrameMaker) and are reluctant to convert to a new tool.
FrameMaker was a great tool and there is no adequate, popular replacement. However we will have at some point to move on.
I would value speed and easier community contribution (pull requests) over perfect layout.
> Inertia is hard to overcome.
Bill: this is not true. Now I can use javaee 7 API for my unit tests without strange JVM errors :-)
>
> Antonio Goncalves wrote on 05/03/16 23:10:
>> Hi Bill,
>>
>> If most of the specs end-up in GitHub, do you think we could use this migration to write the specifications in Asciidoc (or MarkDown) ? This way we could use Pull-Requests when it comes to amending a specification ? ATM we exchange PDFs and emails about what could be improved in the specification. Using Asciidoc would ease this process.
>>
>> WDYT ?
>>
>> Antonio
>>
>> On Tue, May 3, 2016 at 8:16 PM, Bill Shannon <bill.shannon_at_oracle.com> wrote:
>> We're in the process of planning this migration. Some subprojects are already mirrored at Github, which is most likely where these projects will end up. It's not clear that there's anything the community can do to help, but if you have ideas let us know. It will likely be several months before we work out all the details for the migration.
>>
>> arjan tijms wrote on 05/03/16 09:12:
>>> Hi,
>>>
>>> It was recently announced that java.net and kenai.com will shutdown on 28 April, 2017. See https://community.oracle.com/community/java/javanet-forge-sunset
>>>
>>> I wonder if there's already a plan to migrate the various Java EE assets, specifically the RI itself (the GlassFish project), and the associated mailing lists, JIRA instance, project pages, etc.
>>>
>>> Would people from the community be able to help with this migration in any way?
>>>
>>> Kind regards,
>>> Arjan Tijms
>>
>>
>>
>>
>> --
>> Antonio Goncalves
>> Software architect, Java Champion and Pluralsight author
>>
>> Web site | Twitter | LinkedIn | Pluralsight | Paris JUG | Devoxx France
>
>
>
>
> From: Adam Bien <abien_at_adam-bien.com>
> Subject: [javaee-spec users] Re: Digest for list users_at_javaee-spec.java.net
> Date: 5. Mai 2016 um 03:48:53 MESZ
> To: users_at_javaee-spec.java.net
> Reply-To: users_at_javaee-spec.java.net
>
>
> +1 for adoc (or markdown) this would encourage contributions.
>
> cheers,
>
> adam
>> On 04.05.2016, at 22:42, users-request_at_javaee-spec.java.net wrote:
>>
>> Table of contents:
>>
>> 1. [javaee-spec users] Re: Migration Java EE regarding java.net shutdown - Antonio Goncalves <antonio.goncalves_at_gmail.com>
>>
>>
>> From: Antonio Goncalves <antonio.goncalves_at_gmail.com>
>> Subject: [javaee-spec users] Re: Migration Java EE regarding java.net shutdown
>> Date: 4. Mai 2016 um 08:10:09 MESZ
>> To: "users_at_javaee-spec.java.net" <users_at_javaee-spec.java.net>
>> Reply-To: users_at_javaee-spec.java.net
>>
>>
>> Hi Bill,
>>
>> If most of the specs end-up in GitHub, do you think we could use this migration to write the specifications in Asciidoc (or MarkDown) ? This way we could use Pull-Requests when it comes to amending a specification ? ATM we exchange PDFs and emails about what could be improved in the specification. Using Asciidoc would ease this process.
>>
>> WDYT ?
>>
>> Antonio
>>
>> On Tue, May 3, 2016 at 8:16 PM, Bill Shannon <bill.shannon_at_oracle.com> wrote:
>> We're in the process of planning this migration. Some subprojects are already mirrored at Github, which is most likely where these projects will end up. It's not clear that there's anything the community can do to help, but if you have ideas let us know. It will likely be several months before we work out all the details for the migration.
>>
>> arjan tijms wrote on 05/03/16 09:12:
>>> Hi,
>>>
>>> It was recently announced that java.net and kenai.com will shutdown on 28 April, 2017. See https://community.oracle.com/community/java/javanet-forge-sunset
>>>
>>> I wonder if there's already a plan to migrate the various Java EE assets, specifically the RI itself (the GlassFish project), and the associated mailing lists, JIRA instance, project pages, etc.
>>>
>>> Would people from the community be able to help with this migration in any way?
>>>
>>> Kind regards,
>>> Arjan Tijms
>>
>>
>>
>>
>> --
>> Antonio Goncalves
>> Software architect, Java Champion and Pluralsight author
>>
>> Web site | Twitter | LinkedIn | Pluralsight | Paris JUG | Devoxx France
>>
>>
>> End of digest for list users_at_javaee-spec.java.net - Wed, 04 May 2016
>
> workshops.adam-bien.com
> effectivejavaee.com
> blog.adam-bien.com
> airhacks.news
>
> Author of:
> "Real World Java EE Night Hacks”,
> "Real World Java EE Patterns— Rethinking Best Practices"
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> End of digest for list users_at_javaee-spec.java.net - Thu, 05 May 2016
workshops.adam-bien.com
effectivejavaee.com
blog.adam-bien.com
airhacks.news
Author of:
"Real World Java EE Night Hacks”,
"Real World Java EE Patterns— Rethinking Best Practices"