Subscribe first, then go to that mailing list archive link, and click on the message author link (first link on the top of the page). It’s actually a mailto: link that should open your mail client with an empty e-mail message accordingly configured as a thread response.
Attila. > On 2018. Jun 11., at 23:26, Jesus Luzon <jlu...@riotgames.com> wrote: > > Is there any way to reply to a thread before I was subscribed? I'm pretty > much a noob when it comes to this mailing list process. > > As for the deprecation, we use Nashorn heavily for our Edge transformation > layers and would need to find something that's at least backwards compatible > with our use case. Our use case is actually quite simple so I think it would > be easy to get functionality again, but would rather find something that will > last more than a few years without heavy maintenance. > > On Mon, Jun 11, 2018 at 1:56 PM, Attila Szegedi <szege...@gmail.com > <mailto:szege...@gmail.com>> wrote: > Hey folks, > > the best thing you can do is answer to this thread on jdk-dev mailing list: > <http://mail.openjdk.java.net/pipermail/jdk-dev/2018-June/001338.html > <http://mail.openjdk.java.net/pipermail/jdk-dev/2018-June/001338.html>>. The > JEP is a candidate, and they’re gathering feedback there. If there’s a lot of > community feedback saying people use and depend on Nashorn, it’ll be taken > into consideration. Lots of people have already chimed in on that thread > already saying they rely on Nashorn. If you can re-post your below messages > in that thread, it’d be the best. If you are not subscribed to jdk-dev, you > can do so at <http://mail.openjdk.java.net/mailman/listinfo/jdk-dev > <http://mail.openjdk.java.net/mailman/listinfo/jdk-dev>>. > > Paulo, your specific experience of already having tried to replace Nashorn > with GraalVM.js might be particularly significant. > > Best regards, > Attila. > > > > On 2018. Jun 11., at 21:35, Paulo Lopes <pmart...@redhat.com > > <mailto:pmart...@redhat.com>> wrote: > > > > Hi, > > As the "core" developer of JS support for Vert.x this is quite some > > shocking news as the project really relies on Nashorn for JS support. > > I've been spending many hours to get GraalVM.js working and to some > > extent we can run some unmodified application with it, but we're not > > there yet. For example Nashorn dynalink and Multi threading support are > > not there yet. > > It would be nice to hear what's the ETA for the removal, will project > > Detroit provide a JS script engine (ala Nashorn and will it be > > available as a replacement?)... > > Cheers,Paulo > > On Mon, 2018-06-11 at 14:50 -0300, João Paulo Varandas wrote: > >> Hello Yikes. Well pointed... that is a drag indeed. > >> Any news on those questions? > >> > >> We are completely reliant to this feature in our platform, a lot > >> ofsoftware customization is made using ECMAScript and runs on top > >> ofNashorn/JDK8 currently. I was surprised and scared when I saw > >> that.Hopefully, Jim will bring us good news. > >> > >> > >> > >> > >> > >> On Thu, Jun 7, 2018 at 9:31 AM, yikes aroni <yikesar...@gmail.com > >> <mailto:yikesar...@gmail.com>> > >> wrote: > >> Hi i just read that Nashorn is being deprecated (JEP 335<http://openj > >> <http://openj/> > >> dk.java.net/jeps/335 <http://dk.java.net/jeps/335>>). First of all, that > >> is a drag. Two(ish) > >> questions: > >> 1) So what is the last planned release of Nashorn? J9? It wasnt' > >> clear fromthe JEP. > >> 2) Is this deprecation specifically to make room for GraalJS? That > >> is, isit the Oracle plan to sideline Nashorn and push forward GraalJS > >> afully-supported, not-just-for-research GraalJS? > >> Thanks. Important stuff to know for planning for projects dependent > >> onNashorn / JS support in the JVM! > >> > >> > >
