+1
John Neffenger
On 4/11/23 1:16 AM, Neil C Smith wrote:
# Proposed policy
* Apache NetBeans 18 will be the last release to support running the
platform on JDK 8.
* From Apache NetBeans 19, the minimum JDK required to build and run
the IDE or platform will be JDK 11.
* Future releases
On 4/10/23 5:08 AM, Svata Dedic wrote:
I am advocating not to drop JDK8 as runtime for NetBeans (extended)
Platform, as that decision affects NetBeans-based applications.
Microchip IDE, that mining analytic stuff we had presentation a long
time ago (but that still IMHO lives), and possibly
On 4/4/23 1:24 PM, László Kishalmi wrote:
It would be possible to package a downloaded JDK along with the Snap or
have one downloaded during the install phase. However then comes the
question: which one?
I actually created a NetBeans Snap package that does just that. It
downloads and connects
+1 from me for the proposal.
On 4/3/23 2:38 AM, Neil C Smith wrote:
Three JDKs will be supported at any one time - the current JDK, plus
the previous two LTS releases. eg. NetBeans 20 and 21 (Nov 2023 / Feb
2024) will support JDK 11, 17 and 21. NetBeans 22 (May 2024) will
support JDK 17, 21 and
On 2/15/23 10:14 AM, name name2 wrote:
Hello
.io.IOException: Could not connect to
https://gitbox.apache.org/repos/asf?p=netbeans-jenkins-lib.git;a=blob_plain;f=meta/netbeansrelease.json
within 15000 milliseconds
I assume you got that message while building NetBeans.
If so, it is likely
On 2/8/23 8:38 PM, Jaroslav Tulach wrote:
These days it is JDK8 - the primary reason being that
Android supports JDK8 - as such, should a library be aspire to be used on
Android (as well as regular Java), it needs to stick to version eight.
There are some benefits to that strategy, but there's
On 1/28/23 10:55 AM, Łukasz Bownik wrote:
I noticed that as soon as I push a branch to my copy of the repository CI
picks it up. Is there a way to postpone CI process until a PR is being
created?
Can't we just disable GitHub Actions in the forked repository?
I did that under Settings > Code
I always thought it would be nice to be able to use Markdown in Javadoc
comments, but this was a big surprise!
JDK-8298405: Markdown support in the standard doclet
https://github.com/openjdk/jdk/pull/11701
It's targeted for JDK 21. Will NetBeans need to do anything extra to
support this
On 11/2/22 11:16 AM, Michael Bien wrote:
I have a list of options I usually change when setting up NetBeans.
One more I would add: change the default keyboard shortcuts for shifting
editor tabs from their current values of:
Shift Window Tab Left - Ctrl+Alt+Shift+LEFT
Shift Window Tab
On 11/2/22 11:16 AM, Michael Bien wrote:
grouped tab list (tools -> options -> appearance -> doc tabs -> and
check "Sort opened documents list by project")
Okay by me.
small toolbar icons:
Those are very tiny on my 109-dpi (non-HiDPI) 27-inch monitor.
view -> show versioning label:
As the progress on my pull request has stalled, I'm starting over with a
proper bug report:
Building with proxies causes DoS attack on OSU
https://github.com/apache/netbeans/issues/4890
"Building NetBeans in an environment that defines both proxy
variables causes a brief
On 10/13/22 3:26 AM, Michael Bien wrote:
When you clone a repo, gh won't have any actions enabled (I just checked
to confirm that it is still the case). The action tab will show a
confirmation/warning:
"Workflows aren’t being run on this forked repository"
I just checked to confirm, too,
On 10/12/22 8:55 AM, Michael Bien wrote:
the NB repo has this enabled. PRs from non-committers would not trigger
CI until someone approves the workflow run.
Just to clarify ...
I am not a committer -- I can't merge pull requests -- yet the GitHub
Actions ran automatically. I am a minor
On 10/12/22 3:00 AM, Michael Bien wrote:
if you clone the project you getting the same behavior, just on your own
copy.
Thank you, Michael. Four years in, and I'm still learning GitHub. :-)
its defined on the very top of the .github/workflows/main.yml file in
your master branch.
Got it. I
I was surprised to see test jobs triggered when I synced the upstream
master branch with the master branch of my fork:
https://github.com/jgneff/netbeans/actions/runs/3228261286
I expected tests to be triggered only when pushing a commit to the
branch of a pull request.
For example, on
On 6/22/22 12:35 PM, John Neffenger wrote:
$ diff -s binaries.log cache.log
Files binaries.log and cache.log are identical
A better comparison ...
$ ant -quiet -Dmetabuild.branch=master download-all-extbins
$ find ~/.hgexternalcache/ -type f | sed
's|^/home/ubuntu/.hgexternalcache
On 6/22/22 8:15 AM, Neil C Smith wrote:
Why are you surprised there's caching?
Thank you, Neil. Now I get it.
I hadn't realized that the files going into the repository directory (in
~/src/netbeans) were the same ones being cached for the next time (in
~/.hgexternalcache). I thought they
On 6/21/22 10:26 AM, Matthias Bläsing wrote:
I ran a clean build (after removing ~/.hgexternal). The build with a
direct connection still works.
Thank you, Matthias.
As an aside, I was surprised that the build downloads directly to the
repository directory in addition to '~/.hgexternal'. I
On 6/15/22 3:05 AM, Neil C Smith wrote:
I can think of at least one person who checks the diff between source
bundle and git repository when voting - that could be made more
explicit in the voting instructions perhaps?
That verification of every file (every line!) in the source release
seems
On 6/14/22 11:28 AM, Ernie Rael wrote:
I built nb based on current delivery branch for local use (I see that
release140 is now available). I'd like to know what difference there is
from this to what is released.
I build from the 'release140' branch on GitHub, and below are the
differences
If you build NetBeans behind a proxy server, I would greatly appreciate
your help in testing the following pull request:
Make one connection to download a file, not three
https://github.com/apache/netbeans/pull/4206
The test involves deleting the external cache (742 MB) and building
On 5/25/22 10:27 AM, Michael Bien wrote:
async-profiler[1] combined with flame graphs can be helpful to find
bottlenecks of long running tasks (> few seconds).
+1 for async-profiler! It can let you get a much bigger picture than is
possible with most other profilers, and it often shows you
On 12/7/21 4:58 AM, Eric Bresie wrote:
I know this is a grander, not a short term thing, and a little out of scope
here but would transition the UI of Netbeans from Swing to JavaFX based with
its own (css) theme paradigm be of value?
There is one important difference between Swing and JavaFX
On 5/31/21 9:11 AM, Geertjan Wielenga wrote:
Use it and keep the feedback coming.
I noticed the file 'discoclient.properties' in my home directory after
running the feature in NetBeans 12.4. It took a while to track down that
it was created by NetBeans. It contains:
#Sat May 29 10:32:55
On 1/2/21 3:56 PM, Tomáš Procházka wrote:
Having some form of guidance for reporter would be useful.
Please see:
INFRA-19430 - Add an issue description template
https://issues.apache.org/jira/browse/INFRA-19430
I'm not sure what's still holding up the change, but it may help for the
On 11/9/20 12:34 AM, Jakub Herkel wrote:
These tags are parts of Java Compiler API. So for Java 10+ there is a new
SUMMARY tag.
While we're at it, there's also a handy new Javadoc tag for system
properties, available in Java 12, that I've noticed is missing in NetBeans:
JEP draft:
On 10/21/20 10:01 PM, Laszlo Kishalmi wrote:
I just came up with the warning as I'm seriously thinking about somehow
moving the Snap out of Apache distribution as there is no legal way to
me to package everything into one working out of the box package.
For those of us on Ubuntu, the Snap
On 9/18/20 7:24 AM, Laszlo Kishalmi wrote:
One of the gray areas we have is the profiler support.
The NetBeans Profiler has been quite helpful in the past -- especially
for heap usage. Lately, though, I find the Async Profiler [1] to be the
best tool by far.
As an example of its utility,
On 5/10/20 1:43 AM, Neil C Smith wrote:
If tracing authorship of contributions is the only concern, there is
also the fact that the commit is not the only (or canonical) record of
this - there is the pull request and associated email trail that is
archived by ASF for this reason. Does this
On 4/28/20 3:58 PM, Brad Walker wrote:
So what are the collective thoughts and opinions about dropping SunStudio
support in Apache Netbeans?
For what it's worth, that's fine by me. My requirement is to be able to
compile and cross-compile C-language code for the Java Native Interface
on
On 12/7/19 1:32 PM, Eric Bresie wrote:
[javac]
C:\src\git\netbeans.eric\netbeans\nbbuild\build\langtools\src\jdk.compiler\share\classes\com\sun\tools\javac\platform\JDKPlatformProvider.java:120:
error: reference to newFileSystem is ambiguous
[javac]
On 11/18/19 11:39 AM, Emilian Bold wrote:
$ git fetch
$ git reset --hard / # Destructive!
I get it now. Thank you, Emilian. It's an interesting problem only if I
were also making changes to the code while testing, which I'm not. More
details here:
How do I recover/resynchronise after
in
the Commit field using just one entry in the history. For example:
- openjdk/jdk ---
$ git log -n 1 --format=full 0ed2c6c2957269d1342610b6d0382a2f8052f167
commit 0ed2c6c2957269d1342610b6d0382a2f8052f167
Author: John Neffenger
Commit: Phil Race
On 11/18/19 12:20 PM, Emilian Bold wrote:
You are angry. But you did ask if you are doing something wrong and
re-downloading the entire repository for 1 force modified commit is
not the way to go.
You're right. I'm sorry, Emilian. I was wrong to disregard your honest
answer and use it just to
On 11/18/19 11:39 AM, Emilian Bold wrote:
Or you could checkout HEAD~3 or some ancestor (which would be
netbeans:master) and then fetch the PR branch and re-checkout?
Or we could just stop doing forced pushes on pull requests under review.
I even think that's what our contributor guidelines
I'm continuing on the mailing list a discussion that started here:
Next time, though, could you add incremental commits ...
https://github.com/apache/netbeans/pull/1548#issuecomment-554833121
The Contributor Guidelines [1] state, "After submission (and certainly
after someone starts reviewing
On 11/17/19 10:39 AM, Emilian Bold wrote:
It seem impossible to notice what changed in netbeans_default_options
based on a diff since it's such a long line. Luckily things get
prepended, so it's not that hard in practice, but still...
I agree. It's also quite difficult to see what you have
On 11/17/19 2:06 AM, Dmitry Avtonomov wrote:
I did do that - there's a button to re-index maven repos afair.
If that's the button in the Options under Java > Maven, I think that
just pulls down the latest list from Maven Central again.
Instead, open the Services Window (Ctrl-5), expand
On 11/6/19 12:24 AM, Christian Lenz wrote:
Feel free to have a look/change it and maybe we can create a Infra ticket soon
for that improvement. I think there are not that much concerns about it so it
is good to go.
I opened the following issue with Apache Infrastructure.
INFRA-19430: Add an
On 11/10/19 7:40 AM, Christian Lenz wrote:
Sure, I mean they have separated fields if we can handle this under Apache, to
have suche a template, why not. I don’t want to exegerate it. Using a plain
text like others do in Github, for example here:
On 11/6/19 12:24 AM, Christian Lenz wrote:
Feel free to have a look/change it and maybe we can create a Infra ticket soon
for that improvement. I think there are not that much concerns about it so it
is good to go.
Thank you, Chris. What do you think about starting with the Java bug
report
On 11/3/19 1:58 AM, Thomas Zimmermann wrote:
until the maintainers find the time, would you mind testing what
problems remain after merging my PR?
I posted my test results as a comment on the pull request:
https://github.com/apache/netbeans/pull/1548#issuecomment-551237510
It's a *huge*
I notice that many new issues are created by copying and pasting the
entire UI Log or IDE Log (or both) from a NetBeans View Data error
report into the issue description field. The Jira formatting makes it
difficult to find the error and stack trace, and the large amount of
text, often
On 11/3/19 1:58 AM, Thomas Zimmermann wrote:
until the maintainers find the time, would you mind testing what
problems remain after merging my PR?
Sure, I'll give it a try. I should first remove the following extra
copies of the Javadoc and Sources in my local Maven cache, right?
On 11/2/19 7:51 AM, Laszlo Kishalmi wrote:
I'm on Ubuntu (not Debian), checked what is available for the platform.
They have the 8.1 platform as library there. Other than that, it is the
10.0 harness.
Right. Here's the full list:
Package netbeans
Ever since NetBeans 9, I've had problems trying to get the IDE to
recognize the JavaFX Javadoc and Sources. I identified eleven different
errors, summarized in the issue report below. I tested with the JavaFX
SDK, but the errors may happen with other libraries as well.
NETBEANS-3296:
On 10/17/19 2:35 PM, Glenn Holmer wrote:
It's much less subtle than that (see attachment: without on the left,
with on the right). Interestingly, I checked my anti-aliasing settings
in KDE, which were set to "Vendor Default". When I changed anti-aliasing
to "Enabled", hinting style "Medium",
On 10/17/19 8:49 AM, Laszlo Kishalmi wrote:
The stats says the majority of the Snap users are on Ubuntu 18.04 and
though I do not have stats on the used JDK, but I guess they are still
using either OpenJDK 1.8 or OpenJDK 11 LTS. So I feel for the majority
of the users who do not really care
On 10/17/19 4:39 AM, Glenn Holmer wrote:
However, I find that I still need to add
-J-Dawt.useSystemAAFontSettings=on
to make fonts look good in NetBeans (even under JDK 13). What would be
the correct incantation to start the installer that way as well?
Do you set that system property because
On 10/4/19 12:27 PM, Neil C Smith wrote:
After making sure both java -version and javac -version give 8,
cd into the netbeans directory and run `ant` as per
http://netbeans.apache.org/download/dev/index.html
Thank you, Neil. That prompted me to figure out how I got off to such a
bad start. It
On 10/4/19 9:42 AM, mlist wrote:
Even that results in the same failure.
I also had trouble building NetBeans, even though I've been building the
JDK and JavaFX for years. I am very new to the NetBeans source code,
though. Here's what I did to get it working. I'm on Ubuntu 16.04.6 LTS.
On 9/26/19 6:54 AM, Laszlo Kishalmi wrote:
As usual the Apache NetBeans 11.2-beta1 is available as Snap package on
the Snap store on the latest/edge channel.
I'm trying to test the beta version with a Snap parallel install, as
described below:
Parallel installs – test and run multiple
On 8/5/19 11:30 AM, Kenneth Fogel wrote:
Please suggest any part of NetBeans that makes it superior to Eclipse, IntelliJ
or Visual Studio Code.
I'm not familiar with Visual Studio Code, but I've used NetBeans,
Eclipse, and IntelliJ off and on for years. NetBeans is the only IDE
that makes
On 5/22/19 11:10 PM, Laszlo Kishalmi wrote:
This result makes the patch release accepted.
The followup events are:
* Moving the files from staging to the release area.
* The the new NBMs will be "overwritten" in the 11.0 release area
* Wait 24 hours for mirrors to puck up the new files.
54 matches
Mail list logo
