You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@netbeans.apache.org by Emilian Bold <em...@gmail.com> on 2019/01/11 20:35:35 UTC
Where is `Oracle JS Parser Implementation` built from?
We suggest the plugin in NetBeans, but I don't know where the source for it is.
The plugin we point to is
http://plugins.netbeans.org/plugin/74901/oracle-js-parser-implementation
I suspect it used to be part of the repository, so where is it? (I
also remember a discussion about relicensing some JS parser as Apache,
I gather that went nowhere. Sorry if a bit fuzzy.)
--emi
http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more!
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Help, JavaScript fans! was: Use Graal.js (parser) for NetBeans 11
Posted by Jose Ch <pe...@gmail.com>.
Hey everyone,
This is from http://www.graalvm.org/docs/release-notes/ about its latest
release:
1.0-RC11
JavaScript
- Graal.js only supports ECMAScript 5 (ES5) and newer, and enforces that
rule.
- Added support for sharing Java objects using the experimental Node.js
Worker Threads API.
- Added support for ScriptEngine GLOBAL_SCOPE bindings.
- Added options to enable/disable several extension features e.g.,
print() or load().
- Added options to disable features for security reasons e.g., eval().
Cheers
Jose
El jue., 31 ene. 2019 a las 8:17, Christian Lenz (<ch...@gmx.net>)
escribió:
> Hey Jaroslav,
>
> I have a Question About this test here:
> https://builds.apache.org/job/incubator-netbeans-jsparser/6/testReport/org.netbeans.modules.javascript2.editor/JsCodeCompletionES6Test/testClassName01/
>
> Does that mean, that graal can’t handle ES6 atm or do I understand smth
> wrong? Because the expected result should be „CLASS“ but the completion
> says it is „VARIABLE“.
>
> Can you help me here to understand that?
>
>
> Cheers
>
> Chris
>
>
>
> Von: Jaroslav Tulach
> Gesendet: Dienstag, 29. Januar 2019 15:33
> An: Apache NetBeans
> Betreff: Re: Help, JavaScript fans! was: Use Graal.js (parser) for
> NetBeans 11
>
> Hail JavaScript!
>
> One of the common questions is how many of those more than six hundred
> failures are related to switch of the parser from Nashorn to Graal.js. To
> answer that question I have set another job up:
>
> https://builds.apache.org/job/incubator-netbeans-jsparser-tests/
>
> it does the same test as
>
> https://builds.apache.org/job/incubator-netbeans-jsparser/
> <
> https://builds.apache.org/job/incubator-netbeans-jsparser/lastCompletedBuild/testReport/org.netbeans.modules.javascript2.sdoc/SDocCompletionDocumentationTest/testCompletionDocumentation01/
> >
>
> but it takes the sources from master branch. There seems to be 129 failures
> in the master branch. That is a lot and it would be nice to fix them,
> but...
>
> It means that there is more than five hundred failures that are somehow
> related to the parser change. I assume that means the branch isn't in
> mergable state right now. Your help is needed!
>
> Fix a test! Make NetBeans better!
> -jt
>
> pá 25. 1. 2019 v 19:38 odesílatel Geertjan Wielenga
> <ge...@googlemail.com.invalid> napsal:
>
> > Investigated the ones starting with this one (there are 11 others) but
> > couldn't figure it out:
> >
> >
> >
> https://builds.apache.org/job/incubator-netbeans-jsparser/lastCompletedBuild/testReport/org.netbeans.modules.javascript2.sdoc/SDocCompletionDocumentationTest/testCompletionDocumentation01/
> >
> > Gj
> >
> > On Fri, Jan 25, 2019 at 3:59 PM Geertjan Wielenga <
> > geertjan.wielenga@googlemail.com> wrote:
> >
> > > Would it be true to say that the majority, or at least many, of these
> > > failing tests were already failing before the introduction of the
> > Graal.js
> > > parser?
> > >
> > > Gj
> > >
> > >
> > > On Fri, Jan 25, 2019 at 3:50 PM Geertjan Wielenga <
> > > geertjan.wielenga@googlemail.com> wrote:
> > >
> > >> Well, that issue probably doesn't make sense since we're checking in
> > >> directly into Svata's repo, right?
> > >>
> > >> Anyway, let me know if this makes sense, if not, tell me how to do it
> > >> differently:
> > >>
> > >>
> > >>
> >
> https://github.com/sdedic/incubator-netbeans/commit/908659392359671f7166566294b20c14e8d71232
> > >>
> > >> Gj
> > >>
> > >>
> > >> On Fri, Jan 25, 2019 at 2:51 PM Geertjan Wielenga <
> > >> geertjan.wielenga@googlemail.com> wrote:
> > >>
> > >>> Not sure if there is an issue yet for fixing the failing tests,
> created
> > >>> it and will be referencing this in my pull requests:
> > >>>
> > >>> https://issues.apache.org/jira/browse/NETBEANS-1990
> > >>>
> > >>> Gj
> > >>>
> > >>>
> > >>> On Fri, Jan 25, 2019 at 2:37 PM Christian Lenz <
> christian.lenz@gmx.net
> > >
> > >>> wrote:
> > >>>
> > >>>> Will try to help on the weekend. Maybe.
> > >>>>
> > >>>>
> > >>>> Cheers
> > >>>>
> > >>>> Chris
> > >>>>
> > >>>>
> > >>>>
> > >>>> Von: Jaroslav Tulach
> > >>>> Gesendet: Freitag, 25. Januar 2019 13:18
> > >>>> An: Apache NetBeans
> > >>>> Cc: Svata Dedic
> > >>>> Betreff: Help, JavaScript fans! was: Use Graal.js (parser) for
> > NetBeans
> > >>>> 11
> > >>>>
> > >>>> I assume there is a lot of people interested in support of modern
> > >>>> JavaScript, right? We need you help:
> > >>>>
> > >>>> čt 24. 1. 2019 v 5:59 odesílatel Jaroslav Tulach <
> > >>>> jaroslav.tulach@oracle.com>
> > >>>> napsal:
> > >>>> >
> > >>>> > The PR-1011 is in.
> > >>>> >
> > >>>> > Somebody needs to start working on rewriting the `webcommon/
> > >>>> > javascript2.editor/` to use the parser in
> `webcommon.libs.graaljs`.
> > >>>>
> > >>>>
> > >>>>
> > >>>> Sváťa created a PR:
> > >>>> https://github.com/apache/incubator-netbeans/pull/1099,
> > >>>> but it cannot be merged until the code is rewritten to use the new
> > >>>> version
> > >>>> of the parser and work correctly. There is a Jenkins job that tracks
> > the
> > >>>> status:
> > >>>>
> > >>>> https://builds.apache.org/job/incubator-netbeans-jsparser/
> > >>>>
> > >>>> Right now we have 693 failures. Please help us fix them. The
> > >>>> instructions
> > >>>> are given in the job description, and it should be fairly easy. Get
> > the
> > >>>> repository:
> > >>>>
> > >>>> git clone https://github.com/sdedic/incubator-netbeans.git
> > >>>> cd incubator-netbeans
> > >>>> git checkout experimental/graaljs_parser
> > >>>>
> > >>>> and then build it all and check the tests:
> > >>>>
> > >>>> ant build
> > >>>> for i in webcommon/*; do
> > >>>> (cd $i; ant test-unit -Dcontinue.after.failing.tests=true)
> > >>>> done
> > >>>>
> > >>>> You can open any module under webcommon in the NetBeans IDE, select
> a
> > >>>> test
> > >>>> and run or debug it.
> > >>>>
> > >>>> If you care about JavaScript, please help: Fix a test. Make NetBeans
> > >>>> better!
> > >>>> -jt
> > >>>>
> > >>>>
> > >>>>
> > >>>> > Dne neděle 13. ledna 2019 5:24:04 CET, Jaroslav Tulach napsal(a):
> > >>>> > > Hello Emilian, Matthias & everyone.
> > >>>> > >
> > >>>> > > Dne sobota 12. ledna 2019 9:38:53 CET, Emilian Bold napsal(a):
> > >>>> > > > I see the parser source is here
> > >>>> > > >
> > >>>> >
> > >>>>
> >
> https://github.com/graalvm/graaljs/tree/master/graal-js/src/com.oracle.js
> > >>>> .
> > >>>> > > > pa rser but it's not compiled as an independent JAR available
> in
> > >>>> Maven
> > >>>> > > > Central. Could the GraalVM project do this?
> > >>>> > > >
> > >>>> > > > The whole org.graalvm.js:js seems pretty big and has many
> > >>>> > > > dependencies. We just need the parser.
> > >>>> > >
> > >>>> > > Let's consider this in the context of 371465581f2011 and PR-1011
> > and
> > >>>> > > NETBEANS-1009.
> > >>>> > >
> > >>>> > > #1 - Nashorn isn't the future of JavaScript engines on JDK. We
> > will
> > >>>> need
> > >>>> > > another engine anyway in the future.
> > >>>> > >
> > >>>> > > #2 - Emilian commented in PR-1011 that using Graal.js from
> > >>>> bootclasspath
> > >>>> > > isn't appropriate
> > >>>> > >
> > >>>> > > #3 - We need parts of Graal.js anyway for the editing support
> > >>>> > >
> > >>>> > > #4 - OracleLabs (my employer) supports wider use of Graal.js
> > >>>> > >
> > >>>> > > When I look at the parser issue from a broader perspective, I
> > >>>> propose to:
> > >>>> > >
> > >>>> > > * modify PR-1011 to bundle whole Graal.js and necessary
> libraries
> > >>>> > >
> > >>>> > > that will solve #1, #2, #4. Then we need another PR to modify
> the
> > >>>> > JavaScript
> > >>>> > > editing infrastructure to use the new version of the Graal.js
> > >>>> parser. I
> > >>>> > was
> > >>>> > > hoping Svatopluk Dědic could take care of that, but as he is
> busy
> > >>>> with
> > >>>> > > other tasks, help from community would be more than welcomed.
> > Anyone
> > >>>> > > interested in supporting EcmaScript7 features (syntax of which
> the
> > >>>> newest
> > >>>> > > version of Graal.js handles) in NetBeans?
> > >>>> > >
> > >>>> > > I'll work on modifying the PR-1011 to include Graal.js as a
> > library
> > >>>> on
> > >>>> > > Monday, next week.
> > >>>> > > -jt
> > >>>> >
> > >>>> >
> > >>>> >
> > >>>> >
> > >>>> >
> > >>>> >
> > ---------------------------------------------------------------------
> > >>>> > To unsubscribe, e-mail:
> > dev-unsubscribe@netbeans.incubator.apache.org
> > >>>> > For additional commands, e-mail:
> > >>>> dev-help@netbeans.incubator.apache.org
> > >>>> >
> > >>>> > For further information about the NetBeans mailing lists, visit:
> > >>>> >
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> > >>>> >
> > >>>> >
> > >>>> >
> > >>>> >
> > >>>>
> > >>>>
> >
>
>
AW: Help, JavaScript fans! was: Use Graal.js (parser) for NetBeans
11
Posted by Christian Lenz <ch...@gmx.net>.
Hey Jaroslav,
I have a Question About this test here: https://builds.apache.org/job/incubator-netbeans-jsparser/6/testReport/org.netbeans.modules.javascript2.editor/JsCodeCompletionES6Test/testClassName01/
Does that mean, that graal can’t handle ES6 atm or do I understand smth wrong? Because the expected result should be „CLASS“ but the completion says it is „VARIABLE“.
Can you help me here to understand that?
Cheers
Chris
Von: Jaroslav Tulach
Gesendet: Dienstag, 29. Januar 2019 15:33
An: Apache NetBeans
Betreff: Re: Help, JavaScript fans! was: Use Graal.js (parser) for NetBeans 11
Hail JavaScript!
One of the common questions is how many of those more than six hundred
failures are related to switch of the parser from Nashorn to Graal.js. To
answer that question I have set another job up:
https://builds.apache.org/job/incubator-netbeans-jsparser-tests/
it does the same test as
https://builds.apache.org/job/incubator-netbeans-jsparser/
<https://builds.apache.org/job/incubator-netbeans-jsparser/lastCompletedBuild/testReport/org.netbeans.modules.javascript2.sdoc/SDocCompletionDocumentationTest/testCompletionDocumentation01/>
but it takes the sources from master branch. There seems to be 129 failures
in the master branch. That is a lot and it would be nice to fix them, but...
It means that there is more than five hundred failures that are somehow
related to the parser change. I assume that means the branch isn't in
mergable state right now. Your help is needed!
Fix a test! Make NetBeans better!
-jt
pá 25. 1. 2019 v 19:38 odesílatel Geertjan Wielenga
<ge...@googlemail.com.invalid> napsal:
> Investigated the ones starting with this one (there are 11 others) but
> couldn't figure it out:
>
>
> https://builds.apache.org/job/incubator-netbeans-jsparser/lastCompletedBuild/testReport/org.netbeans.modules.javascript2.sdoc/SDocCompletionDocumentationTest/testCompletionDocumentation01/
>
> Gj
>
> On Fri, Jan 25, 2019 at 3:59 PM Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
> > Would it be true to say that the majority, or at least many, of these
> > failing tests were already failing before the introduction of the
> Graal.js
> > parser?
> >
> > Gj
> >
> >
> > On Fri, Jan 25, 2019 at 3:50 PM Geertjan Wielenga <
> > geertjan.wielenga@googlemail.com> wrote:
> >
> >> Well, that issue probably doesn't make sense since we're checking in
> >> directly into Svata's repo, right?
> >>
> >> Anyway, let me know if this makes sense, if not, tell me how to do it
> >> differently:
> >>
> >>
> >>
> https://github.com/sdedic/incubator-netbeans/commit/908659392359671f7166566294b20c14e8d71232
> >>
> >> Gj
> >>
> >>
> >> On Fri, Jan 25, 2019 at 2:51 PM Geertjan Wielenga <
> >> geertjan.wielenga@googlemail.com> wrote:
> >>
> >>> Not sure if there is an issue yet for fixing the failing tests, created
> >>> it and will be referencing this in my pull requests:
> >>>
> >>> https://issues.apache.org/jira/browse/NETBEANS-1990
> >>>
> >>> Gj
> >>>
> >>>
> >>> On Fri, Jan 25, 2019 at 2:37 PM Christian Lenz <christian.lenz@gmx.net
> >
> >>> wrote:
> >>>
> >>>> Will try to help on the weekend. Maybe.
> >>>>
> >>>>
> >>>> Cheers
> >>>>
> >>>> Chris
> >>>>
> >>>>
> >>>>
> >>>> Von: Jaroslav Tulach
> >>>> Gesendet: Freitag, 25. Januar 2019 13:18
> >>>> An: Apache NetBeans
> >>>> Cc: Svata Dedic
> >>>> Betreff: Help, JavaScript fans! was: Use Graal.js (parser) for
> NetBeans
> >>>> 11
> >>>>
> >>>> I assume there is a lot of people interested in support of modern
> >>>> JavaScript, right? We need you help:
> >>>>
> >>>> čt 24. 1. 2019 v 5:59 odesílatel Jaroslav Tulach <
> >>>> jaroslav.tulach@oracle.com>
> >>>> napsal:
> >>>> >
> >>>> > The PR-1011 is in.
> >>>> >
> >>>> > Somebody needs to start working on rewriting the `webcommon/
> >>>> > javascript2.editor/` to use the parser in `webcommon.libs.graaljs`.
> >>>>
> >>>>
> >>>>
> >>>> Sváťa created a PR:
> >>>> https://github.com/apache/incubator-netbeans/pull/1099,
> >>>> but it cannot be merged until the code is rewritten to use the new
> >>>> version
> >>>> of the parser and work correctly. There is a Jenkins job that tracks
> the
> >>>> status:
> >>>>
> >>>> https://builds.apache.org/job/incubator-netbeans-jsparser/
> >>>>
> >>>> Right now we have 693 failures. Please help us fix them. The
> >>>> instructions
> >>>> are given in the job description, and it should be fairly easy. Get
> the
> >>>> repository:
> >>>>
> >>>> git clone https://github.com/sdedic/incubator-netbeans.git
> >>>> cd incubator-netbeans
> >>>> git checkout experimental/graaljs_parser
> >>>>
> >>>> and then build it all and check the tests:
> >>>>
> >>>> ant build
> >>>> for i in webcommon/*; do
> >>>> (cd $i; ant test-unit -Dcontinue.after.failing.tests=true)
> >>>> done
> >>>>
> >>>> You can open any module under webcommon in the NetBeans IDE, select a
> >>>> test
> >>>> and run or debug it.
> >>>>
> >>>> If you care about JavaScript, please help: Fix a test. Make NetBeans
> >>>> better!
> >>>> -jt
> >>>>
> >>>>
> >>>>
> >>>> > Dne neděle 13. ledna 2019 5:24:04 CET, Jaroslav Tulach napsal(a):
> >>>> > > Hello Emilian, Matthias & everyone.
> >>>> > >
> >>>> > > Dne sobota 12. ledna 2019 9:38:53 CET, Emilian Bold napsal(a):
> >>>> > > > I see the parser source is here
> >>>> > > >
> >>>> >
> >>>>
> https://github.com/graalvm/graaljs/tree/master/graal-js/src/com.oracle.js
> >>>> .
> >>>> > > > pa rser but it's not compiled as an independent JAR available in
> >>>> Maven
> >>>> > > > Central. Could the GraalVM project do this?
> >>>> > > >
> >>>> > > > The whole org.graalvm.js:js seems pretty big and has many
> >>>> > > > dependencies. We just need the parser.
> >>>> > >
> >>>> > > Let's consider this in the context of 371465581f2011 and PR-1011
> and
> >>>> > > NETBEANS-1009.
> >>>> > >
> >>>> > > #1 - Nashorn isn't the future of JavaScript engines on JDK. We
> will
> >>>> need
> >>>> > > another engine anyway in the future.
> >>>> > >
> >>>> > > #2 - Emilian commented in PR-1011 that using Graal.js from
> >>>> bootclasspath
> >>>> > > isn't appropriate
> >>>> > >
> >>>> > > #3 - We need parts of Graal.js anyway for the editing support
> >>>> > >
> >>>> > > #4 - OracleLabs (my employer) supports wider use of Graal.js
> >>>> > >
> >>>> > > When I look at the parser issue from a broader perspective, I
> >>>> propose to:
> >>>> > >
> >>>> > > * modify PR-1011 to bundle whole Graal.js and necessary libraries
> >>>> > >
> >>>> > > that will solve #1, #2, #4. Then we need another PR to modify the
> >>>> > JavaScript
> >>>> > > editing infrastructure to use the new version of the Graal.js
> >>>> parser. I
> >>>> > was
> >>>> > > hoping Svatopluk Dědic could take care of that, but as he is busy
> >>>> with
> >>>> > > other tasks, help from community would be more than welcomed.
> Anyone
> >>>> > > interested in supporting EcmaScript7 features (syntax of which the
> >>>> newest
> >>>> > > version of Graal.js handles) in NetBeans?
> >>>> > >
> >>>> > > I'll work on modifying the PR-1011 to include Graal.js as a
> library
> >>>> on
> >>>> > > Monday, next week.
> >>>> > > -jt
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> ---------------------------------------------------------------------
> >>>> > To unsubscribe, e-mail:
> dev-unsubscribe@netbeans.incubator.apache.org
> >>>> > For additional commands, e-mail:
> >>>> dev-help@netbeans.incubator.apache.org
> >>>> >
> >>>> > For further information about the NetBeans mailing lists, visit:
> >>>> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>>
> >>>>
>
Re: Help, JavaScript fans! was: Use Graal.js (parser) for NetBeans 11
Posted by Jaroslav Tulach <ja...@gmail.com>.
Hail JavaScript!
One of the common questions is how many of those more than six hundred
failures are related to switch of the parser from Nashorn to Graal.js. To
answer that question I have set another job up:
https://builds.apache.org/job/incubator-netbeans-jsparser-tests/
it does the same test as
https://builds.apache.org/job/incubator-netbeans-jsparser/
<https://builds.apache.org/job/incubator-netbeans-jsparser/lastCompletedBuild/testReport/org.netbeans.modules.javascript2.sdoc/SDocCompletionDocumentationTest/testCompletionDocumentation01/>
but it takes the sources from master branch. There seems to be 129 failures
in the master branch. That is a lot and it would be nice to fix them, but...
It means that there is more than five hundred failures that are somehow
related to the parser change. I assume that means the branch isn't in
mergable state right now. Your help is needed!
Fix a test! Make NetBeans better!
-jt
pá 25. 1. 2019 v 19:38 odesílatel Geertjan Wielenga
<ge...@googlemail.com.invalid> napsal:
> Investigated the ones starting with this one (there are 11 others) but
> couldn't figure it out:
>
>
> https://builds.apache.org/job/incubator-netbeans-jsparser/lastCompletedBuild/testReport/org.netbeans.modules.javascript2.sdoc/SDocCompletionDocumentationTest/testCompletionDocumentation01/
>
> Gj
>
> On Fri, Jan 25, 2019 at 3:59 PM Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
> > Would it be true to say that the majority, or at least many, of these
> > failing tests were already failing before the introduction of the
> Graal.js
> > parser?
> >
> > Gj
> >
> >
> > On Fri, Jan 25, 2019 at 3:50 PM Geertjan Wielenga <
> > geertjan.wielenga@googlemail.com> wrote:
> >
> >> Well, that issue probably doesn't make sense since we're checking in
> >> directly into Svata's repo, right?
> >>
> >> Anyway, let me know if this makes sense, if not, tell me how to do it
> >> differently:
> >>
> >>
> >>
> https://github.com/sdedic/incubator-netbeans/commit/908659392359671f7166566294b20c14e8d71232
> >>
> >> Gj
> >>
> >>
> >> On Fri, Jan 25, 2019 at 2:51 PM Geertjan Wielenga <
> >> geertjan.wielenga@googlemail.com> wrote:
> >>
> >>> Not sure if there is an issue yet for fixing the failing tests, created
> >>> it and will be referencing this in my pull requests:
> >>>
> >>> https://issues.apache.org/jira/browse/NETBEANS-1990
> >>>
> >>> Gj
> >>>
> >>>
> >>> On Fri, Jan 25, 2019 at 2:37 PM Christian Lenz <christian.lenz@gmx.net
> >
> >>> wrote:
> >>>
> >>>> Will try to help on the weekend. Maybe.
> >>>>
> >>>>
> >>>> Cheers
> >>>>
> >>>> Chris
> >>>>
> >>>>
> >>>>
> >>>> Von: Jaroslav Tulach
> >>>> Gesendet: Freitag, 25. Januar 2019 13:18
> >>>> An: Apache NetBeans
> >>>> Cc: Svata Dedic
> >>>> Betreff: Help, JavaScript fans! was: Use Graal.js (parser) for
> NetBeans
> >>>> 11
> >>>>
> >>>> I assume there is a lot of people interested in support of modern
> >>>> JavaScript, right? We need you help:
> >>>>
> >>>> čt 24. 1. 2019 v 5:59 odesílatel Jaroslav Tulach <
> >>>> jaroslav.tulach@oracle.com>
> >>>> napsal:
> >>>> >
> >>>> > The PR-1011 is in.
> >>>> >
> >>>> > Somebody needs to start working on rewriting the `webcommon/
> >>>> > javascript2.editor/` to use the parser in `webcommon.libs.graaljs`.
> >>>>
> >>>>
> >>>>
> >>>> Sváťa created a PR:
> >>>> https://github.com/apache/incubator-netbeans/pull/1099,
> >>>> but it cannot be merged until the code is rewritten to use the new
> >>>> version
> >>>> of the parser and work correctly. There is a Jenkins job that tracks
> the
> >>>> status:
> >>>>
> >>>> https://builds.apache.org/job/incubator-netbeans-jsparser/
> >>>>
> >>>> Right now we have 693 failures. Please help us fix them. The
> >>>> instructions
> >>>> are given in the job description, and it should be fairly easy. Get
> the
> >>>> repository:
> >>>>
> >>>> git clone https://github.com/sdedic/incubator-netbeans.git
> >>>> cd incubator-netbeans
> >>>> git checkout experimental/graaljs_parser
> >>>>
> >>>> and then build it all and check the tests:
> >>>>
> >>>> ant build
> >>>> for i in webcommon/*; do
> >>>> (cd $i; ant test-unit -Dcontinue.after.failing.tests=true)
> >>>> done
> >>>>
> >>>> You can open any module under webcommon in the NetBeans IDE, select a
> >>>> test
> >>>> and run or debug it.
> >>>>
> >>>> If you care about JavaScript, please help: Fix a test. Make NetBeans
> >>>> better!
> >>>> -jt
> >>>>
> >>>>
> >>>>
> >>>> > Dne neděle 13. ledna 2019 5:24:04 CET, Jaroslav Tulach napsal(a):
> >>>> > > Hello Emilian, Matthias & everyone.
> >>>> > >
> >>>> > > Dne sobota 12. ledna 2019 9:38:53 CET, Emilian Bold napsal(a):
> >>>> > > > I see the parser source is here
> >>>> > > >
> >>>> >
> >>>>
> https://github.com/graalvm/graaljs/tree/master/graal-js/src/com.oracle.js
> >>>> .
> >>>> > > > pa rser but it's not compiled as an independent JAR available in
> >>>> Maven
> >>>> > > > Central. Could the GraalVM project do this?
> >>>> > > >
> >>>> > > > The whole org.graalvm.js:js seems pretty big and has many
> >>>> > > > dependencies. We just need the parser.
> >>>> > >
> >>>> > > Let's consider this in the context of 371465581f2011 and PR-1011
> and
> >>>> > > NETBEANS-1009.
> >>>> > >
> >>>> > > #1 - Nashorn isn't the future of JavaScript engines on JDK. We
> will
> >>>> need
> >>>> > > another engine anyway in the future.
> >>>> > >
> >>>> > > #2 - Emilian commented in PR-1011 that using Graal.js from
> >>>> bootclasspath
> >>>> > > isn't appropriate
> >>>> > >
> >>>> > > #3 - We need parts of Graal.js anyway for the editing support
> >>>> > >
> >>>> > > #4 - OracleLabs (my employer) supports wider use of Graal.js
> >>>> > >
> >>>> > > When I look at the parser issue from a broader perspective, I
> >>>> propose to:
> >>>> > >
> >>>> > > * modify PR-1011 to bundle whole Graal.js and necessary libraries
> >>>> > >
> >>>> > > that will solve #1, #2, #4. Then we need another PR to modify the
> >>>> > JavaScript
> >>>> > > editing infrastructure to use the new version of the Graal.js
> >>>> parser. I
> >>>> > was
> >>>> > > hoping Svatopluk Dědic could take care of that, but as he is busy
> >>>> with
> >>>> > > other tasks, help from community would be more than welcomed.
> Anyone
> >>>> > > interested in supporting EcmaScript7 features (syntax of which the
> >>>> newest
> >>>> > > version of Graal.js handles) in NetBeans?
> >>>> > >
> >>>> > > I'll work on modifying the PR-1011 to include Graal.js as a
> library
> >>>> on
> >>>> > > Monday, next week.
> >>>> > > -jt
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> ---------------------------------------------------------------------
> >>>> > To unsubscribe, e-mail:
> dev-unsubscribe@netbeans.incubator.apache.org
> >>>> > For additional commands, e-mail:
> >>>> dev-help@netbeans.incubator.apache.org
> >>>> >
> >>>> > For further information about the NetBeans mailing lists, visit:
> >>>> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >>>> >
> >>>> >
> >>>> >
> >>>> >
> >>>>
> >>>>
>
Re: Help, JavaScript fans! was: Use Graal.js (parser) for NetBeans 11
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Investigated the ones starting with this one (there are 11 others) but
couldn't figure it out:
https://builds.apache.org/job/incubator-netbeans-jsparser/lastCompletedBuild/testReport/org.netbeans.modules.javascript2.sdoc/SDocCompletionDocumentationTest/testCompletionDocumentation01/
Gj
On Fri, Jan 25, 2019 at 3:59 PM Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:
> Would it be true to say that the majority, or at least many, of these
> failing tests were already failing before the introduction of the Graal.js
> parser?
>
> Gj
>
>
> On Fri, Jan 25, 2019 at 3:50 PM Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
>> Well, that issue probably doesn't make sense since we're checking in
>> directly into Svata's repo, right?
>>
>> Anyway, let me know if this makes sense, if not, tell me how to do it
>> differently:
>>
>>
>> https://github.com/sdedic/incubator-netbeans/commit/908659392359671f7166566294b20c14e8d71232
>>
>> Gj
>>
>>
>> On Fri, Jan 25, 2019 at 2:51 PM Geertjan Wielenga <
>> geertjan.wielenga@googlemail.com> wrote:
>>
>>> Not sure if there is an issue yet for fixing the failing tests, created
>>> it and will be referencing this in my pull requests:
>>>
>>> https://issues.apache.org/jira/browse/NETBEANS-1990
>>>
>>> Gj
>>>
>>>
>>> On Fri, Jan 25, 2019 at 2:37 PM Christian Lenz <ch...@gmx.net>
>>> wrote:
>>>
>>>> Will try to help on the weekend. Maybe.
>>>>
>>>>
>>>> Cheers
>>>>
>>>> Chris
>>>>
>>>>
>>>>
>>>> Von: Jaroslav Tulach
>>>> Gesendet: Freitag, 25. Januar 2019 13:18
>>>> An: Apache NetBeans
>>>> Cc: Svata Dedic
>>>> Betreff: Help, JavaScript fans! was: Use Graal.js (parser) for NetBeans
>>>> 11
>>>>
>>>> I assume there is a lot of people interested in support of modern
>>>> JavaScript, right? We need you help:
>>>>
>>>> čt 24. 1. 2019 v 5:59 odesílatel Jaroslav Tulach <
>>>> jaroslav.tulach@oracle.com>
>>>> napsal:
>>>> >
>>>> > The PR-1011 is in.
>>>> >
>>>> > Somebody needs to start working on rewriting the `webcommon/
>>>> > javascript2.editor/` to use the parser in `webcommon.libs.graaljs`.
>>>>
>>>>
>>>>
>>>> Sváťa created a PR:
>>>> https://github.com/apache/incubator-netbeans/pull/1099,
>>>> but it cannot be merged until the code is rewritten to use the new
>>>> version
>>>> of the parser and work correctly. There is a Jenkins job that tracks the
>>>> status:
>>>>
>>>> https://builds.apache.org/job/incubator-netbeans-jsparser/
>>>>
>>>> Right now we have 693 failures. Please help us fix them. The
>>>> instructions
>>>> are given in the job description, and it should be fairly easy. Get the
>>>> repository:
>>>>
>>>> git clone https://github.com/sdedic/incubator-netbeans.git
>>>> cd incubator-netbeans
>>>> git checkout experimental/graaljs_parser
>>>>
>>>> and then build it all and check the tests:
>>>>
>>>> ant build
>>>> for i in webcommon/*; do
>>>> (cd $i; ant test-unit -Dcontinue.after.failing.tests=true)
>>>> done
>>>>
>>>> You can open any module under webcommon in the NetBeans IDE, select a
>>>> test
>>>> and run or debug it.
>>>>
>>>> If you care about JavaScript, please help: Fix a test. Make NetBeans
>>>> better!
>>>> -jt
>>>>
>>>>
>>>>
>>>> > Dne neděle 13. ledna 2019 5:24:04 CET, Jaroslav Tulach napsal(a):
>>>> > > Hello Emilian, Matthias & everyone.
>>>> > >
>>>> > > Dne sobota 12. ledna 2019 9:38:53 CET, Emilian Bold napsal(a):
>>>> > > > I see the parser source is here
>>>> > > >
>>>> >
>>>> https://github.com/graalvm/graaljs/tree/master/graal-js/src/com.oracle.js
>>>> .
>>>> > > > pa rser but it's not compiled as an independent JAR available in
>>>> Maven
>>>> > > > Central. Could the GraalVM project do this?
>>>> > > >
>>>> > > > The whole org.graalvm.js:js seems pretty big and has many
>>>> > > > dependencies. We just need the parser.
>>>> > >
>>>> > > Let's consider this in the context of 371465581f2011 and PR-1011 and
>>>> > > NETBEANS-1009.
>>>> > >
>>>> > > #1 - Nashorn isn't the future of JavaScript engines on JDK. We will
>>>> need
>>>> > > another engine anyway in the future.
>>>> > >
>>>> > > #2 - Emilian commented in PR-1011 that using Graal.js from
>>>> bootclasspath
>>>> > > isn't appropriate
>>>> > >
>>>> > > #3 - We need parts of Graal.js anyway for the editing support
>>>> > >
>>>> > > #4 - OracleLabs (my employer) supports wider use of Graal.js
>>>> > >
>>>> > > When I look at the parser issue from a broader perspective, I
>>>> propose to:
>>>> > >
>>>> > > * modify PR-1011 to bundle whole Graal.js and necessary libraries
>>>> > >
>>>> > > that will solve #1, #2, #4. Then we need another PR to modify the
>>>> > JavaScript
>>>> > > editing infrastructure to use the new version of the Graal.js
>>>> parser. I
>>>> > was
>>>> > > hoping Svatopluk Dědic could take care of that, but as he is busy
>>>> with
>>>> > > other tasks, help from community would be more than welcomed. Anyone
>>>> > > interested in supporting EcmaScript7 features (syntax of which the
>>>> newest
>>>> > > version of Graal.js handles) in NetBeans?
>>>> > >
>>>> > > I'll work on modifying the PR-1011 to include Graal.js as a library
>>>> on
>>>> > > Monday, next week.
>>>> > > -jt
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> > ---------------------------------------------------------------------
>>>> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>>> > For additional commands, e-mail:
>>>> dev-help@netbeans.incubator.apache.org
>>>> >
>>>> > For further information about the NetBeans mailing lists, visit:
>>>> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>>> >
>>>> >
>>>> >
>>>> >
>>>>
>>>>
Re: Help, JavaScript fans! was: Use Graal.js (parser) for NetBeans 11
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Would it be true to say that the majority, or at least many, of these
failing tests were already failing before the introduction of the Graal.js
parser?
Gj
On Fri, Jan 25, 2019 at 3:50 PM Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:
> Well, that issue probably doesn't make sense since we're checking in
> directly into Svata's repo, right?
>
> Anyway, let me know if this makes sense, if not, tell me how to do it
> differently:
>
>
> https://github.com/sdedic/incubator-netbeans/commit/908659392359671f7166566294b20c14e8d71232
>
> Gj
>
>
> On Fri, Jan 25, 2019 at 2:51 PM Geertjan Wielenga <
> geertjan.wielenga@googlemail.com> wrote:
>
>> Not sure if there is an issue yet for fixing the failing tests, created
>> it and will be referencing this in my pull requests:
>>
>> https://issues.apache.org/jira/browse/NETBEANS-1990
>>
>> Gj
>>
>>
>> On Fri, Jan 25, 2019 at 2:37 PM Christian Lenz <ch...@gmx.net>
>> wrote:
>>
>>> Will try to help on the weekend. Maybe.
>>>
>>>
>>> Cheers
>>>
>>> Chris
>>>
>>>
>>>
>>> Von: Jaroslav Tulach
>>> Gesendet: Freitag, 25. Januar 2019 13:18
>>> An: Apache NetBeans
>>> Cc: Svata Dedic
>>> Betreff: Help, JavaScript fans! was: Use Graal.js (parser) for NetBeans
>>> 11
>>>
>>> I assume there is a lot of people interested in support of modern
>>> JavaScript, right? We need you help:
>>>
>>> čt 24. 1. 2019 v 5:59 odesílatel Jaroslav Tulach <
>>> jaroslav.tulach@oracle.com>
>>> napsal:
>>> >
>>> > The PR-1011 is in.
>>> >
>>> > Somebody needs to start working on rewriting the `webcommon/
>>> > javascript2.editor/` to use the parser in `webcommon.libs.graaljs`.
>>>
>>>
>>>
>>> Sváťa created a PR:
>>> https://github.com/apache/incubator-netbeans/pull/1099,
>>> but it cannot be merged until the code is rewritten to use the new
>>> version
>>> of the parser and work correctly. There is a Jenkins job that tracks the
>>> status:
>>>
>>> https://builds.apache.org/job/incubator-netbeans-jsparser/
>>>
>>> Right now we have 693 failures. Please help us fix them. The instructions
>>> are given in the job description, and it should be fairly easy. Get the
>>> repository:
>>>
>>> git clone https://github.com/sdedic/incubator-netbeans.git
>>> cd incubator-netbeans
>>> git checkout experimental/graaljs_parser
>>>
>>> and then build it all and check the tests:
>>>
>>> ant build
>>> for i in webcommon/*; do
>>> (cd $i; ant test-unit -Dcontinue.after.failing.tests=true)
>>> done
>>>
>>> You can open any module under webcommon in the NetBeans IDE, select a
>>> test
>>> and run or debug it.
>>>
>>> If you care about JavaScript, please help: Fix a test. Make NetBeans
>>> better!
>>> -jt
>>>
>>>
>>>
>>> > Dne neděle 13. ledna 2019 5:24:04 CET, Jaroslav Tulach napsal(a):
>>> > > Hello Emilian, Matthias & everyone.
>>> > >
>>> > > Dne sobota 12. ledna 2019 9:38:53 CET, Emilian Bold napsal(a):
>>> > > > I see the parser source is here
>>> > > >
>>> >
>>> https://github.com/graalvm/graaljs/tree/master/graal-js/src/com.oracle.js
>>> .
>>> > > > pa rser but it's not compiled as an independent JAR available in
>>> Maven
>>> > > > Central. Could the GraalVM project do this?
>>> > > >
>>> > > > The whole org.graalvm.js:js seems pretty big and has many
>>> > > > dependencies. We just need the parser.
>>> > >
>>> > > Let's consider this in the context of 371465581f2011 and PR-1011 and
>>> > > NETBEANS-1009.
>>> > >
>>> > > #1 - Nashorn isn't the future of JavaScript engines on JDK. We will
>>> need
>>> > > another engine anyway in the future.
>>> > >
>>> > > #2 - Emilian commented in PR-1011 that using Graal.js from
>>> bootclasspath
>>> > > isn't appropriate
>>> > >
>>> > > #3 - We need parts of Graal.js anyway for the editing support
>>> > >
>>> > > #4 - OracleLabs (my employer) supports wider use of Graal.js
>>> > >
>>> > > When I look at the parser issue from a broader perspective, I
>>> propose to:
>>> > >
>>> > > * modify PR-1011 to bundle whole Graal.js and necessary libraries
>>> > >
>>> > > that will solve #1, #2, #4. Then we need another PR to modify the
>>> > JavaScript
>>> > > editing infrastructure to use the new version of the Graal.js
>>> parser. I
>>> > was
>>> > > hoping Svatopluk Dědic could take care of that, but as he is busy
>>> with
>>> > > other tasks, help from community would be more than welcomed. Anyone
>>> > > interested in supporting EcmaScript7 features (syntax of which the
>>> newest
>>> > > version of Graal.js handles) in NetBeans?
>>> > >
>>> > > I'll work on modifying the PR-1011 to include Graal.js as a library
>>> on
>>> > > Monday, next week.
>>> > > -jt
>>> >
>>> >
>>> >
>>> >
>>> >
>>> > ---------------------------------------------------------------------
>>> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>>> > For additional commands, e-mail:
>>> dev-help@netbeans.incubator.apache.org
>>> >
>>> > For further information about the NetBeans mailing lists, visit:
>>> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>>> >
>>> >
>>> >
>>> >
>>>
>>>
Re: Help, JavaScript fans! was: Use Graal.js (parser) for NetBeans 11
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Well, that issue probably doesn't make sense since we're checking in
directly into Svata's repo, right?
Anyway, let me know if this makes sense, if not, tell me how to do it
differently:
https://github.com/sdedic/incubator-netbeans/commit/908659392359671f7166566294b20c14e8d71232
Gj
On Fri, Jan 25, 2019 at 2:51 PM Geertjan Wielenga <
geertjan.wielenga@googlemail.com> wrote:
> Not sure if there is an issue yet for fixing the failing tests, created it
> and will be referencing this in my pull requests:
>
> https://issues.apache.org/jira/browse/NETBEANS-1990
>
> Gj
>
>
> On Fri, Jan 25, 2019 at 2:37 PM Christian Lenz <ch...@gmx.net>
> wrote:
>
>> Will try to help on the weekend. Maybe.
>>
>>
>> Cheers
>>
>> Chris
>>
>>
>>
>> Von: Jaroslav Tulach
>> Gesendet: Freitag, 25. Januar 2019 13:18
>> An: Apache NetBeans
>> Cc: Svata Dedic
>> Betreff: Help, JavaScript fans! was: Use Graal.js (parser) for NetBeans 11
>>
>> I assume there is a lot of people interested in support of modern
>> JavaScript, right? We need you help:
>>
>> čt 24. 1. 2019 v 5:59 odesílatel Jaroslav Tulach <
>> jaroslav.tulach@oracle.com>
>> napsal:
>> >
>> > The PR-1011 is in.
>> >
>> > Somebody needs to start working on rewriting the `webcommon/
>> > javascript2.editor/` to use the parser in `webcommon.libs.graaljs`.
>>
>>
>>
>> Sváťa created a PR:
>> https://github.com/apache/incubator-netbeans/pull/1099,
>> but it cannot be merged until the code is rewritten to use the new version
>> of the parser and work correctly. There is a Jenkins job that tracks the
>> status:
>>
>> https://builds.apache.org/job/incubator-netbeans-jsparser/
>>
>> Right now we have 693 failures. Please help us fix them. The instructions
>> are given in the job description, and it should be fairly easy. Get the
>> repository:
>>
>> git clone https://github.com/sdedic/incubator-netbeans.git
>> cd incubator-netbeans
>> git checkout experimental/graaljs_parser
>>
>> and then build it all and check the tests:
>>
>> ant build
>> for i in webcommon/*; do
>> (cd $i; ant test-unit -Dcontinue.after.failing.tests=true)
>> done
>>
>> You can open any module under webcommon in the NetBeans IDE, select a test
>> and run or debug it.
>>
>> If you care about JavaScript, please help: Fix a test. Make NetBeans
>> better!
>> -jt
>>
>>
>>
>> > Dne neděle 13. ledna 2019 5:24:04 CET, Jaroslav Tulach napsal(a):
>> > > Hello Emilian, Matthias & everyone.
>> > >
>> > > Dne sobota 12. ledna 2019 9:38:53 CET, Emilian Bold napsal(a):
>> > > > I see the parser source is here
>> > > >
>> >
>> https://github.com/graalvm/graaljs/tree/master/graal-js/src/com.oracle.js
>> .
>> > > > pa rser but it's not compiled as an independent JAR available in
>> Maven
>> > > > Central. Could the GraalVM project do this?
>> > > >
>> > > > The whole org.graalvm.js:js seems pretty big and has many
>> > > > dependencies. We just need the parser.
>> > >
>> > > Let's consider this in the context of 371465581f2011 and PR-1011 and
>> > > NETBEANS-1009.
>> > >
>> > > #1 - Nashorn isn't the future of JavaScript engines on JDK. We will
>> need
>> > > another engine anyway in the future.
>> > >
>> > > #2 - Emilian commented in PR-1011 that using Graal.js from
>> bootclasspath
>> > > isn't appropriate
>> > >
>> > > #3 - We need parts of Graal.js anyway for the editing support
>> > >
>> > > #4 - OracleLabs (my employer) supports wider use of Graal.js
>> > >
>> > > When I look at the parser issue from a broader perspective, I propose
>> to:
>> > >
>> > > * modify PR-1011 to bundle whole Graal.js and necessary libraries
>> > >
>> > > that will solve #1, #2, #4. Then we need another PR to modify the
>> > JavaScript
>> > > editing infrastructure to use the new version of the Graal.js parser.
>> I
>> > was
>> > > hoping Svatopluk Dědic could take care of that, but as he is busy with
>> > > other tasks, help from community would be more than welcomed. Anyone
>> > > interested in supporting EcmaScript7 features (syntax of which the
>> newest
>> > > version of Graal.js handles) in NetBeans?
>> > >
>> > > I'll work on modifying the PR-1011 to include Graal.js as a library on
>> > > Monday, next week.
>> > > -jt
>> >
>> >
>> >
>> >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
>> > For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>> >
>> > For further information about the NetBeans mailing lists, visit:
>> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>> >
>> >
>> >
>> >
>>
>>
Re: Help, JavaScript fans! was: Use Graal.js (parser) for NetBeans 11
Posted by Geertjan Wielenga <ge...@googlemail.com.INVALID>.
Not sure if there is an issue yet for fixing the failing tests, created it
and will be referencing this in my pull requests:
https://issues.apache.org/jira/browse/NETBEANS-1990
Gj
On Fri, Jan 25, 2019 at 2:37 PM Christian Lenz <ch...@gmx.net>
wrote:
> Will try to help on the weekend. Maybe.
>
>
> Cheers
>
> Chris
>
>
>
> Von: Jaroslav Tulach
> Gesendet: Freitag, 25. Januar 2019 13:18
> An: Apache NetBeans
> Cc: Svata Dedic
> Betreff: Help, JavaScript fans! was: Use Graal.js (parser) for NetBeans 11
>
> I assume there is a lot of people interested in support of modern
> JavaScript, right? We need you help:
>
> čt 24. 1. 2019 v 5:59 odesílatel Jaroslav Tulach <
> jaroslav.tulach@oracle.com>
> napsal:
> >
> > The PR-1011 is in.
> >
> > Somebody needs to start working on rewriting the `webcommon/
> > javascript2.editor/` to use the parser in `webcommon.libs.graaljs`.
>
>
>
> Sváťa created a PR: https://github.com/apache/incubator-netbeans/pull/1099
> ,
> but it cannot be merged until the code is rewritten to use the new version
> of the parser and work correctly. There is a Jenkins job that tracks the
> status:
>
> https://builds.apache.org/job/incubator-netbeans-jsparser/
>
> Right now we have 693 failures. Please help us fix them. The instructions
> are given in the job description, and it should be fairly easy. Get the
> repository:
>
> git clone https://github.com/sdedic/incubator-netbeans.git
> cd incubator-netbeans
> git checkout experimental/graaljs_parser
>
> and then build it all and check the tests:
>
> ant build
> for i in webcommon/*; do
> (cd $i; ant test-unit -Dcontinue.after.failing.tests=true)
> done
>
> You can open any module under webcommon in the NetBeans IDE, select a test
> and run or debug it.
>
> If you care about JavaScript, please help: Fix a test. Make NetBeans
> better!
> -jt
>
>
>
> > Dne neděle 13. ledna 2019 5:24:04 CET, Jaroslav Tulach napsal(a):
> > > Hello Emilian, Matthias & everyone.
> > >
> > > Dne sobota 12. ledna 2019 9:38:53 CET, Emilian Bold napsal(a):
> > > > I see the parser source is here
> > > >
> >
> https://github.com/graalvm/graaljs/tree/master/graal-js/src/com.oracle.js.
> > > > pa rser but it's not compiled as an independent JAR available in
> Maven
> > > > Central. Could the GraalVM project do this?
> > > >
> > > > The whole org.graalvm.js:js seems pretty big and has many
> > > > dependencies. We just need the parser.
> > >
> > > Let's consider this in the context of 371465581f2011 and PR-1011 and
> > > NETBEANS-1009.
> > >
> > > #1 - Nashorn isn't the future of JavaScript engines on JDK. We will
> need
> > > another engine anyway in the future.
> > >
> > > #2 - Emilian commented in PR-1011 that using Graal.js from
> bootclasspath
> > > isn't appropriate
> > >
> > > #3 - We need parts of Graal.js anyway for the editing support
> > >
> > > #4 - OracleLabs (my employer) supports wider use of Graal.js
> > >
> > > When I look at the parser issue from a broader perspective, I propose
> to:
> > >
> > > * modify PR-1011 to bundle whole Graal.js and necessary libraries
> > >
> > > that will solve #1, #2, #4. Then we need another PR to modify the
> > JavaScript
> > > editing infrastructure to use the new version of the Graal.js parser. I
> > was
> > > hoping Svatopluk Dědic could take care of that, but as he is busy with
> > > other tasks, help from community would be more than welcomed. Anyone
> > > interested in supporting EcmaScript7 features (syntax of which the
> newest
> > > version of Graal.js handles) in NetBeans?
> > >
> > > I'll work on modifying the PR-1011 to include Graal.js as a library on
> > > Monday, next week.
> > > -jt
> >
> >
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> > For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
> >
> > For further information about the NetBeans mailing lists, visit:
> > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
> >
> >
> >
> >
>
>
AW: Help, JavaScript fans! was: Use Graal.js (parser) for NetBeans
11
Posted by Christian Lenz <ch...@gmx.net>.
Will try to help on the weekend. Maybe.
Cheers
Chris
Von: Jaroslav Tulach
Gesendet: Freitag, 25. Januar 2019 13:18
An: Apache NetBeans
Cc: Svata Dedic
Betreff: Help, JavaScript fans! was: Use Graal.js (parser) for NetBeans 11
I assume there is a lot of people interested in support of modern
JavaScript, right? We need you help:
čt 24. 1. 2019 v 5:59 odesílatel Jaroslav Tulach <ja...@oracle.com>
napsal:
>
> The PR-1011 is in.
>
> Somebody needs to start working on rewriting the `webcommon/
> javascript2.editor/` to use the parser in `webcommon.libs.graaljs`.
Sváťa created a PR: https://github.com/apache/incubator-netbeans/pull/1099,
but it cannot be merged until the code is rewritten to use the new version
of the parser and work correctly. There is a Jenkins job that tracks the
status:
https://builds.apache.org/job/incubator-netbeans-jsparser/
Right now we have 693 failures. Please help us fix them. The instructions
are given in the job description, and it should be fairly easy. Get the
repository:
git clone https://github.com/sdedic/incubator-netbeans.git
cd incubator-netbeans
git checkout experimental/graaljs_parser
and then build it all and check the tests:
ant build
for i in webcommon/*; do
(cd $i; ant test-unit -Dcontinue.after.failing.tests=true)
done
You can open any module under webcommon in the NetBeans IDE, select a test
and run or debug it.
If you care about JavaScript, please help: Fix a test. Make NetBeans better!
-jt
> Dne neděle 13. ledna 2019 5:24:04 CET, Jaroslav Tulach napsal(a):
> > Hello Emilian, Matthias & everyone.
> >
> > Dne sobota 12. ledna 2019 9:38:53 CET, Emilian Bold napsal(a):
> > > I see the parser source is here
> > >
> https://github.com/graalvm/graaljs/tree/master/graal-js/src/com.oracle.js.
> > > pa rser but it's not compiled as an independent JAR available in Maven
> > > Central. Could the GraalVM project do this?
> > >
> > > The whole org.graalvm.js:js seems pretty big and has many
> > > dependencies. We just need the parser.
> >
> > Let's consider this in the context of 371465581f2011 and PR-1011 and
> > NETBEANS-1009.
> >
> > #1 - Nashorn isn't the future of JavaScript engines on JDK. We will need
> > another engine anyway in the future.
> >
> > #2 - Emilian commented in PR-1011 that using Graal.js from bootclasspath
> > isn't appropriate
> >
> > #3 - We need parts of Graal.js anyway for the editing support
> >
> > #4 - OracleLabs (my employer) supports wider use of Graal.js
> >
> > When I look at the parser issue from a broader perspective, I propose to:
> >
> > * modify PR-1011 to bundle whole Graal.js and necessary libraries
> >
> > that will solve #1, #2, #4. Then we need another PR to modify the
> JavaScript
> > editing infrastructure to use the new version of the Graal.js parser. I
> was
> > hoping Svatopluk Dědic could take care of that, but as he is busy with
> > other tasks, help from community would be more than welcomed. Anyone
> > interested in supporting EcmaScript7 features (syntax of which the newest
> > version of Graal.js handles) in NetBeans?
> >
> > I'll work on modifying the PR-1011 to include Graal.js as a library on
> > Monday, next week.
> > -jt
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Help, JavaScript fans! was: Use Graal.js (parser) for NetBeans 11
Posted by Jaroslav Tulach <ja...@gmail.com>.
I assume there is a lot of people interested in support of modern
JavaScript, right? We need you help:
čt 24. 1. 2019 v 5:59 odesílatel Jaroslav Tulach <ja...@oracle.com>
napsal:
>
> The PR-1011 is in.
>
> Somebody needs to start working on rewriting the `webcommon/
> javascript2.editor/` to use the parser in `webcommon.libs.graaljs`.
Sváťa created a PR: https://github.com/apache/incubator-netbeans/pull/1099,
but it cannot be merged until the code is rewritten to use the new version
of the parser and work correctly. There is a Jenkins job that tracks the
status:
https://builds.apache.org/job/incubator-netbeans-jsparser/
Right now we have 693 failures. Please help us fix them. The instructions
are given in the job description, and it should be fairly easy. Get the
repository:
git clone https://github.com/sdedic/incubator-netbeans.git
cd incubator-netbeans
git checkout experimental/graaljs_parser
and then build it all and check the tests:
ant build
for i in webcommon/*; do
(cd $i; ant test-unit -Dcontinue.after.failing.tests=true)
done
You can open any module under webcommon in the NetBeans IDE, select a test
and run or debug it.
If you care about JavaScript, please help: Fix a test. Make NetBeans better!
-jt
> Dne neděle 13. ledna 2019 5:24:04 CET, Jaroslav Tulach napsal(a):
> > Hello Emilian, Matthias & everyone.
> >
> > Dne sobota 12. ledna 2019 9:38:53 CET, Emilian Bold napsal(a):
> > > I see the parser source is here
> > >
> https://github.com/graalvm/graaljs/tree/master/graal-js/src/com.oracle.js.
> > > pa rser but it's not compiled as an independent JAR available in Maven
> > > Central. Could the GraalVM project do this?
> > >
> > > The whole org.graalvm.js:js seems pretty big and has many
> > > dependencies. We just need the parser.
> >
> > Let's consider this in the context of 371465581f2011 and PR-1011 and
> > NETBEANS-1009.
> >
> > #1 - Nashorn isn't the future of JavaScript engines on JDK. We will need
> > another engine anyway in the future.
> >
> > #2 - Emilian commented in PR-1011 that using Graal.js from bootclasspath
> > isn't appropriate
> >
> > #3 - We need parts of Graal.js anyway for the editing support
> >
> > #4 - OracleLabs (my employer) supports wider use of Graal.js
> >
> > When I look at the parser issue from a broader perspective, I propose to:
> >
> > * modify PR-1011 to bundle whole Graal.js and necessary libraries
> >
> > that will solve #1, #2, #4. Then we need another PR to modify the
> JavaScript
> > editing infrastructure to use the new version of the Graal.js parser. I
> was
> > hoping Svatopluk Dědic could take care of that, but as he is busy with
> > other tasks, help from community would be more than welcomed. Anyone
> > interested in supporting EcmaScript7 features (syntax of which the newest
> > version of Graal.js handles) in NetBeans?
> >
> > I'll work on modifying the PR-1011 to include Graal.js as a library on
> > Monday, next week.
> > -jt
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: Use Graal.js (parser) for NetBeans 11
Posted by Jaroslav Tulach <ja...@oracle.com>.
The PR-1011 is in.
Somebody needs to start working on rewriting the `webcommon/
javascript2.editor/` to use the parser in `webcommon.libs.graaljs`.
Any volunteers?
-jt
Dne neděle 13. ledna 2019 5:24:04 CET, Jaroslav Tulach napsal(a):
> Hello Emilian, Matthias & everyone.
>
> Dne sobota 12. ledna 2019 9:38:53 CET, Emilian Bold napsal(a):
> > I see the parser source is here
> > https://github.com/graalvm/graaljs/tree/master/graal-js/src/com.oracle.js.
> > pa rser but it's not compiled as an independent JAR available in Maven
> > Central. Could the GraalVM project do this?
> >
> > The whole org.graalvm.js:js seems pretty big and has many
> > dependencies. We just need the parser.
>
> Let's consider this in the context of 371465581f2011 and PR-1011 and
> NETBEANS-1009.
>
> #1 - Nashorn isn't the future of JavaScript engines on JDK. We will need
> another engine anyway in the future.
>
> #2 - Emilian commented in PR-1011 that using Graal.js from bootclasspath
> isn't appropriate
>
> #3 - We need parts of Graal.js anyway for the editing support
>
> #4 - OracleLabs (my employer) supports wider use of Graal.js
>
> When I look at the parser issue from a broader perspective, I propose to:
>
> * modify PR-1011 to bundle whole Graal.js and necessary libraries
>
> that will solve #1, #2, #4. Then we need another PR to modify the JavaScript
> editing infrastructure to use the new version of the Graal.js parser. I was
> hoping Svatopluk Dědic could take care of that, but as he is busy with
> other tasks, help from community would be more than welcomed. Anyone
> interested in supporting EcmaScript7 features (syntax of which the newest
> version of Graal.js handles) in NetBeans?
>
> I'll work on modifying the PR-1011 to include Graal.js as a library on
> Monday, next week.
> -jt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Use Graal.js (parser) for NetBeans 11
Posted by Jaroslav Tulach <ja...@gmail.com>.
Hello Emilian, Matthias & everyone.
Dne sobota 12. ledna 2019 9:38:53 CET, Emilian Bold napsal(a):
> I see the parser source is here
> https://github.com/graalvm/graaljs/tree/master/graal-js/src/com.oracle.js.pa
> rser but it's not compiled as an independent JAR available in Maven
> Central. Could the GraalVM project do this?
>
> The whole org.graalvm.js:js seems pretty big and has many
> dependencies. We just need the parser.
Let's consider this in the context of 371465581f2011 and PR-1011 and
NETBEANS-1009.
#1 - Nashorn isn't the future of JavaScript engines on JDK. We will need
another engine anyway in the future.
#2 - Emilian commented in PR-1011 that using Graal.js from bootclasspath isn't
appropriate
#3 - We need parts of Graal.js anyway for the editing support
#4 - OracleLabs (my employer) supports wider use of Graal.js
When I look at the parser issue from a broader perspective, I propose to:
* modify PR-1011 to bundle whole Graal.js and necessary libraries
that will solve #1, #2, #4. Then we need another PR to modify the JavaScript
editing infrastructure to use the new version of the Graal.js parser. I was
hoping Svatopluk Dědic could take care of that, but as he is busy with other
tasks, help from community would be more than welcomed. Anyone interested in
supporting EcmaScript7 features (syntax of which the newest version of
Graal.js handles) in NetBeans?
I'll work on modifying the PR-1011 to include Graal.js as a library on Monday,
next week.
-jt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
RE: Use Graal.js parser for NetBeans 11 was: Where is `Oracle JS
Parser Implementation` built from?
Posted by Eduardo Quintanilla <eq...@bnext.mx>.
Should the plugin be installed by default(Before opening a Java EE project) as nb-javac plugin?
In my tests if the plugin is not installed before opening a Java EE project(Maven) then Netbeans stops responding.
Eduardo Quintanilla
Software Developer
Block Networks
-----Original Message-----
From: Emilian Bold <em...@gmail.com>
Sent: sábado, 12 de enero de 2019 2:39 a. m.
To: Jaroslav Tulach <ja...@gmail.com>
Cc: NetBeans Dev@ <de...@netbeans.incubator.apache.org>
Subject: Re: Use Graal.js parser for NetBeans 11 was: Where is `Oracle JS Parser Implementation` built from?
I see the parser source is here
https://github.com/graalvm/graaljs/tree/master/graal-js/src/com.oracle.js.parser
but it's not compiled as an independent JAR available in Maven Central. Could the GraalVM project do this?
The whole org.graalvm.js:js seems pretty big and has many dependencies. We just need the parser.
--emi
http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more!
On Sat, Jan 12, 2019 at 9:05 AM Emilian Bold <em...@gmail.com> wrote:
>
> Wow, it's an issue I reported myself :-)
>
> --emi
>
> http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more!
>
> On Sat, Jan 12, 2019 at 9:00 AM Jaroslav Tulach
> <ja...@gmail.com> wrote:
> >
> > Dne pátek 11. ledna 2019 22:14:41 CET, Emilian Bold napsal(a):
> >
> > > This means that we could actually include it in Apache NetBeans,
> >
> > > correct? No need for the run-time plugin.
> >
> >
> >
> > Newer version of lib.nashorn parser is available as org.graalvm.js in Maven repository. It is licensed under friendly UPL license. It is "just" necessary to modify the code to use the new version.
> >
> >
> >
> > I've put that not to
> > https://issues.apache.org/jira/browse/NETBEANS-2
> >
> >
> >
> > We have just one problem: find somebody who does the work...
> >
> > -jt
> >
> >
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Use Graal.js parser for NetBeans 11 was: Where is `Oracle JS
Parser Implementation` built from?
Posted by Emilian Bold <em...@gmail.com>.
I see the parser source is here
https://github.com/graalvm/graaljs/tree/master/graal-js/src/com.oracle.js.parser
but it's not compiled as an independent JAR available in Maven
Central. Could the GraalVM project do this?
The whole org.graalvm.js:js seems pretty big and has many
dependencies. We just need the parser.
--emi
http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more!
On Sat, Jan 12, 2019 at 9:05 AM Emilian Bold <em...@gmail.com> wrote:
>
> Wow, it's an issue I reported myself :-)
>
> --emi
>
> http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more!
>
> On Sat, Jan 12, 2019 at 9:00 AM Jaroslav Tulach
> <ja...@gmail.com> wrote:
> >
> > Dne pátek 11. ledna 2019 22:14:41 CET, Emilian Bold napsal(a):
> >
> > > This means that we could actually include it in Apache NetBeans,
> >
> > > correct? No need for the run-time plugin.
> >
> >
> >
> > Newer version of lib.nashorn parser is available as org.graalvm.js in Maven repository. It is licensed under friendly UPL license. It is "just" necessary to modify the code to use the new version.
> >
> >
> >
> > I've put that not to https://issues.apache.org/jira/browse/NETBEANS-2
> >
> >
> >
> > We have just one problem: find somebody who does the work...
> >
> > -jt
> >
> >
> >
> >
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Use Graal.js parser for NetBeans 11 was: Where is `Oracle JS
Parser Implementation` built from?
Posted by Emilian Bold <em...@gmail.com>.
Wow, it's an issue I reported myself :-)
--emi
http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more!
On Sat, Jan 12, 2019 at 9:00 AM Jaroslav Tulach
<ja...@gmail.com> wrote:
>
> Dne pátek 11. ledna 2019 22:14:41 CET, Emilian Bold napsal(a):
>
> > This means that we could actually include it in Apache NetBeans,
>
> > correct? No need for the run-time plugin.
>
>
>
> Newer version of lib.nashorn parser is available as org.graalvm.js in Maven repository. It is licensed under friendly UPL license. It is "just" necessary to modify the code to use the new version.
>
>
>
> I've put that not to https://issues.apache.org/jira/browse/NETBEANS-2
>
>
>
> We have just one problem: find somebody who does the work...
>
> -jt
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Use Graal.js parser for NetBeans 11 was: Where is `Oracle JS Parser Implementation` built from?
Posted by Jaroslav Tulach <ja...@gmail.com>.
Dne pátek 11. ledna 2019 22:14:41 CET, Emilian Bold napsal(a):
> This means that we could actually include it in Apache NetBeans,
> correct? No need for the run-time plugin.
Newer version of lib.nashorn parser is available as org.graalvm.js[1] in Maven repository.
It is licensed under friendly UPL license. It is "just" necessary to modify the code to use
the new version.
I've put that not to https://issues.apache.org/jira/browse/NETBEANS-2
We have just one problem: find somebody who does the work...
-jt
--------
[1] https://search.maven.org/search?q=g:org.graalvm.js
Re: Where is `Oracle JS Parser Implementation` built from?
Posted by Emilian Bold <em...@gmail.com>.
I imagine is not part of the Apache repository, I was just wondering
where was it referenced from in the Oracle repository.
OK, so I do remember correctly about a relicensing.
This means that we could actually include it in Apache NetBeans,
correct? No need for the run-time plugin.
--emi
http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more!
On Fri, Jan 11, 2019 at 10:44 PM Matthias Bläsing
<mb...@doppel-helix.eu> wrote:
>
> Hi Emilian,
>
> Am Freitag, den 11.01.2019, 22:35 +0200 schrieb Emilian Bold:
> > We suggest the plugin in NetBeans, but I don't know where the source
> > for it is.
> >
> > The plugin we point to is
> > http://plugins.netbeans.org/plugin/74901/oracle-js-parser-implementation
> >
> > I suspect it used to be part of the repository, so where is it? (I
> > also remember a discussion about relicensing some JS parser as
> > Apache,
> > I gather that went nowhere. Sorry if a bit fuzzy.)
>
> nope it is not part of the repository. If I remember correctly the
> change JS parser was redistributed by the javascript modules and was
> extracted because it was licenses GPLv2-CP.
>
> The graaljs parser can be found here:
>
> https://github.com/graalvm/graaljs
>
> The work, that externalized the parser should be rereviewed, as the
> license for the parser was changed to UPL.
>
> HTH
>
> Matthias
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Where is `Oracle JS Parser Implementation` built from?
Posted by Matthias Bläsing <mb...@doppel-helix.eu>.
Hi Emilian,
Am Freitag, den 11.01.2019, 22:35 +0200 schrieb Emilian Bold:
> We suggest the plugin in NetBeans, but I don't know where the source
> for it is.
>
> The plugin we point to is
> http://plugins.netbeans.org/plugin/74901/oracle-js-parser-implementation
>
> I suspect it used to be part of the repository, so where is it? (I
> also remember a discussion about relicensing some JS parser as
> Apache,
> I gather that went nowhere. Sorry if a bit fuzzy.)
nope it is not part of the repository. If I remember correctly the
change JS parser was redistributed by the javascript modules and was
extracted because it was licenses GPLv2-CP.
The graaljs parser can be found here:
https://github.com/graalvm/graaljs
The work, that externalized the parser should be rereviewed, as the
license for the parser was changed to UPL.
HTH
Matthias
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@netbeans.incubator.apache.org
For additional commands, e-mail: dev-help@netbeans.incubator.apache.org
For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists