Hi,
This is quite clear about the future of java.net:
https://community.oracle.com/community/java/javanet-forge-sunset
As only project owners can do this, I assume Alex will have to help us
before it stops, but it sounds reasonable to start using Google Groups
lists only very soon. The text archive of all prior conversations may be
available somewhere (we could even put it on the GitHub page under github.io)
but *The Java.net and Kenai.com forges will be going dark on April 28,
2017. *
means those sites and all infrastructure will be GONE after that, shut down
completely, not just read only.
Regards,
Werner
On Fri, Jul 22, 2016 at 4:38 PM, Werner Keil <werner.keil_at_gmail.com> wrote:
> Arjan/all,
>
> Thanks for the update. I plan to do when I can. Unfortunately the
> enthusiasm by events (including and especially JavaOne) we proposed JSR 375
> to was not so great as you know. I did extensive live demos for prior
> events like Codemotion in Tel Aviv, but of course the code changed a bit.
>
> Hopefully the announcement around critical aspects for the Cloud like
> Security means that some goals of JSR 375 are also appreciated and further
> supported by Oracle. Either as Spec Lead or a more active EG member than it
> was in the past few months.
>
> I don't know who actually has commit rights or can add things, but
> eventually this could also be an interesting case for the Microprofile
> repo. However, JSR 375 and Security aspects in general seem to big for the
> "minimal" profile, so let's see how that fleshes out before discussing
> other profiles for it.
>
> Btw. I copied the Google Groups list, since despite all of Oracle's
> positive signals, there is no indication that java.net gets a lifeline
> beyond April, so we don't know what's going to happen to the
> "javaee-security-spec" project on java.net or the mailing list.
>
> Kind Regards,
> Werner
>
>
>
> On Fri, Jul 22, 2016 at 4:11 PM, arjan tijms <arjan.tijms_at_gmail.com>
> wrote:
>
>> Hi,
>>
>> For those who haven't seen it yet, here's some feedback from a user
>> actually trying Soteria:
>>
>> https://github.com/javaee-security-spec/soteria/issues/9
>>
>> There's quite an amount of interesting feedback there, and some issues
>> are brought to the surface that I think we should try to solve.
>>
>> Would also be great if more of the EG members actually tried to use
>> Soteria for an actual (example) application, as there's typically quite an
>> amount of things you encounter then.
>>
>> Kind regards,
>> Arjan Tijms
>>
>>
>
>