Re: [VOTE] Apache NetBeans Version Number: 11.0
+1(non binding) Enrico Il giorno sab 26 gen 2019, 08:19 Tomas Poledny ha scritto: > +1 > > On Sat, Jan 26, 2019, 05:54 Vano Beridze > > +1 > > > > On Sat, Jan 26, 2019, 7:51 AM Laszlo Kishalmi > wrote: > > > > > Dear all, > > > > > > Well, it is time to finalize out version scheme for a while. There will > > > be three voting threads created on this topic with subjects: > > > > > > * [VOTE] Apache NetBeans Version Number: 11 > > > * [VOTE] Apache NetBeans Version Number: 11.0 > > > * [VOTE] Apache NetBeans Version Number: 2019.03 > > > > > > Everyone from the community can cast his/her own vote on each thread > as: > > > > > > +1 I like it, let's do this way > > > 0I'm Ok with it, does not particularly like it, but won't mind it > > > -1 I do not like it at all. > > > > > > Each thread is going to be open for 72+ hours and going to be closed at > > > the same time. Regardless from the number of votes, that version number > > > would win which has the greatest sum of the vote values. > > > > > > Voting is a community event! Be a proud community member and cast your > > > vote! > > > > > > Thank you! > > > > > > Laszlo Kishalmi > > > > > > Volunteer Release Manager of Apache NetBeans 11.0 > > > > > > P.S.: Please keep this thread for voting only! > > > > > > > > >
Re: [VOTE] Apache NetBeans Version Number: 11
0 On Sat, Jan 26, 2019, 04:52 Laszlo Kishalmi 0 > > On 1/25/19 7:50 PM, Laszlo Kishalmi wrote: > > > > Dear all, > > > > Well, it is time to finalize out version scheme for a while. There > > will be three voting threads created on this topic with subjects: > > > > * [VOTE] Apache NetBeans Version Number: 11 > > * [VOTE] Apache NetBeans Version Number: 11.0 > > * [VOTE] Apache NetBeans Version Number: 2019.03 > > > > Everyone from the community can cast his/her own vote on each thread as: > > > > +1 I like it, let's do this way > > 0I'm Ok with it, does not particularly like it, but won't mind it > > -1 I do not like it at all. > > > > Each thread is going to be open for 72+ hours and going to be closed > > at the same time. Regardless from the number of votes, that version > > number would win which has the greatest sum of the vote values. > > > > Voting is a community event! Be a proud community member and cast your > > vote! > > > > Thank you! > > > > Laszlo Kishalmi > > > > Volunteer Release Manager of Apache NetBeans 11 > > > > P.S.: Please keep this thread for voting only! > > >
Re: [VOTE] Apache NetBeans Version Number: 11
0 Am Sa., 26. Jan. 2019, 04:52 hat Laszlo Kishalmi geschrieben: > 0 > > On 1/25/19 7:50 PM, Laszlo Kishalmi wrote: > > > > Dear all, > > > > Well, it is time to finalize out version scheme for a while. There > > will be three voting threads created on this topic with subjects: > > > > * [VOTE] Apache NetBeans Version Number: 11 > > * [VOTE] Apache NetBeans Version Number: 11.0 > > * [VOTE] Apache NetBeans Version Number: 2019.03 > > > > Everyone from the community can cast his/her own vote on each thread as: > > > > +1 I like it, let's do this way > > 0I'm Ok with it, does not particularly like it, but won't mind it > > -1 I do not like it at all. > > > > Each thread is going to be open for 72+ hours and going to be closed > > at the same time. Regardless from the number of votes, that version > > number would win which has the greatest sum of the vote values. > > > > Voting is a community event! Be a proud community member and cast your > > vote! > > > > Thank you! > > > > Laszlo Kishalmi > > > > Volunteer Release Manager of Apache NetBeans 11 > > > > P.S.: Please keep this thread for voting only! > > >
Re: [VOTE] Apache NetBeans Version Number: 11.0
+1 Am Sa., 26. Jan. 2019, 08:19 hat Tomas Poledny geschrieben: > +1 > > On Sat, Jan 26, 2019, 05:54 Vano Beridze > > +1 > > > > On Sat, Jan 26, 2019, 7:51 AM Laszlo Kishalmi > wrote: > > > > > Dear all, > > > > > > Well, it is time to finalize out version scheme for a while. There will > > > be three voting threads created on this topic with subjects: > > > > > > * [VOTE] Apache NetBeans Version Number: 11 > > > * [VOTE] Apache NetBeans Version Number: 11.0 > > > * [VOTE] Apache NetBeans Version Number: 2019.03 > > > > > > Everyone from the community can cast his/her own vote on each thread > as: > > > > > > +1 I like it, let's do this way > > > 0I'm Ok with it, does not particularly like it, but won't mind it > > > -1 I do not like it at all. > > > > > > Each thread is going to be open for 72+ hours and going to be closed at > > > the same time. Regardless from the number of votes, that version number > > > would win which has the greatest sum of the vote values. > > > > > > Voting is a community event! Be a proud community member and cast your > > > vote! > > > > > > Thank you! > > > > > > Laszlo Kishalmi > > > > > > Volunteer Release Manager of Apache NetBeans 11.0 > > > > > > P.S.: Please keep this thread for voting only! > > > > > > > > >
Re: [VOTE] Apache NetBeans Version Number: 2019.03
-1 Am Sa., 26. Jan. 2019, 08:20 hat Tomas Poledny geschrieben: > -1 > > On Sat, Jan 26, 2019, 04:51 Laszlo Kishalmi wrote: > > > +1 > > > > On 1/25/19 7:51 PM, Laszlo Kishalmi wrote: > > > > > > Dear all, > > > > > > Well, it is time to finalize out version scheme for a while. There > > > will be three voting threads created on this topic with subjects: > > > > > > * [VOTE] Apache NetBeans Version Number: 11 > > > * [VOTE] Apache NetBeans Version Number: 11.0 > > > * [VOTE] Apache NetBeans Version Number: 2019.03 > > > > > > Everyone from the community can cast his/her own vote on each thread > as: > > > > > > +1 I like it, let's do this way > > > 0I'm Ok with it, does not particularly like it, but won't mind it > > > -1 I do not like it at all. > > > > > > Each thread is going to be open for 72+ hours and going to be closed > > > at the same time. Regardless from the number of votes, that version > > > number would win which has the greatest sum of the vote values. > > > > > > Voting is a community event! Be a proud community member and cast > > > your vote! > > > > > > Thank you! > > > > > > Laszlo Kishalmi > > > > > > Volunteer Release Manager of Apache NetBeans 2019.03 > > > > > > P.S.: Please keep this thread for voting only! > > > > > >
Re: [VOTE] Apache NetBeans Version Number: 2019.03
-1 On Sat, Jan 26, 2019, 04:51 Laszlo Kishalmi +1 > > On 1/25/19 7:51 PM, Laszlo Kishalmi wrote: > > > > Dear all, > > > > Well, it is time to finalize out version scheme for a while. There > > will be three voting threads created on this topic with subjects: > > > > * [VOTE] Apache NetBeans Version Number: 11 > > * [VOTE] Apache NetBeans Version Number: 11.0 > > * [VOTE] Apache NetBeans Version Number: 2019.03 > > > > Everyone from the community can cast his/her own vote on each thread as: > > > > +1 I like it, let's do this way > > 0I'm Ok with it, does not particularly like it, but won't mind it > > -1 I do not like it at all. > > > > Each thread is going to be open for 72+ hours and going to be closed > > at the same time. Regardless from the number of votes, that version > > number would win which has the greatest sum of the vote values. > > > > Voting is a community event! Be a proud community member and cast > > your vote! > > > > Thank you! > > > > Laszlo Kishalmi > > > > Volunteer Release Manager of Apache NetBeans 2019.03 > > > > P.S.: Please keep this thread for voting only! > > >
Re: [VOTE] Apache NetBeans Version Number: 11.0
+1 On Sat, Jan 26, 2019, 05:54 Vano Beridze +1 > > On Sat, Jan 26, 2019, 7:51 AM Laszlo Kishalmi wrote: > > > Dear all, > > > > Well, it is time to finalize out version scheme for a while. There will > > be three voting threads created on this topic with subjects: > > > > * [VOTE] Apache NetBeans Version Number: 11 > > * [VOTE] Apache NetBeans Version Number: 11.0 > > * [VOTE] Apache NetBeans Version Number: 2019.03 > > > > Everyone from the community can cast his/her own vote on each thread as: > > > > +1 I like it, let's do this way > > 0I'm Ok with it, does not particularly like it, but won't mind it > > -1 I do not like it at all. > > > > Each thread is going to be open for 72+ hours and going to be closed at > > the same time. Regardless from the number of votes, that version number > > would win which has the greatest sum of the vote values. > > > > Voting is a community event! Be a proud community member and cast your > > vote! > > > > Thank you! > > > > Laszlo Kishalmi > > > > Volunteer Release Manager of Apache NetBeans 11.0 > > > > P.S.: Please keep this thread for voting only! > > > > >
Re: [VOTE] Apache NetBeans Version Number: 11.0
+1 On Sat, Jan 26, 2019, 7:51 AM Laszlo Kishalmi Dear all, > > Well, it is time to finalize out version scheme for a while. There will > be three voting threads created on this topic with subjects: > > * [VOTE] Apache NetBeans Version Number: 11 > * [VOTE] Apache NetBeans Version Number: 11.0 > * [VOTE] Apache NetBeans Version Number: 2019.03 > > Everyone from the community can cast his/her own vote on each thread as: > > +1 I like it, let's do this way > 0I'm Ok with it, does not particularly like it, but won't mind it > -1 I do not like it at all. > > Each thread is going to be open for 72+ hours and going to be closed at > the same time. Regardless from the number of votes, that version number > would win which has the greatest sum of the vote values. > > Voting is a community event! Be a proud community member and cast your > vote! > > Thank you! > > Laszlo Kishalmi > > Volunteer Release Manager of Apache NetBeans 11.0 > > P.S.: Please keep this thread for voting only! > >
Re: [VOTE] Apache NetBeans Version Number: 11
0 On 1/25/19 7:50 PM, Laszlo Kishalmi wrote: Dear all, Well, it is time to finalize out version scheme for a while. There will be three voting threads created on this topic with subjects: * [VOTE] Apache NetBeans Version Number: 11 * [VOTE] Apache NetBeans Version Number: 11.0 * [VOTE] Apache NetBeans Version Number: 2019.03 Everyone from the community can cast his/her own vote on each thread as: +1 I like it, let's do this way 0 I'm Ok with it, does not particularly like it, but won't mind it -1 I do not like it at all. Each thread is going to be open for 72+ hours and going to be closed at the same time. Regardless from the number of votes, that version number would win which has the greatest sum of the vote values. Voting is a community event! Be a proud community member and cast your vote! Thank you! Laszlo Kishalmi Volunteer Release Manager of Apache NetBeans 11 P.S.: Please keep this thread for voting only!
Re: [VOTE] Apache NetBeans Version Number: 11.0
+1 On 1/25/19 7:51 PM, Laszlo Kishalmi wrote: Dear all, Well, it is time to finalize out version scheme for a while. There will be three voting threads created on this topic with subjects: * [VOTE] Apache NetBeans Version Number: 11 * [VOTE] Apache NetBeans Version Number: 11.0 * [VOTE] Apache NetBeans Version Number: 2019.03 Everyone from the community can cast his/her own vote on each thread as: +1 I like it, let's do this way 0 I'm Ok with it, does not particularly like it, but won't mind it -1 I do not like it at all. Each thread is going to be open for 72+ hours and going to be closed at the same time. Regardless from the number of votes, that version number would win which has the greatest sum of the vote values. Voting is a community event! Be a proud community member and cast your vote! Thank you! Laszlo Kishalmi Volunteer Release Manager of Apache NetBeans 11.0 P.S.: Please keep this thread for voting only!
Re: [VOTE] Apache NetBeans Version Number: 2019.03
+1 On 1/25/19 7:51 PM, Laszlo Kishalmi wrote: Dear all, Well, it is time to finalize out version scheme for a while. There will be three voting threads created on this topic with subjects: * [VOTE] Apache NetBeans Version Number: 11 * [VOTE] Apache NetBeans Version Number: 11.0 * [VOTE] Apache NetBeans Version Number: 2019.03 Everyone from the community can cast his/her own vote on each thread as: +1 I like it, let's do this way 0 I'm Ok with it, does not particularly like it, but won't mind it -1 I do not like it at all. Each thread is going to be open for 72+ hours and going to be closed at the same time. Regardless from the number of votes, that version number would win which has the greatest sum of the vote values. Voting is a community event! Be a proud community member and cast your vote! Thank you! Laszlo Kishalmi Volunteer Release Manager of Apache NetBeans 2019.03 P.S.: Please keep this thread for voting only!
[VOTE] Apache NetBeans Version Number: 2019.03
Dear all, Well, it is time to finalize out version scheme for a while. There will be three voting threads created on this topic with subjects: * [VOTE] Apache NetBeans Version Number: 11 * [VOTE] Apache NetBeans Version Number: 11.0 * [VOTE] Apache NetBeans Version Number: 2019.03 Everyone from the community can cast his/her own vote on each thread as: +1 I like it, let's do this way 0 I'm Ok with it, does not particularly like it, but won't mind it -1 I do not like it at all. Each thread is going to be open for 72+ hours and going to be closed at the same time. Regardless from the number of votes, that version number would win which has the greatest sum of the vote values. Voting is a community event! Be a proud community member and cast your vote! Thank you! Laszlo Kishalmi Volunteer Release Manager of Apache NetBeans 2019.03 P.S.: Please keep this thread for voting only!
[VOTE] Apache NetBeans Version Number: 11.0
Dear all, Well, it is time to finalize out version scheme for a while. There will be three voting threads created on this topic with subjects: * [VOTE] Apache NetBeans Version Number: 11 * [VOTE] Apache NetBeans Version Number: 11.0 * [VOTE] Apache NetBeans Version Number: 2019.03 Everyone from the community can cast his/her own vote on each thread as: +1 I like it, let's do this way 0 I'm Ok with it, does not particularly like it, but won't mind it -1 I do not like it at all. Each thread is going to be open for 72+ hours and going to be closed at the same time. Regardless from the number of votes, that version number would win which has the greatest sum of the vote values. Voting is a community event! Be a proud community member and cast your vote! Thank you! Laszlo Kishalmi Volunteer Release Manager of Apache NetBeans 11.0 P.S.: Please keep this thread for voting only!
[VOTE] Apache NetBeans Version Number: 11
Dear all, Well, it is time to finalize out version scheme for a while. There will be three voting threads created on this topic with subjects: * [VOTE] Apache NetBeans Version Number: 11 * [VOTE] Apache NetBeans Version Number: 11.0 * [VOTE] Apache NetBeans Version Number: 2019.03 Everyone from the community can cast his/her own vote on each thread as: +1 I like it, let's do this way 0 I'm Ok with it, does not particularly like it, but won't mind it -1 I do not like it at all. Each thread is going to be open for 72+ hours and going to be closed at the same time. Regardless from the number of votes, that version number would win which has the greatest sum of the vote values. Voting is a community event! Be a proud community member and cast your vote! Thank you! Laszlo Kishalmi Volunteer Release Manager of Apache NetBeans 11 P.S.: Please keep this thread for voting only!
Re: Apache NetBeans 11 or 11.0 ?
Well, all I am wishing for is clarity and consistency. Though as humans, naming a baby creates a real active discussion, however the most important thing is that it should be healthy. There were a few attempts on this list to bring up the topic every attempt died with time without actually having this issue resolved. I do understand everyone's opinion, but after all, we need to settle this one and focus on other tasks, and while I can read through every email on this topic here, I see that either we act like a community and vote or just let somebody to make a decision for us. See: https://www.apache.org/foundation/voting.html#reasons-for-votes So the top tree option usually are: 1. Keep it simple one number: 11 2. Keep the tradition, have a minor version: 11.0 3. Use calendar versioning: 2019.03 Using codenames, like moons or chemical elements, or using codenames at all is another topic. Let's not deal with that now. Well Apache does not say anything about multi-option votes, though I think we can handle 3 threads. On 1/24/19 11:35 AM, Emilian Bold wrote: Seems so odd to have multiple voting threads because Apache rules can't allow multiple options voting... I also want to include calendar versioning aka 'NetBeans 2019.03' on the voting list. So that makes 3 voting threads? --emi http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more! On Thu, Jan 24, 2019 at 7:53 PM Laszlo Kishalmi wrote: Well, all I'm seeking is the consensus here. I have pro-s for both of them. What about, if I start two voting threads on each version and whichever got the most +1 in three days will win? (I know it is a kind of pity, but sometimes small things matter.) On 1/23/19 10:41 PM, Laszlo Kishalmi wrote: Well, probably it is the right time to decide: 11 or 11.0 ? - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@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
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.wiele...@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.wiele...@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.wiele...@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 >>> 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.tul...@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'
Re: [NBI Launcher] nbi/nlw.exe broken for OpenJDK 11
Hi All, I have been having great difficulty in getting a Platform installer to work with a bundled JDK 11... After much hard work, I eventually had great success with JDK 8 JREs (Using both Open JDK and Zulu), starting off by following the instructions from https://dzone.com/articles/including-jre-in-nbi Now trying to migrate to JDK 11, I am using jlink to create a JRE and bundle this in the same way. Works on Linux, but no matter what I try, the installer always objects on Windows, saying that there is no Java available, which is maddening because it just extracted the JVM and executed it with it's test-java-class (I think...). I would like to examine the tmp directory that the installer creates, but it deletes that and I cannot find a switch to disable that behaviour. I can't understand how the NBI installers are actually created - the relationship between the C code, exe launchers, shell scripts, nbi.engine, harness/libs.nbi.engine is unclear to me and the NBI Developer page doesn't explain the details. http://wiki.netbeans.org/NBI My feeling is that there is work to be done for updating the NBI system and I would be happy to help - but I don't know how to build it surgically. Has anyone out there had real success with a bundled JDK11 installer on Windows yet? Some of the scripting to create the JVM and output of my installer is here: https://gist.github.com/phipma/a513d4f8e7a6a93811ffde09fbedf6ce Thanks Mark On 05/01/2019 19:55, Michael Huang wrote: Hi, Thanks for the update. Yes, I think that may be the case (it was not recompiled). I didn't find nlw.exe from the Netbeans10 source and now I remember that I populated that from Netbeans 9.0 including the problematic source. It's good that it's now fixed. I will try to find recompiled nlw.exe as I'm having trouble recompiling a working one using VisualStudio 2017 (the project was using Visual Studio 2005). Regards, MH --- SPISim: [www.spisim.com] EDA in Signal, Power Integrity and SIMulation --- On Sat, Jan 5, 2019 at 11:43 AM Emilian Bold wrote: Maybe we are looking at different versions of JavaUtils.c but to me it looks like it has a small parser and it expressly supports major versions with more digits: https://github.com/apache/incubator-netbeans/blob/master/nbi/engine/native/launcher/windows/src/JavaUtils.c#L138 This has been fixed since Aug 21st by Andreas Hauffe in NETBEANS-1157, see https://github.com/apache/incubator-netbeans/commit/57cb8c469fb6024de3a3b9702fa468302acb4039#diff-f0f864825c4c1d5461c1a84cc9aa9e00 So you are saying the exe file from NetBeans 10 is not good? Maybe we never recompiled it? --emi http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more! On Sat, Jan 5, 2019 at 9:26 PM Michael Huang wrote: Hi, I think there is a bug in nbi's JavaUtils.c, line 125 (Function getJavaVersionFromString), when it's used to unpack JVM of version 10 or above such as OpenJDK11. This will affect netbeans launcher on windows (nlw.exe) and thus need to have it rebuild after code fix. The current codes' assumption is that Java version (java -version) show MAJOR.MINOR and the MAJOR only has one digit (e.g. 1.8, 1.7 etc). Codes use string[1] to check "." first. For OpenJDK11, the java -version will show 11.X... and thus the dot "." will not appear at the string[1]. As a result, result code of "ERROR_OK" will not be assigned and JVM unpacking will fail. I have never committed codes to netbeans myself and thus will leave this for someone more familiar with the code committing process to review first and then commit if necessary. Hope this will help those whom may need NetBeans launcher to unpack JVM during installation process on windows. Thanks and regards, MH --- SPISim: [www.spisim.com] EDA in Signal, Power Integrity and SIMulation --- - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists www.sucdenfinancial.com Sucden Financial Limited, Plantation Place South, 60 Great Tower Street, London EC3R 5AZ Telephone +44 203 207 5000 Registered in England no. 1095841 VAT registration no. GB 446 9061 33 Authorised and Regulated by the Financial Conduct Authority (FCA) and entered in the FCA register under no. 114239 This email, including any files transmitted with it, is confidential and may be privileged. It may be read, copied and used only by the intended recipient. If you are not the intended recipient of this message, please notify postmas...@sucfin.com immediately and dele
Re: Cannot compile NetBeans because of Gradle
https://github.com/apache/incubator-netbeans/pull/1102 On 1/25/19 5:26 AM, Jaroslav Tulach wrote: I on Linux, behind a corporate proxy. I could get though it with nbbuild.*DownloadBinaries, but since the integration of Gradle I cannot build NetBeans anymore. Can this be fixed? -jt -copy-gradle-wrapper: -uptodate-tooling: build-tooling-lib: [java] Downloading https://services.gradle.org/distributions/gradle-4.10.2-bin.zip [java] [java] Exception in thread "main" java.net.ConnectException: Connection timed out (Connection timed out) [java] at java.net.PlainSocketImpl.socketConnect(Native Method) [java] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) [java] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) [java] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) [java] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) [java] at java.net.Socket.connect(Socket.java:589) [java] at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:673) [java] at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:173) [java] at sun.net.NetworkClient.doConnect(NetworkClient.java:180) [java] at sun.net.www.http.HttpClient.openServer(HttpClient.java:463) [java] at sun.net.www.http.HttpClient.openServer(HttpClient.java:558) [java] at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:264) [java] at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367) [java] at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) [java] at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156) [java] at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050) [java] at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177) [java] at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564) [java] at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492) [java] at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263) [java] at org.gradle.wrapper.Download.downloadInternal(Download.java:67) [java] at org.gradle.wrapper.Download.download(Download.java:52) [java] at org.gradle.wrapper.Install$1.call(Install.java:62) [java] at org.gradle.wrapper.Install$1.call(Install.java:48) [java] at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:69) [java] at org.gradle.wrapper.Install.createDist(Install.java:48) [java] at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:107) [java] at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:62) [nbmerge] Failed to build target: all-gradle BUILD FAILED - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
RE: Apache NetBeans 11 or 11.0 ?
Just to know, the format Y.0M is a standard to do this kind of versioning ? Maybe for maven we can have also do the release as 2019.03-RELEASE (and for the old one 2018.09-RELEASE for (9.0),2018.12-RELEASE for (10)) so it may help know if there is a new version from a maven point of view. We are not bind to RELEASE... version I guess. Anyway I will follow the decision. Eric -Message d'origine- De : Emilian Bold Envoyé : vendredi 25 janvier 2019 11:01 À : NetBeans Dev@ Objet : Re: Apache NetBeans 11 or 11.0 ? > Or should we change the apidocs, the maven artefacts ? Normally module versions are unrelated to the NetBeans version. So a NetBeans Platform app doesn't update versions the same way a Maven-based NetBeans Platform app (where for convenience we have only major versions like RELEASE82, whatever). So it's actually the Maven support that's the odd one. I don't see a problem with using RELEASE201903. > What if a release has to be released in a short period because of security > fixes? Append calendar with day, use another moon or new element? I believe Ubuntu just adds another number for patches. So 2018.10.1, 2018.10.2 -- thus the end number is not a day but the patch level. calver.org calls this 'micro' or 'patch' segment. > Is this only for branding? Primordially yes. The version number is something end users see and remember. The actual module versions are for programmers and we don't change them all when we do another release (except for Maven I guess?). --emi http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more! On Fri, Jan 25, 2019 at 11:37 AM Eric Barboni wrote: > > Hi, > > Is this only for branding? > Or should we change the apidocs, the maven artefacts ? > What if a release has to be released in a short period because of security > fixes? Append calendar with day, use another moon or new element? > > Regards > Eric > -Message d'origine- > De : Tomas Poledny Envoyé : vendredi 25 janvier > 2019 10:12 À : dev@netbeans.incubator.apache.org Objet : Re: Apache > NetBeans 11 or 11.0 ? > > Hi, > I don't like calendar versioning. I have problem with remember it. It > is more easy to remember 11 or 11.0 than 2019.03. What will be next > version > 2019.02 or 2019.03 or 2019.04 and what was previous version? > > So +1 for 11.0 > Tomas > > > On Fri, Jan 25, 2019 at 10:09 AM Daniel Gruno wrote: > > > On 1/25/19 9:48 AM, Geertjan Wielenga wrote: > > > Are you saying you're against Emilian's proposal, i.e., 2019.03, > > > calendar versioning? > > > > I'm not against it at all :) > > My only suggestion or opinion would be that it should be something > > where users can quickly see whether version A is newer or older than > > version B. Both numerical and calendar versioning solve that. Using > > nicknames would complicate matters, even if just slightly. > > > > > > > > No, we're not going to start any vote at all, until we've seen > > > whether we can reach consensus. Emilian's proposal is completely > > > new. I like it, a lot. Let's see what others say first and then if > > > we cannot reach > > consensus, > > > we'll do a vote. But I have a feeling we're able to reach > > > consensus > > around > > > calendar versioning. > > > > > > Gj > > > > > > > > > On Fri, Jan 25, 2019 at 9:32 AM Daniel Gruno > > > > > wrote: > > > > > >> On 1/25/19 9:30 AM, Geertjan Wielenga wrote: > > >>> I think whatever is super simple and clear is what we should do > > >>> and therefore I really like Emilian's suggestion. > > >> > > >> I think (hope?!) some of these suggestions were in jest. > > >> Let's keep it simple - version numbers are free, 1,2,3,4,5,6I > > >> could continue for quite a while before I run out :) > > >> > > >>> > > >>> We spend more time and energy discussing release numbering than > > anything > > >>> else and the sooner that can stop the better. :-) > > >>> > > >>> Gj > > >>> > > >>> On Fri, Jan 25, 2019 at 9:28 AM Christian Lenz > > >>> > > > > >>> wrote: > > >>> > > And for the codenames, I mean 2019.03 could have also a moon > > chemical thing like Natrium or whatever. For me it is more to > > say and, instead > > >> of or. > > > > > > Cheers > > > > Chris > > > > > > > > Von: Kenneth Fogel > > Gesendet: Donnerstag, 24. Januar 2019 20:44 > > An: dev@netbeans.incubator.apache.org > > Betreff: RE: Apache NetBeans 11 or 11.0 ? > > > > We could use seemingly random words like Eclipse does so that > > no one > > >> knows > > what the most recent version is. For example, we could use the > > names > > of > > >> the > > 63 moons of Jupiter, the planet with the most moons. Also, > > select them randomly, users will catch on if we do it alphabetically. > > Here are the > > >> 51 > > named moons: > > > > AdrasteaErinome Isonoe Sponde > > Aitne Euanthe Ka
Re: Help, JavaScript fans! was: Use Graal.js (parser) for NetBeans 11
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.wiele...@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.wiele...@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 >> 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.tul...@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-unsubscr...@netbeans.incubator.apache.org >>> > For additional commands, e-mail: >>> dev-h...@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
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.wiele...@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 > 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.tul...@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-unsubscr...@netbeans.incubator.apache.org >> > For additional commands, e-mail: dev-h...@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
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 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.tul...@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-unsubscr...@netbeans.incubator.apache.org > > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > > > For further information about the NetBeans mailing lists, visit: > > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > > > > > > > >
Re: Cannot compile NetBeans because of Gradle
That could be added to netbeans.osuosl.org. Not sure why are we downloading from another server... Do we keep the hash for that dependency? --emi On Fri, 25 Jan 2019 at 15:26, Jaroslav Tulach wrote: > I on Linux, behind a corporate proxy. I could get though it with > nbbuild.*DownloadBinaries, but since the integration of Gradle I cannot > build NetBeans anymore. Can this be fixed? > -jt > > > -copy-gradle-wrapper: > > -uptodate-tooling: > > build-tooling-lib: > [java] Downloading > https://services.gradle.org/distributions/gradle-4.10.2-bin.zip > [java] > [java] Exception in thread "main" java.net.ConnectException: > Connection timed out (Connection timed out) > [java] at java.net.PlainSocketImpl.socketConnect(Native Method) > [java] at > java.net > .AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) > [java] at > java.net > .AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) > [java] at > java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) > [java] at > java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) > [java] at java.net.Socket.connect(Socket.java:589) > [java] at > sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:673) > [java] at > sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:173) > [java] at sun.net.NetworkClient.doConnect(NetworkClient.java:180) > [java] at > sun.net.www.http.HttpClient.openServer(HttpClient.java:463) > [java] at > sun.net.www.http.HttpClient.openServer(HttpClient.java:558) > [java] at > sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:264) > [java] at > sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367) > [java] at > > sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) > [java] at > > sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156) > [java] at > > sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050) > [java] at > > sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177) > [java] at > > sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564) > [java] at > > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492) > [java] at > > sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263) > [java] at > org.gradle.wrapper.Download.downloadInternal(Download.java:67) > [java] at org.gradle.wrapper.Download.download(Download.java:52) > [java] at org.gradle.wrapper.Install$1.call(Install.java:62) > [java] at org.gradle.wrapper.Install$1.call(Install.java:48) > [java] at > > org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:69) > [java] at org.gradle.wrapper.Install.createDist(Install.java:48) > [java] at > org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:107) > [java] at > org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:62) > [nbmerge] Failed to build target: all-gradle > > BUILD FAILED > -- --emi
AW: Help, JavaScript fans! was: Use Graal.js (parser) for NetBeans 11
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 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-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Cannot compile NetBeans because of Gradle
I on Linux, behind a corporate proxy. I could get though it with nbbuild.*DownloadBinaries, but since the integration of Gradle I cannot build NetBeans anymore. Can this be fixed? -jt -copy-gradle-wrapper: -uptodate-tooling: build-tooling-lib: [java] Downloading https://services.gradle.org/distributions/gradle-4.10.2-bin.zip [java] [java] Exception in thread "main" java.net.ConnectException: Connection timed out (Connection timed out) [java] at java.net.PlainSocketImpl.socketConnect(Native Method) [java] at java.net.AbstractPlainSocketImpl.doConnect(AbstractPlainSocketImpl.java:350) [java] at java.net.AbstractPlainSocketImpl.connectToAddress(AbstractPlainSocketImpl.java:206) [java] at java.net.AbstractPlainSocketImpl.connect(AbstractPlainSocketImpl.java:188) [java] at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:392) [java] at java.net.Socket.connect(Socket.java:589) [java] at sun.security.ssl.SSLSocketImpl.connect(SSLSocketImpl.java:673) [java] at sun.security.ssl.BaseSSLSocketImpl.connect(BaseSSLSocketImpl.java:173) [java] at sun.net.NetworkClient.doConnect(NetworkClient.java:180) [java] at sun.net.www.http.HttpClient.openServer(HttpClient.java:463) [java] at sun.net.www.http.HttpClient.openServer(HttpClient.java:558) [java] at sun.net.www.protocol.https.HttpsClient.(HttpsClient.java:264) [java] at sun.net.www.protocol.https.HttpsClient.New(HttpsClient.java:367) [java] at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.getNewHttpClient(AbstractDelegateHttpsURLConnection.java:191) [java] at sun.net.www.protocol.http.HttpURLConnection.plainConnect0(HttpURLConnection.java:1156) [java] at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConnection.java:1050) [java] at sun.net.www.protocol.https.AbstractDelegateHttpsURLConnection.connect(AbstractDelegateHttpsURLConnection.java:177) [java] at sun.net.www.protocol.http.HttpURLConnection.getInputStream0(HttpURLConnection.java:1564) [java] at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1492) [java] at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:263) [java] at org.gradle.wrapper.Download.downloadInternal(Download.java:67) [java] at org.gradle.wrapper.Download.download(Download.java:52) [java] at org.gradle.wrapper.Install$1.call(Install.java:62) [java] at org.gradle.wrapper.Install$1.call(Install.java:48) [java] at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:69) [java] at org.gradle.wrapper.Install.createDist(Install.java:48) [java] at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:107) [java] at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:62) [nbmerge] Failed to build target: all-gradle BUILD FAILED
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 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-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: Javadoc for 9 and 10
čt 24. 1. 2019 v 15:15 odesílatel Eric Barboni napsal:
> Javadoc for 9.0 and 10.0 are regenerated according to Jaroslav comments
>
Oh, that is nice a quick. Thanks.
There are still wrong case with the following api's belonging to stable but
> rendered as "under dev" or "friend"
> Base Utilities API ( javadoc )
>
The stability is decided based on tags present in the arch.xml
document. If there is:
then the whole API is treated as stable. Alas, when Utilities API was split
into two, this tag disappeared.
-jt
> Filesystems NetBeans Client ( javadoc )
> Java Source ( javadoc )
> UI Gestures Collector Infrastructure ( javadoc )
> UI Handler Library ( javadoc )
>
> What should we do there
>
> Regards
> Eric
> -Message d'origine-
> De : Eric Barboni
> Envoyé : jeudi 24 janvier 2019 09:27
> À : dev@netbeans.incubator.apache.org
> Objet : RE: Javadoc for 9 and 10
>
> Hi
> I will commit the changes to the respective branches.
> I thinks the https://bits.netbeans.org/8.2/javadoc/ was bad generated
> and I base my previous branding on that :/
>
> Regards
> Eric
> -Message d'origine-
> De : László Kishalmi Envoyé : jeudi 24
> janvier 2019 06:03 À : Apache NetBeans
> Objet : Re: Javadoc for 9 and 10
>
> Got that! Thanks!
>
> On Wed, Jan 23, 2019, 20:46 Jaroslav Tulach wrote:
>
> > Dne neděle 20. ledna 2019 16:49:45 CET, Geertjan Wielenga napsal(a):
> > > Fantastic work as always. :-)
> >
> > Thanks for the Javadocs at
> >
> > http://bits.netbeans.org/dev/javadoc/
> > https://bits.netbeans.org/9.0/javadoc/
> > https://bits.netbeans.org/10.0/javadoc/
> >
> > Btw. The Javadoc for releases should only contain stable modules.
> > There should be no "under development" warning and modules like
> > bootstrap, core, etc.
> > shouldn't be listed there. They were not listed in 8.0 and prior
> releases:
> >
> > http://bits.netbeans.org/8.0/javadoc/
> >
> > This can be done by modifying `nbbuild/build.properties` and removing
> > other than stable from
> >
> > config.javadoc.all=\
> > ${config.javadoc.stable},\
> > ${config.javadoc.devel},\
> > ${config.javadoc.friend},\
> > ${config.javadoc.deprecated}
> >
> > Probably something for the release coordianator to do after branching
> > next time.
> >
> > Thanks again for publishing the Javadocs.
> > -jt
> >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org
> > For additional commands, e-mail:
> > dev-h...@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-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.incubator.apache.org
> For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>
>
>
Re: [NETBEANS-965] & [NETBEANS-997]
I'm not 100% sure yet... still working through the downloader code. For each version of Glassfish supported, there is an enum in /enterprise/glassfish.common/src/org/netbeans/modules/glassfish/common/ServerDetails.java that contains among other things two URLS: 1) Link to the Glassfish .zip file hosted on download.java.net 2) Link to one of these .txt files hosted on serverplugins.netbeans.org E.g. for Glassfish 4.1.1: " http://download.java.net/glassfish/4.1.1/release/glassfish-4.1.1.zip?nbretriever=fallback";, // NOI18N "http://serverplugins.netbeans.org/glassfishv3/post71v4-1-1.txt"; // NOI18N The download.java.net links still seem to be valid, but the serverplugins.netbeans.org links aren't. It's still a bit of a hunch at the moment, and you are right, we need to figure out how those txt files were used, but given that the downloader no longer works in NB8.2 too, I'm thinking it could well be an external dependency that is broken? I'm hoping somebody more experienced than I has an idea what those txt files were for? P On Fri, Jan 25, 2019 at 10:54 AM Geertjan Wielenga wrote: > How are they needed? I doubt they have been needed or used for a while > since they come from Kenai which has not been around for some time. Thanks > for your great work. > > Gj > > On Friday, January 25, 2019, Pete Whelpton wrote: > > > Hi all :) > > > > Thought I might have a quick look into these (attempting to download > > Glassfish via NB results in "Not Found" error). > > > > I think one problem here is that for each supported version of Glassfish, > > there was a related text file on the old netbeans.org: > > > > * http://serverplugins.netbeans.org/glassfishv3/post701v3.txt > > * http://serverplugins.netbeans.org/glassfishv3/post701v3-0-1.txt > > * http://serverplugins.netbeans.org/glassfishv3/post701v3-1.txt > > * http://serverplugins.netbeans.org/glassfishv3/post701v3-1-1.txt > > * http://serverplugins.netbeans.org/glassfishv3/post71v3-1-2.txt > > * http://serverplugins.netbeans.org/glassfishv3/post71v3-1-2.txt > > * http://serverplugins.netbeans.org/glassfishv3/post71v4-0.txt > > * http://serverplugins.netbeans.org/glassfishv3/post71v4-0-1.txt > > * http://serverplugins.netbeans.org/glassfishv3/post71v4-1.txt > > * http://serverplugins.netbeans.org/glassfishv3/post71v4-1-1.txt > > * http://serverplugins.netbeans.org/glassfishv3/post71v5-0.txt > > > > Does anybody know: > > > > a) what these .txt files are? > > b) if they made it to a new home on netbeans.apache.org? > > > > > > P > > >
Re: [NETBEANS-965] & [NETBEANS-997]
How are they needed? I doubt they have been needed or used for a while since they come from Kenai which has not been around for some time. Thanks for your great work. Gj On Friday, January 25, 2019, Pete Whelpton wrote: > Hi all :) > > Thought I might have a quick look into these (attempting to download > Glassfish via NB results in "Not Found" error). > > I think one problem here is that for each supported version of Glassfish, > there was a related text file on the old netbeans.org: > > * http://serverplugins.netbeans.org/glassfishv3/post701v3.txt > * http://serverplugins.netbeans.org/glassfishv3/post701v3-0-1.txt > * http://serverplugins.netbeans.org/glassfishv3/post701v3-1.txt > * http://serverplugins.netbeans.org/glassfishv3/post701v3-1-1.txt > * http://serverplugins.netbeans.org/glassfishv3/post71v3-1-2.txt > * http://serverplugins.netbeans.org/glassfishv3/post71v3-1-2.txt > * http://serverplugins.netbeans.org/glassfishv3/post71v4-0.txt > * http://serverplugins.netbeans.org/glassfishv3/post71v4-0-1.txt > * http://serverplugins.netbeans.org/glassfishv3/post71v4-1.txt > * http://serverplugins.netbeans.org/glassfishv3/post71v4-1-1.txt > * http://serverplugins.netbeans.org/glassfishv3/post71v5-0.txt > > Does anybody know: > > a) what these .txt files are? > b) if they made it to a new home on netbeans.apache.org? > > > P >
Re: Apache NetBeans 11 or 11.0 ?
> Or should we change the apidocs, the maven artefacts ? Normally module versions are unrelated to the NetBeans version. So a NetBeans Platform app doesn't update versions the same way a Maven-based NetBeans Platform app (where for convenience we have only major versions like RELEASE82, whatever). So it's actually the Maven support that's the odd one. I don't see a problem with using RELEASE201903. > What if a release has to be released in a short period because of security > fixes? Append calendar with day, use another moon or new element? I believe Ubuntu just adds another number for patches. So 2018.10.1, 2018.10.2 -- thus the end number is not a day but the patch level. calver.org calls this 'micro' or 'patch' segment. > Is this only for branding? Primordially yes. The version number is something end users see and remember. The actual module versions are for programmers and we don't change them all when we do another release (except for Maven I guess?). --emi http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more! On Fri, Jan 25, 2019 at 11:37 AM Eric Barboni wrote: > > Hi, > > Is this only for branding? > Or should we change the apidocs, the maven artefacts ? > What if a release has to be released in a short period because of security > fixes? Append calendar with day, use another moon or new element? > > Regards > Eric > -Message d'origine- > De : Tomas Poledny > Envoyé : vendredi 25 janvier 2019 10:12 > À : dev@netbeans.incubator.apache.org > Objet : Re: Apache NetBeans 11 or 11.0 ? > > Hi, > I don't like calendar versioning. I have problem with remember it. It is more > easy to remember 11 or 11.0 than 2019.03. What will be next version > 2019.02 or 2019.03 or 2019.04 and what was previous version? > > So +1 for 11.0 > Tomas > > > On Fri, Jan 25, 2019 at 10:09 AM Daniel Gruno wrote: > > > On 1/25/19 9:48 AM, Geertjan Wielenga wrote: > > > Are you saying you're against Emilian's proposal, i.e., 2019.03, > > > calendar versioning? > > > > I'm not against it at all :) > > My only suggestion or opinion would be that it should be something > > where users can quickly see whether version A is newer or older than > > version B. Both numerical and calendar versioning solve that. Using > > nicknames would complicate matters, even if just slightly. > > > > > > > > No, we're not going to start any vote at all, until we've seen > > > whether we can reach consensus. Emilian's proposal is completely > > > new. I like it, a lot. Let's see what others say first and then if > > > we cannot reach > > consensus, > > > we'll do a vote. But I have a feeling we're able to reach consensus > > around > > > calendar versioning. > > > > > > Gj > > > > > > > > > On Fri, Jan 25, 2019 at 9:32 AM Daniel Gruno > > wrote: > > > > > >> On 1/25/19 9:30 AM, Geertjan Wielenga wrote: > > >>> I think whatever is super simple and clear is what we should do > > >>> and therefore I really like Emilian's suggestion. > > >> > > >> I think (hope?!) some of these suggestions were in jest. > > >> Let's keep it simple - version numbers are free, 1,2,3,4,5,6I > > >> could continue for quite a while before I run out :) > > >> > > >>> > > >>> We spend more time and energy discussing release numbering than > > anything > > >>> else and the sooner that can stop the better. :-) > > >>> > > >>> Gj > > >>> > > >>> On Fri, Jan 25, 2019 at 9:28 AM Christian Lenz > > >>> > > > > >>> wrote: > > >>> > > And for the codenames, I mean 2019.03 could have also a moon > > chemical thing like Natrium or whatever. For me it is more to say > > and, instead > > >> of or. > > > > > > Cheers > > > > Chris > > > > > > > > Von: Kenneth Fogel > > Gesendet: Donnerstag, 24. Januar 2019 20:44 > > An: dev@netbeans.incubator.apache.org > > Betreff: RE: Apache NetBeans 11 or 11.0 ? > > > > We could use seemingly random words like Eclipse does so that no > > one > > >> knows > > what the most recent version is. For example, we could use the > > names > > of > > >> the > > 63 moons of Jupiter, the planet with the most moons. Also, select > > them randomly, users will catch on if we do it alphabetically. > > Here are the > > >> 51 > > named moons: > > > > AdrasteaErinome Isonoe Sponde > > Aitne Euanthe KaleTaygete > > AmaltheaEukeladeKallichore Thebe > > Ananke Euporie Kalyke Thelxinoe > > Aoede Europa KoreThemisto > > Arche EurydomeLedaThyone > > Autonoe GanymedeLysithea > > Callirrhoe Harpalyke Megaclite > > CallistoHegemoneMetis > > Carme Helike Mneme > > Carpo HermippeOrthosie > > ChaldeneHerse Pasiphae >
AW: Apache NetBeans 11 or 11.0 ?
+1 for calver. (Yearh.month) Cheers Chris Von: Neil C Smith Gesendet: Freitag, 25. Januar 2019 10:41 An: dev@netbeans.incubator.apache.org Betreff: Re: Apache NetBeans 11 or 11.0 ? On Fri, 25 Jan 2019 at 09:12, Tomas Poledny wrote: > I don't like calendar versioning. I have problem with remember it. It is > more easy to remember 11 or 11.0 than 2019.03. What will be next version > 2019.02 or 2019.03 or 2019.04 and what was previous version? > > So +1 for 11.0 Yes, +1 for 11.0, 12.0, 13.0 for me, for the same reasons. And just referring to it as NetBeans 11, NetBeans 12, etc. on website, splash, etc. I really don't understand the argument this caused with NetBeans 10 here if .1, .2, etc. are only intended to be patch releases? And that's the question I don't think we've really answered yet - if we're moving to time-based releases are all releases treated equal? Are all point releases just bug fixes *on the release branch*? -0 on date releases - not against it, but have a few questions if that went ahead. Can all our infrastructure manage that well? eg. do we use that in publishing platform artefacts to Maven, or do we end up using multiple version schemes? What happens when like NB 10 we need to delay a release for a blocker - do we end up having to rename 2018-10-rc to 2018-12? Is there any significance to a change from 2019.x to 2020.x? Does it change how we integrate NetCAT? I can't decide whether this thread is cosmetic bike-shedding or quite fundamental at the moment! ;-) Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Apache NetBeans 11 or 11.0 ?
On Fri, 25 Jan 2019 at 09:12, Tomas Poledny wrote: > I don't like calendar versioning. I have problem with remember it. It is > more easy to remember 11 or 11.0 than 2019.03. What will be next version > 2019.02 or 2019.03 or 2019.04 and what was previous version? > > So +1 for 11.0 Yes, +1 for 11.0, 12.0, 13.0 for me, for the same reasons. And just referring to it as NetBeans 11, NetBeans 12, etc. on website, splash, etc. I really don't understand the argument this caused with NetBeans 10 here if .1, .2, etc. are only intended to be patch releases? And that's the question I don't think we've really answered yet - if we're moving to time-based releases are all releases treated equal? Are all point releases just bug fixes *on the release branch*? -0 on date releases - not against it, but have a few questions if that went ahead. Can all our infrastructure manage that well? eg. do we use that in publishing platform artefacts to Maven, or do we end up using multiple version schemes? What happens when like NB 10 we need to delay a release for a blocker - do we end up having to rename 2018-10-rc to 2018-12? Is there any significance to a change from 2019.x to 2020.x? Does it change how we integrate NetCAT? I can't decide whether this thread is cosmetic bike-shedding or quite fundamental at the moment! ;-) Best wishes, Neil - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
[NETBEANS-965] & [NETBEANS-997]
Hi all :) Thought I might have a quick look into these (attempting to download Glassfish via NB results in "Not Found" error). I think one problem here is that for each supported version of Glassfish, there was a related text file on the old netbeans.org: * http://serverplugins.netbeans.org/glassfishv3/post701v3.txt * http://serverplugins.netbeans.org/glassfishv3/post701v3-0-1.txt * http://serverplugins.netbeans.org/glassfishv3/post701v3-1.txt * http://serverplugins.netbeans.org/glassfishv3/post701v3-1-1.txt * http://serverplugins.netbeans.org/glassfishv3/post71v3-1-2.txt * http://serverplugins.netbeans.org/glassfishv3/post71v3-1-2.txt * http://serverplugins.netbeans.org/glassfishv3/post71v4-0.txt * http://serverplugins.netbeans.org/glassfishv3/post71v4-0-1.txt * http://serverplugins.netbeans.org/glassfishv3/post71v4-1.txt * http://serverplugins.netbeans.org/glassfishv3/post71v4-1-1.txt * http://serverplugins.netbeans.org/glassfishv3/post71v5-0.txt Does anybody know: a) what these .txt files are? b) if they made it to a new home on netbeans.apache.org? P
RE: Apache NetBeans 11 or 11.0 ?
Hi, Is this only for branding? Or should we change the apidocs, the maven artefacts ? What if a release has to be released in a short period because of security fixes? Append calendar with day, use another moon or new element? Regards Eric -Message d'origine- De : Tomas Poledny Envoyé : vendredi 25 janvier 2019 10:12 À : dev@netbeans.incubator.apache.org Objet : Re: Apache NetBeans 11 or 11.0 ? Hi, I don't like calendar versioning. I have problem with remember it. It is more easy to remember 11 or 11.0 than 2019.03. What will be next version 2019.02 or 2019.03 or 2019.04 and what was previous version? So +1 for 11.0 Tomas On Fri, Jan 25, 2019 at 10:09 AM Daniel Gruno wrote: > On 1/25/19 9:48 AM, Geertjan Wielenga wrote: > > Are you saying you're against Emilian's proposal, i.e., 2019.03, > > calendar versioning? > > I'm not against it at all :) > My only suggestion or opinion would be that it should be something > where users can quickly see whether version A is newer or older than > version B. Both numerical and calendar versioning solve that. Using > nicknames would complicate matters, even if just slightly. > > > > > No, we're not going to start any vote at all, until we've seen > > whether we can reach consensus. Emilian's proposal is completely > > new. I like it, a lot. Let's see what others say first and then if > > we cannot reach > consensus, > > we'll do a vote. But I have a feeling we're able to reach consensus > around > > calendar versioning. > > > > Gj > > > > > > On Fri, Jan 25, 2019 at 9:32 AM Daniel Gruno > wrote: > > > >> On 1/25/19 9:30 AM, Geertjan Wielenga wrote: > >>> I think whatever is super simple and clear is what we should do > >>> and therefore I really like Emilian's suggestion. > >> > >> I think (hope?!) some of these suggestions were in jest. > >> Let's keep it simple - version numbers are free, 1,2,3,4,5,6I > >> could continue for quite a while before I run out :) > >> > >>> > >>> We spend more time and energy discussing release numbering than > anything > >>> else and the sooner that can stop the better. :-) > >>> > >>> Gj > >>> > >>> On Fri, Jan 25, 2019 at 9:28 AM Christian Lenz > >>> > > >>> wrote: > >>> > And for the codenames, I mean 2019.03 could have also a moon > chemical thing like Natrium or whatever. For me it is more to say > and, instead > >> of or. > > > Cheers > > Chris > > > > Von: Kenneth Fogel > Gesendet: Donnerstag, 24. Januar 2019 20:44 > An: dev@netbeans.incubator.apache.org > Betreff: RE: Apache NetBeans 11 or 11.0 ? > > We could use seemingly random words like Eclipse does so that no > one > >> knows > what the most recent version is. For example, we could use the > names > of > >> the > 63 moons of Jupiter, the planet with the most moons. Also, select > them randomly, users will catch on if we do it alphabetically. > Here are the > >> 51 > named moons: > > AdrasteaErinome Isonoe Sponde > Aitne Euanthe KaleTaygete > AmaltheaEukeladeKallichore Thebe > Ananke Euporie Kalyke Thelxinoe > Aoede Europa KoreThemisto > Arche EurydomeLedaThyone > Autonoe GanymedeLysithea > Callirrhoe Harpalyke Megaclite > CallistoHegemoneMetis > Carme Helike Mneme > Carpo HermippeOrthosie > ChaldeneHerse Pasiphae > Cyllene Himalia Pasithee > Dia Io Praxidike > Elara Iocaste Sinope > > There are about 12 more moons with numeric names awaiting formal > names. > > Ken > > > > >>> > >> > >> > >> --- > >> -- To unsubscribe, e-mail: > >> dev-unsubscr...@netbeans.incubator.apache.org > >> For additional commands, e-mail: > >> dev-h...@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-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: > dev-h...@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-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBean
Re: Apache NetBeans 11 or 11.0 ?
+1 to calendar versioning. +1 to NOT using nicknames. I still have to learn if Debian Wheezy is older or newer than Debian WhateverTheFlippingName El 25/01/2019 a las 10:02, Daniel Gruno escribió: On 1/25/19 9:48 AM, Geertjan Wielenga wrote: Are you saying you're against Emilian's proposal, i.e., 2019.03, calendar versioning? I'm not against it at all :) My only suggestion or opinion would be that it should be something where users can quickly see whether version A is newer or older than version B. Both numerical and calendar versioning solve that. Using nicknames would complicate matters, even if just slightly. - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Apache NetBeans 11 or 11.0 ?
Hi, I don't like calendar versioning. I have problem with remember it. It is more easy to remember 11 or 11.0 than 2019.03. What will be next version 2019.02 or 2019.03 or 2019.04 and what was previous version? So +1 for 11.0 Tomas On Fri, Jan 25, 2019 at 10:09 AM Daniel Gruno wrote: > On 1/25/19 9:48 AM, Geertjan Wielenga wrote: > > Are you saying you're against Emilian's proposal, i.e., 2019.03, calendar > > versioning? > > I'm not against it at all :) > My only suggestion or opinion would be that it should be something where > users can quickly see whether version A is newer or older than version > B. Both numerical and calendar versioning solve that. Using nicknames > would complicate matters, even if just slightly. > > > > > No, we're not going to start any vote at all, until we've seen whether we > > can reach consensus. Emilian's proposal is completely new. I like it, a > > lot. Let's see what others say first and then if we cannot reach > consensus, > > we'll do a vote. But I have a feeling we're able to reach consensus > around > > calendar versioning. > > > > Gj > > > > > > On Fri, Jan 25, 2019 at 9:32 AM Daniel Gruno > wrote: > > > >> On 1/25/19 9:30 AM, Geertjan Wielenga wrote: > >>> I think whatever is super simple and clear is what we should do and > >>> therefore I really like Emilian's suggestion. > >> > >> I think (hope?!) some of these suggestions were in jest. > >> Let's keep it simple - version numbers are free, 1,2,3,4,5,6I could > >> continue for quite a while before I run out :) > >> > >>> > >>> We spend more time and energy discussing release numbering than > anything > >>> else and the sooner that can stop the better. :-) > >>> > >>> Gj > >>> > >>> On Fri, Jan 25, 2019 at 9:28 AM Christian Lenz > > >>> wrote: > >>> > And for the codenames, I mean 2019.03 could have also a moon chemical > thing like Natrium or whatever. For me it is more to say and, instead > >> of or. > > > Cheers > > Chris > > > > Von: Kenneth Fogel > Gesendet: Donnerstag, 24. Januar 2019 20:44 > An: dev@netbeans.incubator.apache.org > Betreff: RE: Apache NetBeans 11 or 11.0 ? > > We could use seemingly random words like Eclipse does so that no one > >> knows > what the most recent version is. For example, we could use the names > of > >> the > 63 moons of Jupiter, the planet with the most moons. Also, select them > randomly, users will catch on if we do it alphabetically. Here are the > >> 51 > named moons: > > AdrasteaErinome Isonoe Sponde > Aitne Euanthe KaleTaygete > AmaltheaEukeladeKallichore Thebe > Ananke Euporie Kalyke Thelxinoe > Aoede Europa KoreThemisto > Arche EurydomeLedaThyone > Autonoe GanymedeLysithea > Callirrhoe Harpalyke Megaclite > CallistoHegemoneMetis > Carme Helike Mneme > Carpo HermippeOrthosie > ChaldeneHerse Pasiphae > Cyllene Himalia Pasithee > Dia Io Praxidike > Elara Iocaste Sinope > > There are about 12 more moons with numeric names awaiting formal > names. > > Ken > > > > >>> > >> > >> > >> - > >> To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > >> For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: Apache NetBeans 11 or 11.0 ?
On 1/25/19 9:48 AM, Geertjan Wielenga wrote: Are you saying you're against Emilian's proposal, i.e., 2019.03, calendar versioning? I'm not against it at all :) My only suggestion or opinion would be that it should be something where users can quickly see whether version A is newer or older than version B. Both numerical and calendar versioning solve that. Using nicknames would complicate matters, even if just slightly. No, we're not going to start any vote at all, until we've seen whether we can reach consensus. Emilian's proposal is completely new. I like it, a lot. Let's see what others say first and then if we cannot reach consensus, we'll do a vote. But I have a feeling we're able to reach consensus around calendar versioning. Gj On Fri, Jan 25, 2019 at 9:32 AM Daniel Gruno wrote: On 1/25/19 9:30 AM, Geertjan Wielenga wrote: I think whatever is super simple and clear is what we should do and therefore I really like Emilian's suggestion. I think (hope?!) some of these suggestions were in jest. Let's keep it simple - version numbers are free, 1,2,3,4,5,6I could continue for quite a while before I run out :) We spend more time and energy discussing release numbering than anything else and the sooner that can stop the better. :-) Gj On Fri, Jan 25, 2019 at 9:28 AM Christian Lenz wrote: And for the codenames, I mean 2019.03 could have also a moon chemical thing like Natrium or whatever. For me it is more to say and, instead of or. Cheers Chris Von: Kenneth Fogel Gesendet: Donnerstag, 24. Januar 2019 20:44 An: dev@netbeans.incubator.apache.org Betreff: RE: Apache NetBeans 11 or 11.0 ? We could use seemingly random words like Eclipse does so that no one knows what the most recent version is. For example, we could use the names of the 63 moons of Jupiter, the planet with the most moons. Also, select them randomly, users will catch on if we do it alphabetically. Here are the 51 named moons: AdrasteaErinome Isonoe Sponde Aitne Euanthe KaleTaygete AmaltheaEukeladeKallichore Thebe Ananke Euporie Kalyke Thelxinoe Aoede Europa KoreThemisto Arche EurydomeLedaThyone Autonoe GanymedeLysithea Callirrhoe Harpalyke Megaclite CallistoHegemoneMetis Carme Helike Mneme Carpo HermippeOrthosie ChaldeneHerse Pasiphae Cyllene Himalia Pasithee Dia Io Praxidike Elara Iocaste Sinope There are about 12 more moons with numeric names awaiting formal names. Ken - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@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-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
Re: Apache NetBeans 11 or 11.0 ?
Are you saying you're against Emilian's proposal, i.e., 2019.03, calendar versioning? No, we're not going to start any vote at all, until we've seen whether we can reach consensus. Emilian's proposal is completely new. I like it, a lot. Let's see what others say first and then if we cannot reach consensus, we'll do a vote. But I have a feeling we're able to reach consensus around calendar versioning. Gj On Fri, Jan 25, 2019 at 9:32 AM Daniel Gruno wrote: > On 1/25/19 9:30 AM, Geertjan Wielenga wrote: > > I think whatever is super simple and clear is what we should do and > > therefore I really like Emilian's suggestion. > > I think (hope?!) some of these suggestions were in jest. > Let's keep it simple - version numbers are free, 1,2,3,4,5,6I could > continue for quite a while before I run out :) > > > > > We spend more time and energy discussing release numbering than anything > > else and the sooner that can stop the better. :-) > > > > Gj > > > > On Fri, Jan 25, 2019 at 9:28 AM Christian Lenz > > wrote: > > > >> And for the codenames, I mean 2019.03 could have also a moon chemical > >> thing like Natrium or whatever. For me it is more to say and, instead > of or. > >> > >> > >> Cheers > >> > >> Chris > >> > >> > >> > >> Von: Kenneth Fogel > >> Gesendet: Donnerstag, 24. Januar 2019 20:44 > >> An: dev@netbeans.incubator.apache.org > >> Betreff: RE: Apache NetBeans 11 or 11.0 ? > >> > >> We could use seemingly random words like Eclipse does so that no one > knows > >> what the most recent version is. For example, we could use the names of > the > >> 63 moons of Jupiter, the planet with the most moons. Also, select them > >> randomly, users will catch on if we do it alphabetically. Here are the > 51 > >> named moons: > >> > >> AdrasteaErinome Isonoe Sponde > >> Aitne Euanthe KaleTaygete > >> AmaltheaEukeladeKallichore Thebe > >> Ananke Euporie Kalyke Thelxinoe > >> Aoede Europa KoreThemisto > >> Arche EurydomeLedaThyone > >> Autonoe GanymedeLysithea > >> Callirrhoe Harpalyke Megaclite > >> CallistoHegemoneMetis > >> Carme Helike Mneme > >> Carpo HermippeOrthosie > >> ChaldeneHerse Pasiphae > >> Cyllene Himalia Pasithee > >> Dia Io Praxidike > >> Elara Iocaste Sinope > >> > >> There are about 12 more moons with numeric names awaiting formal names. > >> > >> Ken > >> > >> > >> > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: Apache NetBeans 11 or 11.0 ?
> > On 1/25/19 9:30 AM, Geertjan Wielenga wrote: > > I think whatever is super simple and clear is what we should do and > > therefore I really like Emilian's suggestion. > > I think (hope?!) some of these suggestions were in jest. > Let's keep it simple - version numbers are free, 1,2,3,4,5,6I could > continue for quite a while before I run out :) > Which suggestions were in jest? No, this is an extremely lengthy discussion where everyone is very serious -- and I'm not sure this intervention is helpful. Yes, version numbers are free. OK. Gj On Fri, Jan 25, 2019 at 9:32 AM Daniel Gruno wrote: > On 1/25/19 9:30 AM, Geertjan Wielenga wrote: > > I think whatever is super simple and clear is what we should do and > > therefore I really like Emilian's suggestion. > > I think (hope?!) some of these suggestions were in jest. > Let's keep it simple - version numbers are free, 1,2,3,4,5,6I could > continue for quite a while before I run out :) > > > > > We spend more time and energy discussing release numbering than anything > > else and the sooner that can stop the better. :-) > > > > Gj > > > > On Fri, Jan 25, 2019 at 9:28 AM Christian Lenz > > wrote: > > > >> And for the codenames, I mean 2019.03 could have also a moon chemical > >> thing like Natrium or whatever. For me it is more to say and, instead > of or. > >> > >> > >> Cheers > >> > >> Chris > >> > >> > >> > >> Von: Kenneth Fogel > >> Gesendet: Donnerstag, 24. Januar 2019 20:44 > >> An: dev@netbeans.incubator.apache.org > >> Betreff: RE: Apache NetBeans 11 or 11.0 ? > >> > >> We could use seemingly random words like Eclipse does so that no one > knows > >> what the most recent version is. For example, we could use the names of > the > >> 63 moons of Jupiter, the planet with the most moons. Also, select them > >> randomly, users will catch on if we do it alphabetically. Here are the > 51 > >> named moons: > >> > >> AdrasteaErinome Isonoe Sponde > >> Aitne Euanthe KaleTaygete > >> AmaltheaEukeladeKallichore Thebe > >> Ananke Euporie Kalyke Thelxinoe > >> Aoede Europa KoreThemisto > >> Arche EurydomeLedaThyone > >> Autonoe GanymedeLysithea > >> Callirrhoe Harpalyke Megaclite > >> CallistoHegemoneMetis > >> Carme Helike Mneme > >> Carpo HermippeOrthosie > >> ChaldeneHerse Pasiphae > >> Cyllene Himalia Pasithee > >> Dia Io Praxidike > >> Elara Iocaste Sinope > >> > >> There are about 12 more moons with numeric names awaiting formal names. > >> > >> Ken > >> > >> > >> > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
Re: Apache NetBeans 11 or 11.0 ?
On 1/25/19 9:30 AM, Geertjan Wielenga wrote: I think whatever is super simple and clear is what we should do and therefore I really like Emilian's suggestion. I think (hope?!) some of these suggestions were in jest. Let's keep it simple - version numbers are free, 1,2,3,4,5,6I could continue for quite a while before I run out :) We spend more time and energy discussing release numbering than anything else and the sooner that can stop the better. :-) Gj On Fri, Jan 25, 2019 at 9:28 AM Christian Lenz wrote: And for the codenames, I mean 2019.03 could have also a moon chemical thing like Natrium or whatever. For me it is more to say and, instead of or. Cheers Chris Von: Kenneth Fogel Gesendet: Donnerstag, 24. Januar 2019 20:44 An: dev@netbeans.incubator.apache.org Betreff: RE: Apache NetBeans 11 or 11.0 ? We could use seemingly random words like Eclipse does so that no one knows what the most recent version is. For example, we could use the names of the 63 moons of Jupiter, the planet with the most moons. Also, select them randomly, users will catch on if we do it alphabetically. Here are the 51 named moons: AdrasteaErinome Isonoe Sponde Aitne Euanthe KaleTaygete AmaltheaEukeladeKallichore Thebe Ananke Euporie Kalyke Thelxinoe Aoede Europa KoreThemisto Arche EurydomeLedaThyone Autonoe GanymedeLysithea Callirrhoe Harpalyke Megaclite CallistoHegemoneMetis Carme Helike Mneme Carpo HermippeOrthosie ChaldeneHerse Pasiphae Cyllene Himalia Pasithee Dia Io Praxidike Elara Iocaste Sinope There are about 12 more moons with numeric names awaiting formal names. Ken - To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org For further information about the NetBeans mailing lists, visit: https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
AW: Apache NetBeans 11 or 11.0 ?
Sure, but as you can see, we have different opinions about that. I mean if it is that simple, we can now start a vote for the suggestions? Cheers Chris Von: Geertjan Wielenga Gesendet: Freitag, 25. Januar 2019 09:30 An: dev Betreff: Re: Apache NetBeans 11 or 11.0 ? I think whatever is super simple and clear is what we should do and therefore I really like Emilian's suggestion. We spend more time and energy discussing release numbering than anything else and the sooner that can stop the better. :-) Gj On Fri, Jan 25, 2019 at 9:28 AM Christian Lenz wrote: > And for the codenames, I mean 2019.03 could have also a moon chemical > thing like Natrium or whatever. For me it is more to say and, instead of or. > > > Cheers > > Chris > > > > Von: Kenneth Fogel > Gesendet: Donnerstag, 24. Januar 2019 20:44 > An: dev@netbeans.incubator.apache.org > Betreff: RE: Apache NetBeans 11 or 11.0 ? > > We could use seemingly random words like Eclipse does so that no one knows > what the most recent version is. For example, we could use the names of the > 63 moons of Jupiter, the planet with the most moons. Also, select them > randomly, users will catch on if we do it alphabetically. Here are the 51 > named moons: > > AdrasteaErinome Isonoe Sponde > Aitne Euanthe KaleTaygete > AmaltheaEukeladeKallichore Thebe > Ananke Euporie Kalyke Thelxinoe > Aoede Europa KoreThemisto > Arche EurydomeLedaThyone > Autonoe GanymedeLysithea > Callirrhoe Harpalyke Megaclite > CallistoHegemoneMetis > Carme Helike Mneme > Carpo HermippeOrthosie > ChaldeneHerse Pasiphae > Cyllene Himalia Pasithee > Dia Io Praxidike > Elara Iocaste Sinope > > There are about 12 more moons with numeric names awaiting formal names. > > Ken > > >
Re: Apache NetBeans 11 or 11.0 ?
I think whatever is super simple and clear is what we should do and therefore I really like Emilian's suggestion. We spend more time and energy discussing release numbering than anything else and the sooner that can stop the better. :-) Gj On Fri, Jan 25, 2019 at 9:28 AM Christian Lenz wrote: > And for the codenames, I mean 2019.03 could have also a moon chemical > thing like Natrium or whatever. For me it is more to say and, instead of or. > > > Cheers > > Chris > > > > Von: Kenneth Fogel > Gesendet: Donnerstag, 24. Januar 2019 20:44 > An: dev@netbeans.incubator.apache.org > Betreff: RE: Apache NetBeans 11 or 11.0 ? > > We could use seemingly random words like Eclipse does so that no one knows > what the most recent version is. For example, we could use the names of the > 63 moons of Jupiter, the planet with the most moons. Also, select them > randomly, users will catch on if we do it alphabetically. Here are the 51 > named moons: > > AdrasteaErinome Isonoe Sponde > Aitne Euanthe KaleTaygete > AmaltheaEukeladeKallichore Thebe > Ananke Euporie Kalyke Thelxinoe > Aoede Europa KoreThemisto > Arche EurydomeLedaThyone > Autonoe GanymedeLysithea > Callirrhoe Harpalyke Megaclite > CallistoHegemoneMetis > Carme Helike Mneme > Carpo HermippeOrthosie > ChaldeneHerse Pasiphae > Cyllene Himalia Pasithee > Dia Io Praxidike > Elara Iocaste Sinope > > There are about 12 more moons with numeric names awaiting formal names. > > Ken > > >
AW: Apache NetBeans 11 or 11.0 ?
And for the codenames, I mean 2019.03 could have also a moon chemical thing like Natrium or whatever. For me it is more to say and, instead of or. Cheers Chris Von: Kenneth Fogel Gesendet: Donnerstag, 24. Januar 2019 20:44 An: dev@netbeans.incubator.apache.org Betreff: RE: Apache NetBeans 11 or 11.0 ? We could use seemingly random words like Eclipse does so that no one knows what the most recent version is. For example, we could use the names of the 63 moons of Jupiter, the planet with the most moons. Also, select them randomly, users will catch on if we do it alphabetically. Here are the 51 named moons: AdrasteaErinome Isonoe Sponde Aitne Euanthe KaleTaygete AmaltheaEukeladeKallichore Thebe Ananke Euporie Kalyke Thelxinoe Aoede Europa KoreThemisto Arche EurydomeLedaThyone Autonoe GanymedeLysithea Callirrhoe Harpalyke Megaclite CallistoHegemoneMetis Carme Helike Mneme Carpo HermippeOrthosie ChaldeneHerse Pasiphae Cyllene Himalia Pasithee Dia Io Praxidike Elara Iocaste Sinope There are about 12 more moons with numeric names awaiting formal names. Ken
Re: Apache NetBeans 11 or 11.0 ?
I think this is something to discuss and we could probably reach consensus around it without a vote. I’m in favor of it for its simplicity and indeed alignment with other tools. Gj On Friday, January 25, 2019, Emilian Bold wrote: > So now, both IntelliJ and Eclipse use calendar versioning (2019.03) > but it seems crazy to suggest this for NetBeans? > > I guess this is also a branding strategy: be against the trends. > > --emi > > http://coolbeans.xyz/ - CoolBeans: An IDE for Java, JavaEE, PHP and more! > > On Thu, Jan 24, 2019 at 10:58 PM Christian Bourque > wrote: > > > > Just so you know, Eclipse stopped using this nomenclature recently! > > > > From now on, it's going to simply be the year and month of release (e.g.: > > Eclipse IDE 2018-12)! > > > > C. > > > > > > On Thu, Jan 24, 2019 at 2:44 PM Kenneth Fogel < > kfo...@dawsoncollege.qc.ca> > > wrote: > > > > > We could use seemingly random words like Eclipse does so that no one > knows > > > what the most recent version is. For example, we could use the names > of the > > > 63 moons of Jupiter, the planet with the most moons. Also, select them > > > randomly, users will catch on if we do it alphabetically. Here are the > 51 > > > named moons: > > > > > > AdrasteaErinome Isonoe Sponde > > > Aitne Euanthe KaleTaygete > > > AmaltheaEukeladeKallichore Thebe > > > Ananke Euporie Kalyke Thelxinoe > > > Aoede Europa KoreThemisto > > > Arche EurydomeLedaThyone > > > Autonoe GanymedeLysithea > > > Callirrhoe Harpalyke Megaclite > > > CallistoHegemoneMetis > > > Carme Helike Mneme > > > Carpo HermippeOrthosie > > > ChaldeneHerse Pasiphae > > > Cyllene Himalia Pasithee > > > Dia Io Praxidike > > > Elara Iocaste Sinope > > > > > > There are about 12 more moons with numeric names awaiting formal names. > > > > > > Ken > > > > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@netbeans.incubator.apache.org > For additional commands, e-mail: dev-h...@netbeans.incubator.apache.org > > For further information about the NetBeans mailing lists, visit: > https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists > > > >
