On 09.03.22 14:43, Jaroslav Tulach wrote:
But to pick a concrete (while random) example: lucene 9.x only supports
JDK11+, the maven indexer modules are stuck with 5.x, updating it to 8.x
might require manually patching a certain bugfix form 9.x to 8.x since
there are no new releases planned for
ne 6. 3. 2022 v 17:02 odesílatel Michael Bien napsal:
> On 06.03.22 16:06, Jaroslav Tulach wrote:
> >> But as you pointed out some modules which are used by the language
> >> server have to be kept compatible with 8 unfortunately, which causes a
> >> lot of ongoing issues but it is what it is.
>
I see "The moment" vs. "At the moment". Yes, then it is not "F.U.D", but a
serious evaluation. Sorry for the misreading - I wasn't expecting switch to
reasonable arguments after two paragraphs of offense.
-jt
út 8. 3. 2022 v 12:40 odesílatel Neil C Smith
napsal:
> On Tue, 8 Mar 2022 at 11:14, J
On Tue, 8 Mar 2022 at 11:14, Jaroslav Tulach wrote:
>
> Spreading F.U.D., Matthias?
>
> The moment you can't compile for JDK 8 anymore with the currently
> > available JDK
>
> jdk-17/bin/javac --help | grep release
I think you mis-read his post!
I broadly agree with him, although I think that pa
Spreading F.U.D., Matthias?
The moment you can't compile for JDK 8 anymore with the currently
> available JDK
jdk-17/bin/javac --help | grep release
Enable preview language features. To be used in conjunction with
either -source or --release.
--release
Compile for the specified J
On Mon, 7 Mar 2022 at 11:17, Michael Bien wrote:
> can i help with this somehow? Does it fail hard or does it produce wrong
> results? What would be the ant task in question?
>
> (sorry for so many questions)
Questions with offers of help are always welcome! :-)
This problem for a start needs a
On 07.03.22 11:12, Neil C Smith wrote:
Unofficially, build on JDK 8 still works with NetBeans 13 because
certain Ant tasks (eg. sigtest things) and bits of testing
infrastructure don't actually work on JDK 11 yet!
We need to fix sigtest generation in delivery or we're not going to
get any API si
On Sun, 6 Mar 2022 at 15:06, Jaroslav Tulach wrote:
> Yes, the decision is: the tests must run on JDK8. If you disagree with my
> statement, present an evidence: show me where a decision to drop JDK8 for
> (automatic) testing has been made!
The decision that was made was actually "Automated testi
On Sun, 6 Mar 2022 at 14:14, Michael Bien wrote:
>
> we could remove the note on the download page for the next release.
>
> I don't think its super useful anyway. Describing edge cases can cause
> issues if someone is only reading part of it etc.
We can remove it now! https://github.com/apache/
Hi,
Am Sonntag, dem 06.03.2022 um 16:06 +0100 schrieb Jaroslav Tulach:
> > NB 12.6 and 13 itself only support JDK 11 and 17, if some of it
> > still
> > runs on 8 its a coincidence. Nobody should run the IDE on 8.
>
> I do. I am running my NetBeans on JDK8 based GraalVM. And it is not a
> coincid
On 06.03.22 16:06, Jaroslav Tulach wrote:
But as you pointed out some modules which are used by the language
server have to be kept compatible with 8 unfortunately, which causes a
lot of ongoing issues but it is what it is.
Can I get pointer to the list of "lot of ongoing issues", please? Thank
Re-reading this thread (
https://lists.apache.org/thread/m2o2sswphmytb18yssd76zy5lmoljxvd), it
mentions attempts to cleanup stuff during gradle testing which was not
possible due to it still being in use which may cause some problems. The
thread has excerpts from the build/failures at the time (th
Dne neděle 6. března 2022 13:46:23 CET, Michael Bien napsal(a):
> On 06.03.22 05:07, Jaroslav Tulach wrote:
> > Dne sobota 5. března 2022 17:54:46 CET, antonio napsal(a):
> >> a) do we need these now that JDK >= 11 is required to run NetBeans?
> >> b) if not, can we get rid of them?
> >
> > No, we
we could remove the note on the download page for the next release.
I don't think its super useful anyway. Describing edge cases can cause
issues if someone is only reading part of it etc.
-mbien
On 06.03.22 14:51, antonio wrote:
Clear now :-)
The README.md file in the sources.zip states, t
Clear now :-)
The README.md file in the sources.zip states, though:
- JDK 11 (to build NetBeans)
- JDK 11 or above (to run NetBeans)
No mention to JDK8, that's why I was confused :-).
Cheers,
Antonio
El 6/3/22 a las 14:29, Michael Bien escribió:
what is confusing? :)
--
what is confusing? :)
"The Apache NetBeans 13 binary releases require JDK 11+, and officially
support running on JDK 11 and JDK 17."
and later:
"Apache NetBeans 13 can be run on JDK 8, with some features disabled, if
built from source using JDK 8. "
meaning: NB requires JDK 11+, unless yo
I'm still somewhat confused :-(
In the README.md of NB13 [1] we say that 11 is required to build/run,
but in the release page [2] we say that 8 can be used to build/run.
Cheers,
Antonio
[1]
https://github.com/apache/netbeans/blob/release130/README.md
[2]
https://netbeans.apache.org/download/
On 06.03.22 05:07, Jaroslav Tulach wrote:
Dne sobota 5. března 2022 17:54:46 CET, antonio napsal(a):
a) do we need these now that JDK >= 11 is required to run NetBeans?
b) if not, can we get rid of them?
No, we cannot get rid of them. While we are compiling on JDK11, the
requirement still is to
Dne sobota 5. března 2022 19:21:53 CET, Michael Bien napsal(a):
> > So it seems our Travis builds fail randomly on (at least) the
> > following tasks:
>
> yes those are known to fail, esp job 13. I had to brute force this one 5
> times yesterday until it passed - i almost reverted a PR since I tho
Dne sobota 5. března 2022 17:54:46 CET, antonio napsal(a):
> a) do we need these now that JDK >= 11 is required to run NetBeans?
> b) if not, can we get rid of them?
No, we cannot get rid of them. While we are compiling on JDK11, the
requirement still is to run and test on JDK8. That can only cha
unfortunately the travis mails you get when the build fails point to the
most recent build after restarts, so i can't find logs retroactively.
Thats why began with a simple list yesterday, it has only two entries so
far (job 13):
org.netbeans.modules.java.lsp.server.explorer.ProjectViewTest
Raw logs preferred, like so:
https://api.travis-ci.com/v3/job/562190248/log.txt
Thanks,
Antonio
El 5/3/22 a las 19:39, antonio escribió:
Since this a PITA, I volunteer to take a look at these.
Would you please attach a list of failures so I can try to see what the
problem is?
Here's a firs
Since this a PITA, I volunteer to take a look at these.
Would you please attach a list of failures so I can try to see what the
problem is?
Here's a first one:
https://app.travis-ci.com/github/apache/netbeans/builds/247446384
Thanks,
Antonio
El 5/3/22 a las 19:21, Michael Bien escribió:
let
Hi Antonio,
On 05.03.22 17:54, antonio wrote:
Hi all,
So it seems our Travis builds fail randomly on (at least) the
following tasks:
- 11538.13 Test Java modules with nb-javac on Java 8
- 11538.14 Test java.hints batch 1 with nb-javac on Java 8
yes those are known to fail, esp job 13. I ha
There was similar discussion on this previously last year. See below
references discussions,
At the time, the going theory may have been related to different java
versions involved which may impact existing "gradle" daemon context but
never drill down beyond that.
Also, not sure if with the nb-
Hi all,
So it seems our Travis builds fail randomly on (at least) the following
tasks:
- 11538.13 Test Java modules with nb-javac on Java 8
- 11538.14 Test java.hints batch 1 with nb-javac on Java 8
Questions are:
a) do we need these now that JDK >= 11 is required to run NetBeans?
b) if not,
On Wed, 26 Jun 2019 at 16:47, Gaurav Gupta wrote:
>
> Thanks Neil, I am looking at the attributes conflicts.
Great, thanks. There also seems to be a versioning issue (possibly
with a plugin elsewhere?) so the IDE wants to update your plugin
immediately. Need to check if that happens when beta2
Thanks Neil, I am looking at the attributes conflicts.
Thanks and kind regards,
Gaurav Gupta
On Wed, Jun 26, 2019 at 7:40 PM Neil C Smith wrote:
> On Wed, 26 Jun 2019 at 14:25, Geertjan Wielenga
> wrote:
> > Yes, Gaurav’s Payara PRs and Josh’s Java EE 8 work needs to be in beta-2.
>
> 2 o
On Wed, 26 Jun 2019 at 14:25, Geertjan Wielenga wrote:
> Yes, Gaurav’s Payara PRs and Josh’s Java EE 8 work needs to be in beta-2.
2 out of 3 were already in master. One of the Payara ones had a merge
conflict with the other one, which was fixed. However, I think there
is a test conflict somewh
Yes, Gaurav’s Payara PRs and Josh’s Java EE 8 work needs to be in beta-2.
Gj
On Wed, 26 Jun 2019 at 14:46, Neil C Smith wrote:
> On Wed, 26 Jun 2019 at 11:59, Geertjan Wielenga
> wrote:
> >
> > Since it’s a beta release, I wouldn’t let Travis stop you, especially if
> we
> > can identify the p
On Wed, 26 Jun 2019 at 11:59, Geertjan Wielenga wrote:
>
> Since it’s a beta release, I wouldn’t let Travis stop you, especially if we
> can identify the problem to fix post beta-2.
OK, I'll merge the Payara Server PR at least then. Not ideal, but it
was passing until the last commit to merge ma
Since it’s a beta release, I wouldn’t let Travis stop you, especially if we
can identify the problem to fix post beta-2.
Gj
On Wed, 26 Jun 2019 at 12:40, Neil C Smith wrote:
> Hi,
>
> Seems we're getting a lot of Travis failures at the moment. There
> were some commits chang
Hi,
Seems we're getting a lot of Travis failures at the moment. There
were some commits changing travis config in master the other day,
which doesn't seem great timing, but I'm not sure that's the reason.
A few messages suggesting failures with osuosl downloads? Somewha
33 matches
Mail list logo
