Re: GraalVM: Anyone still interested or do we reduce support to GraalJS or do we switch back to rhino?

[Svata Dedic]

Hi,

I have tried to follow Matthias' work but tried to retain as much of 
GraalVM/JS libraries as possible - see 
https://github.com/apache/netbeans/pull/7268


If I tested the change correctly, this change should run on GraalVMs 
with and without JS installed as well as non-polyglot / non-jvmci 
(thanks to Matthias' work) VMs as well.


Apologies for not stepping in earlier -- this entire thread ended up in 
my spam folder :-/ sorry.


-S.


On 10. 04. 24 20:07, Oliver Rettig wrote:

Thanks Matthias and Michael for your explainations. I am afraid I can not help
at the moment. I am not familar enough with this stuff but I think I have to
learn more about GraalVM-netbeans integration.

On 08.04.24 20:18, Matthias Bläsing wrote:

https://github.com/apache/netbeans/issues/6925

was ignored for the last 3 months.


not that it changes anything at this point but it was known much longer
than that.

The last update attempt https://github.com/apache/netbeans/pull/6369
bumped the version as much as possible but even the version it bumped it
to was was already EOL at that point.

The outdated graal situation was also tracked via
https://github.com/apache/netbeans/issues/4904, the last update only
bought a little more time.

GraalVM changed polyglot language features from being JDK extensions to
regular maven dependencies. The NB test setup expects everything to be
in the JDK - and it essentially needs all language extensions:

https://github.com/apache/netbeans/issues/6925#issuecomment-2003319844


this is btw a prime example of why I am always pushing to keep
dependencies up to date - the alternative is having to solve many
problems at the same time.


So I just tried to force version 24.0.0 into the current module
structure. I tried two approaches both failed. Maybe this is a trivial
problem for someone knowledgeable,

At some point graal changed versioning back to JDK versioning when it
jumped backwards. So I don't really know what JDK verison graal-sdk
24.0.0 is meant for.

Martin Entlicher contributed in that area before and knows both graal
and NB. Going to ping him via github / #7248

best regards,

-mbien


Greetings

Matthias



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [External] : [VOTE] Release Apache NetBeans VSCode extension 21.9.9

[Svata Dedic]

+1 (binding)

- SHA512 and GPG signatures checked
- LICENSE and NOTICE lok sane
- built cleanly with GraalVM for JDK21
- briefly tested with on Maven java projects

Tested on Ubuntu Linux 22.04, GraalVM for JDK21 21.0.2+13.1

-S.


On 10. 04. 24 13:31, Dusan Balek wrote:

+1 (binding)

Features tested on Linux. SHA check is OK.

Dusan

On 4/9/24 10:11 AM, Martin Balin wrote:

Dear community,
let's update the Apache NetBeans Language Server extension on VSCode 
Marketplace with improved version 21.9.9 mostly in LSP/VSCode code.

Vote candidate 1, source code artifact:
https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/21.9.9/apache-netbeans-java-21.9.9-sources.zip__;!!ACWV5N9M2RV99hQ!MfxRWeINprDk4MEisrUpvTOhinQwuUa9xdARMxyNBmRba9WHp6GGxZQuEiSxGf5Z9fCE3M9is1O-FJpw$
The primary voting artifact is the source built from branch 
‘vsnetbeans_2199`

SHA-512 sum is:
55be95e65d5b0ba9e7ccfc008facb15c3856cbbde26836348e8fc88c40dc275656c458e230121f085161634c93e3d24929ad4bf95ab28c150ecd929edb28ff0b
  apache-netbeans-java-21.9.9-sources.zip
and PGP signature:
https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/21.9.9/apache-netbeans-java-21.9.9-sources.zip.asc__;!!ACWV5N9M2RV99hQ!MfxRWeINprDk4MEisrUpvTOhinQwuUa9xdARMxyNBmRba9WHp6GGxZQuEiSxGf5Z9fCE3M9iszyghEZ0$

Binary artifacts were built by 
https://urldefense.com/v3/__https://ci-builds.apache.org/job/Netbeans/view/vscode/job/netbeans-vscode/2141/__;!!ACWV5N9M2RV99hQ!MfxRWeINprDk4MEisrUpvTOhinQwuUa9xdARMxyNBmRba9WHp6GGxZQuEiSxGf5Z9fCE3M9is_J2As9q$
In addition to the source ZIP file, we are also voting about 
convenience binary:

https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/21.9.9/apache-netbeans-java-21.9.9.vsix__;!!ACWV5N9M2RV99hQ!MfxRWeINprDk4MEisrUpvTOhinQwuUa9xdARMxyNBmRba9WHp6GGxZQuEiSxGf5Z9fCE3M9is2GDhrS6$

SHA-512 sum:
4ca0bccf85be8e9a2f8c44def11b0ad10b0f19c8620f7a44122fff71e781ffe5de69a4a0e85a2aafdcfd69a685ad89ac130a5e15a2660a02c95bacd51862970f
  apache-netbeans-java-21.9.9.vsix
PGP signature:
https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/21.9.9/apache-netbeans-java-21.9.9.vsix.asc__;!!ACWV5N9M2RV99hQ!MfxRWeINprDk4MEisrUpvTOhinQwuUa9xdARMxyNBmRba9WHp6GGxZQuEiSxGf5Z9fCE3M9is0xwfivX$

The binary has been produced by the same job run, from the same commit.
Build from source code artifact, unzip then cd into root of sources:
$ ant build
$ cd java/java.lsp.server
$ ant build-vscode-ext -Dvsix.version=21.9.9

This vote is going to be open at least 72 hours, vote with +1, 0, and 
-1 as usual. Please mark your vote with (binding) if you're an Apache 
NetBeans PMC member.


Thank you,
Martin Balín


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 21

[Svata Dedic]

[X] yes / +1
[ ] no / -1 (please justify -1)
[X] binding (member of PMC)

My vote is based on

[X] I have built and tested the source with OpenJDK 21 on Ubuntu Linux 
22.04.1 (required)
[X] I have tested the binary zip with Oracle JDK 17.0.8 LTS on Ubuntu 
Linux 22.04.1
[X] I have tested the DEB installer(s) with Oracle JDK 17.0.8 LTS on 
Ubuntu Linux 22.04.1

[ ] I have tested the Maven artefacts
[X] I have tested the VSCode extension

Additional info (optional) - any specifics on what you've tested:

The DEPENDENCIES produced during locally run "ant build" differs from 
the DEPENDENCIES in the convenience binary. The difference is:


--- DEPENDENCIES2024-02-18 19:29:42.0 +0100
+++ ../../DEPENDENCIES  2024-02-18 19:17:50.0 +0100
@@ -420,8 +420,6 @@
 From: Gradle Inc.
   - Gradle Tooling API: Gradle Tooling API (https://gradle.org/)
 License: Apache Version 2.0 
(http://www.apache.org/licenses/LICENSE-2.0.txt)

-  - Gradle Wrapper: Gradle Wrapper (https://gradle.org/)
-License: Apache Version 2.0 
(http://www.apache.org/licenses/LICENSE-2.0.txt)


 From: Hamcrest
   - Hamcrest: Provides a library of matcher objects 
(http://search.maven.org/#artifactdetails|org.hamcrest|hamcrest-core|1.3|jar)


the convenience binary DEPENDENCIES file lacks an entry for gradle 
wrapper present in local build from the voted-on sources. But the 
wrapper jar does not seem to be distributed, so I'll file this as an 
issue for the buildscripts.


-Svata

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans VSCode extension 20.0.301 vote candidate 2

[Svata Dedic]

+1 (binding)

- SHA512 and GPG signatures OK
- builds cleanly (JDK17, Ubuntu linux 22.04)
- license, notices present
- tested on JDK17 + JDK21 Ubuntu Linux

-Svata

On 11. 01. 24 11:35, Martin Balin wrote:

Hello,
Yesterday the issue was discovered in VSNetBeans 20.0.301 voting candidate 1 
and fixed https://github.com/apache/netbeans/pull/6941 and tested.

We have new voting candidate 2:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/20.0.301/

The primary voting artifact is the source 
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/20.0.301/apache-netbeans-java-20.0.301-sources.zip
built from branch vsnetbeans_2003

SHA-512 sum is:
cb705cdee43eaee192605a5a5a2e21754df921eb99819d8a4bbe733ab3d60c9eb21d01f61bb272c6aeba6b1e53004ac166dce85412f0d60e5678a28658bb2463
 apache-netbeans-java-20.0.301-sources.zip

PGP Signature is 
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/20.0.301/apache-netbeans-java-20.0.301-sources.zip.asc

Binary artifacts were built by 
https://ci-builds.apache.org/job/Netbeans/view/vscode/job/netbeans-vscode/2030/

In addition to the source ZIP file, we are also voting about convenience binary:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/20.0.301/apache-netbeans-java-20.0.301.vsix

SHA-512 sum is:
c7c5d46dffda689fdef16cae0639965a4021c74f0a21eb5b9e5d0a19d75fa722aa415f749359760c11e424c62fe8b0357faf8e03d1690b0fc866115db8ad5859
 apache-netbeans-java-20.0.301.vsix

PGP signature: 
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/20.0.301/apache-netbeans-java-20.0.301.vsix.asc

The binary has been produced by the same job run, from the same commit.
Build from source code artifact, unzip then cd into root of sources:
$ ant build
$ cd java/java.lsp.server
$ ant build-vscode-ext -Dvsix.version=20.0.301

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as 
usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC 
member.

Thank you and sorry for rebuild,
Martin Balín



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Project dependencies - add/remove ability

[Svata Dedic]

Will check, thanks.

Anything is possible until the API matures and goes public, tentative 
timeframe is NB23. I am willing to adapt 'early adopter' code, we now 
need for Oracle exensions, of course.


-S.

On 18. 12. 23 13:04, Neil C Smith wrote:

On Wed, 29 Nov 2023 at 19:24, Svata Dedic  wrote:

I am working (finishing) on an extension of (still private) Project
Dependency API that would allow to *add* dependency to a project (and
also remove). This is a change that will span both Maven and Gradle
modules, so I thought I'll put a note in advance, but PR will be landing
shortly in Github.


Just catching up on emails having been away.

I like the sound of this API, but if the base API is to be in the IDE
cluster, it might be nice to build around an artifact specification
that is less tied to Gradle / Maven conventions and usable for other
languages including JS and Rust?

I've mentioned before in another context, but I do like PackageURL,
and it's getting more and more adoption.
https://github.com/package-url/purl-spec

You can see PackageURLs for Maven at the top of every page in Maven
Central search - eg. yellow highlighted at
https://central.sonatype.com/artifact/org.netbeans.api/org-openide-util-lookup

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Project dependencies - add/remove ability

[Svata Dedic]

On 01. 12. 23 16:22, Michael Bien wrote:


is this about a convenience action which:

Possibly, but it's mainly about a convenience API that allows (other) 
modules to do that.


Currently a "technology" module (micronaut, spring, oracle cloud) that 
would like to introduce an artifact to the build, must check

- project type (say gradle/maven)
- based on project type:
maven: use Maven API (ModelUtils.checkModelDependency) to add a 
 child

gradle: do textual edit of build.gradle

It's rather peculiar to make such actions from a "technology" module 
that does not directly depend on Maven and Gradle internals, and of 
course does not want to reimplement it.


In addition, I'd like to conform to refactoring API that computes the 
chane first, then allows to apply it, where the Maven API operation will 
directly mutate the POM document.


The result should be nothing more (from API perspective) than add/remove 
(artifact) dependency, later maybe update (version change, simple excludes).


Help would be appreciated in thinking out how to possibly integrate sets 
of maven/gradle artifact references into Library concept of Java project 
common API ... it seems the current impl assumes .jars are present.


-S.

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Project dependencies - add/remove ability

[Svata Dedic]

On 01. 12. 23 15:53, Michael Bien wrote:


Sounds like a useful feature in some situations. The impl details will 
be interesting though, since I am sure someone will try to add a maven 
project to a gradle project or vise versa.


The feature should be primarily used to add artifact (e.g. 
io-micronaut:micronaut-router:4.1.2) dependencies. But yes, it's 
possible to describe a project on local hard disk ... which will most 
probably cause an "unsupported" exception.


It is only IMHO safe to add a subproject in the same multiproject in 
gradle (not in maven) as a dependency. Maven relies entirely on 
artifacts (?).
I could imagine that the implementation would attempt to extract output 
artifact's GAV from the identified project and use that.


-S.


best regards && looking forward to try the feature,

-mbien




-S.


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Project dependencies - add/remove ability

[Svata Dedic]

On 01. 12. 23 3:29, Michael Bien wrote:
And why is it not sufficient to (mvn) install the dependency into the 
local repo, and then depend on it the regular way?




The API is just an abstraction implemented by project system. So with 
Maven project, it will be implemented as an edit into pom.xml. For 
gradle, build.gradle will be changed. Similar to current (private) 
Dependency API query, which just extracts project dependencies from 
pom/build.gradle and presents it. No parallel build system or additional 
metadata.


-S.


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Project dependencies - add/remove ability

[Svata Dedic]

Hi,

I am working (finishing) on an extension of (still private) Project 
Dependency API that would allow to *add* dependency to a project (and 
also remove). This is a change that will span both Maven and Gradle 
modules, so I thought I'll put a note in advance, but PR will be landing 
shortly in Github.


The reason is the ability to add technology libraries, i.e. add 
monitoring to an application, add JDBC driver etc, which all requires 
(among other things) to add a set of artifact(s) to a project. I would 
like to have that ability for our company product, primarily, but the 
API to do _basic_ dependency changes in both major supported build 
systems. Only basic operations (add, remove) and only projects that use 
some artifact repositories are considered (maven, gradle, possibly mx), 
not ant-based projects.


In order to get a reasonable API outcome, I decided to work jointly with 
Refactoring API and LSP API: the changes are best described as text 
changes to project files - and in case of our LSP client use-case, 
perform them. And rectoring API allows to commit() them in NetBeans 
case. Note that while *java* refactoring API describes text 
modifications in its result, the generic refactoring API does not. It 
does not seem beneficial to invent yet another text-changes description 
now, when LSP APIs are here, and basically do what's needed (even for Java).


Gradle implementation: I do not want to pollute basic gradle modules 
more, so I decided to create a small java.gradle.dependencies module; I 
am thinking about migrating the dependencies part out of java.gradle 
module to the new one, which should clean up java.gradle module a bit.


Maven implementation: For Maven, I'd work this into maven.hints. All 
dependencies are there except refactoring.api.


Some more steps are IMHO needed until the dependency API is mature 
enough to get out of private:
- the Scope is not designed well; it was anticipated (and that's why the 
API is not public) the introduction of modifications shed a little more 
light on it. I'll be working on that, keeping Micronaut support module 
as a early adopter (with necessary updates).
- the Dependency children ought to be generated lazily; this gives the 
client the option not to traverse / expand subtrees for dependencies 
already seen. But some clients need exhaustive traversal.

- improve the interaction with BOMs

Cheers,
-Svata

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Module-wide @ServiceProvider/@MimeRegistration?

[Svata Dedic]

Can you invent your own MIME type for your file content (= is it some 
special - purpose JSON/XML) ? If so, then you could use (for XML) 
composed mime type text/javier-content+xml
The editor pane will inherit everything registered for plain XML + 
you'll be able to register specific services for just the 
text/javier-content+xml


Similarly, you can invent application/javier-content+json for your JSON 
content.


-S.

On 08. 10. 23 18:28, Javier Llorente wrote:

Hello,

I was wondering if it is possible to register a module-wide @ServiceProvider/
@MimeRegistration.

I want links found in a JSON/XML displayed by my module TopComponent's
JEditorPane to be opened by another instance of the same TopComponent. For
that purpose, I have another class that extends HtmlBrowser.URLDisplayer.
However, I don't want to be responsible for opening all links in NetBeans (ie:
javadocs).

Implementing a HyperlinkProviderExt (and registering MIME types "text/
plain" and "text/xml") improves the situation a bit; javadocs links are now
opened by an external browser but links found in any plain text or XML file are
also opened by my module.

Any suggestions?

Thanks,



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans VSCode extension 19.0.301

[Svata Dedic]

Hi,

+1 (binding)

- LICENSE, NOTICE checked
- sha sums and signatures OK
- build OK on Java17.0.3.1 / Ubuntu 22.04
- the vsix seems to run OK in basic scenarios

Tested basic editing, completion, build + run on a simple Micronaut 
4.0.3 project, on Ubuntu Linux 22.04


-Svata

On 15. 09. 23 10:50, Martin Balin wrote:

Dear community,
let's update the Apache NetBeans Language Server extension on VSCode 
Marketplace with improved version 19.0.301 mostly in LSP/VSCode code.
Vote candidate 2, source code artifact fixed.
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/19.0.301/

The primary voting artifact is the source
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/19.0.301/apache-netbeans-java-19.0.301-source.zip
built from branch ‘vsnetbeans_1903`
SHA-512 sum is:

a666eac24aca7bac9a2a4b0812db241b8ea1dd533a2ecd41d44840e51e55ae0a492a0cb1b7621c11093496edae7b80ec5230de9658dbea3ef3ab41a57e3ec912
 apache-netbeans-java-19.0.301-source.zip

and PGP signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/19.0.301/apache-netbeans-java-19.0.301-source.zip.asc

Binary artifacts were built by 
https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/1841/

In addition to the source ZIP file, we are also voting about convenience binary:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/19.0.301/apache-netbeans-java-19.0.301.vsix

SHA-512 sum:
e3129f21d0b91274e82906ae14d3f7153974372d0df74379caa04ee4c1f4b0e06f0c0b3a846a26d7bfd5d3cba733823ae307af17fea6833bef58a3cbac4c5334
  apache-netbeans-java-19.0.301.vsix
PGP signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/19.0.301/apache-netbeans-java-19.0.301.vsix.asc

The binary has been produced by the same job run, from the same commit.
Build from source code artifact, unzip then cd into root of sources:
$ ant build
$ cd java/java.lsp.server
$ ant build-vscode-ext -Dvsix.version=19.0.301

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as 
usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC 
member.

Thank you,
Martin Balín



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 19

[Svata Dedic]

[X] yes / +1
[ ] no / -1 (please justify -1)
[X] binding (member of PMC)

My vote is based on

[X] I have built and tested the source with Oracle JDK 17 on Ubuntu 
22.04 (required)
[X] I have tested the binary zip with Oracle JDK 17 and Oracle JDK 21 
(prerelease) on Ubuntu 22.04

[X] I have tested the DEB installer(s) with JDK 17 on Ubunu 22.04
[ ] I have tested the Maven artefacts
[X] I have tested the VSCode extension

-Svata


On 29. 08. 23 11:45, Neil C Smith wrote:

[ ] yes / +1
[ ] no / -1 (please justify -1)
[ ] binding (member of PMC)

My vote is based on

[ ] I have built and tested the source with  on  (required)
[ ] I have tested the binary zip with  on 
[ ] I have tested the  installer(s) with  on 
[ ] I have tested the Maven artefacts
[ ] I have tested the VSCode extension

Additional info (optional) - any specifics on what you've tested

--


Thank you to all contributors for all your hard work!

Apache NetBeans release team

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [RELEASES] Preparing for 18-rc3

[Svata Dedic]

Pls. also consider the memory settings fix here: 
https://github.com/apache/netbeans/pull/5914


-S.

On 09. 05. 23 10:08, Neil C Smith wrote:

On Fri, 5 May 2023 at 10:11, Neil C Smith  wrote:


On Tue, 2 May 2023 at 16:09, Neil C Smith  wrote:

We don't have much in delivery for 18-rc3 yet, and are still waiting
on #5842 to be ready for merging.


Well, https://github.com/apache/netbeans/pull/5842 was merged and we
have consistent test failures in delivery since.  A few other tests
also seem to have become unstable - things that were routinely passing
in merges to delivery prior are sometimes failing.  It's hard to be
sure whether they're definitely related.

...

We'll need to decide what to do, and when to trigger 18-rc3 - would
still like to do that early next week as we've already delayed it.  If
this gets reverted from 18-rc3 then we'll have to live without it in
NB18.  Is it potentially too invasive a fix so late in the release
cycle anyway?


So, no comment from Martin on that, but Svata's update PR is merged -
https://github.com/apache/netbeans/pull/5924

I'm going to let all the branch and sync tests run before merging the
other pending PRs.

All being well, should be able to trigger rc3 to be available tomorrow.

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [DISCUSS] disable remote index extraction by default [NB18]

[Svata Dedic]

Interesting stats, but

Apache-NetBeans-17-bin-windows-x64.exe  643,458 downloads,
netbeans-17-bin.zip 130,456 Downloads

the files being +- the same size.

but the traffic says:

netbeans-17-bin.zip 24,873,400,441,109
Apache-NetBeans-17-bin-windows-x64.exe 539,363,119,735

...so the much less demanded file (comparable size) provides traffic 
larger by 2 orders of magnitude. Something is fishy here.


On 18. 04. 23 10:43, Neil C Smith wrote:


* or 0.5 million unique IPs, so probably somewhere in between - access
to stats for people with Apache account at
https://logging1-he-de.apache.org/stats/





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans VSCode Extension 17.0.301

[Svata Dedic]

+1 (binding)

- sha + signatures checked
- builds cleanly on JDK19
- basic edit/compile cycle seems to work fine on a simple sample project.

Tested on Ubuntu 22.04 / Oracle JDK 17 + 19

-S.

On 11. 04. 23 17:58, Martin Balin wrote:

Dear community,
let's update the Apache NetBeans Language Server extension on VSCode 
Marketplace with improved version 17.0.301 mostly in LSP/VSCode code.
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/17.0.301/ 


The primary voting artifact is the source
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/17.0.301/apache-netbeans-java-17.0.301-source.zip
 

built from branch ‘vsnetbeans_1703`
SHA-512 sum is:
72ea52229fc23988643e98538d60af076ac0ae02cf68f6f7ec669aec9ab4bd552c5912a6301e5c63df7edd917b92423c2b3c646e976af67f2da06a4798eea1a4
  apache-netbeans-java-17.0.301-source.zip
and PGP signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/17.0.301/apache-netbeans-java-17.0.301-source.zip.asc

Binary artifacts were built by 
https://ci-builds.apache.org/job/Netbeans/job/vsnetbeans_1703/8/

Use following commands to build your own 17.0.301 VSIX binary:

tmp$ unzip apache-netbeans-java-17.0.301-source.zip
tmp$ ant build
tmp$ cd java/java.lsp.server
tmp$ ant build-vscode-ext -Dvsix.version=17.0.301 -D3rdparty.modules=none

In addition to the source ZIP file, we are also voting about convenience binary:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/17.0.301/apache-netbeans-java-17.0.301.vsix

SHA-512 sum:
2adf506c3c4e37383d24f1210128137c928ab05b4665bcb82e89dab2eccc30f548cad385e5110b753591897ca7956c1bc7b30cb4edf3361456aca0ca589470a7
  apache-netbeans-java-17.0.301.vsix
PGP signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/17.0.301/apache-netbeans-java-17.0.301.vsix.asc

The binary has been produced by the same job run #8, from the same commit.

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as 
usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC 
member.

Thank you,
Martin Balín



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [Lazy Consensus] Minimum JDK build and run policy (dropping JDK 8)

[Svata Dedic]

On 12. 04. 23 6:04, László Kishalmi wrote:

Well, your proposal is actually putting additional work both on who wants
to move forward and who wants to support Java 8 runtime. Also how would it
look like wne Java 17, 21 would be the base? I would like to avoid having
codes in the ide like this one:
https://github.com/apache/netbeans/blob/7f8dfdeb60ce3bec5554fc19ddb40fac0388d885/extide/gradle/netbeans-gradle-tooling/src/main/java/org/netbeans/modules/gradle/tooling/NbProjectInfoBuilder.java#L1090


Disclaimer: not advocating ob the vote result or the voted-on questions, 
just reacting to a specific technical issue.


I am sure this can be done more gratitiously. For example, if we make a 
chain of processors, that declare themselves to be usable for a version 
range, to process several 'well known' entities to Map info that is then 
merged ...
... it could look a way better and the "old" processors (if we talk 
about NB modular code in general, not the gradle plugin) could be even 
separated to optional modules that won't be distributed by default.
I've already thought about something along those lines with the gradle 
plugin, but it did not seem that important. The fathest in that 
direction was the GradleInternalAdapter.Gradle76().


But it requires some degree of cooperation, which seem to be rejected 
upfront.


Even code beautification, like (for example) using JDK 9+ 
java.util.Map.of() can be accommodated (you know, we have bytecode 
patching classloaders, that can do a lot of magic, like diverting the 
code to an utility method shipped with NB) - again all the magic 
separated into modules that need not load in the first place (similar to 
unless you run an old module, filesystem-compat8 won't load), or even 
distributed with the standard binary.


But again, that assumes some degree of honest cooperation/respect from 
the progressive majority - but given the past communication, throwing 
obstacles in the way could easily happen, manifested in declaring the 
effort "DeadBeans" by a PMC member.


What's funny is that similar tricks could allow us to modernize the 
*source code* to the newest supported JDK (LTS) while gracefuly 
degrading for the rest of supported JDKs (yes, without the hated 
Frgaal), whatever LTS-1 or LTS-2 policy is in the place. But it's too 
easy and self-pleasing to just laugh.


-S.


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: AW: [Lazy Consensus] Minimum JDK build and run policy (dropping JDK 8)

[Svata Dedic]

On 10. 04. 23 19:35, Scott Palmer wrote:

Note that the one example we have been given so far of "Microchip IDE", if
it is what I think it is "MPLAB X IDE" (
https://www.microchip.com/en-us/tools-resources/develop/mplab-x-ide), then
it seems to have Windows 10, Ubuntu 16.04, macOs 10.15 as minimums.  Java
11 runs on those platforms, and a JRE has been distributed with the product
since 5.40.  So I continue to search for a real case for Java 8 support.


Minor correction: the actually distributed JRE is:
	OpenJDK Runtime Environment (Zulu 8.64.0.19-CA-linux64) (build 
1.8.0_345-b01)


-S.


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: AW: [Lazy Consensus] Minimum JDK build and run policy (dropping JDK 8)

[Svata Dedic]

On 10. 04. 23 5:40, Laszlo Kishalmi wrote:


It is also being said that "The IDE will continue to support users 
developing projects for/with JDK 8, for as long as nb-javac and other 
dependencies allow." . I think the team would understand if we keep our 
Gradle Tooling library on JDK8 level for the foreseeable future.




Correction: I am not advocating that NetBeans IDE supports JDK8 target 
for the compilation - that I assumed for granted from the previous 
discussion.


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 others.


Changing the _runtime_ requirements for NetBeans platform affects 
application builders - they are often being forgotten in discussions.


Maintenance releases running on JDK8 are not possible, if the core parts 
of NetBeans start to extensively use JDK11+ APIs 'just for joy from the 
new'.


-S.



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: AW: [Lazy Consensus] Minimum JDK build and run policy (dropping JDK 8)

[Svata Dedic]

Please remember that the published proposal not only covered JDK8's 
fate, which we argue about right now, but also the idea to drop JDK11 in 
2024. So take my


* -1 (at the moment) for JDK8 phase out with NB19;
* and ANOTHER -1 to the JDK11 plans as presented in this thread (but 
that should be discussed separately anyway, not hidden in dropping JDK8 
thread)


Summary:
- I do not think that dropping JDK8 now is a good idea
- I do not think that sufficient relevant data for the decision was 
collected; I think that we did not even start to collect it.

- I do think we can find and reach a reasonable compromise.
- I propose some action items to make the decision better informed and 
based.
- I offer coding help with compatibility bridges, analysis and/or 
migration of the code.


TL;DR:

I'd like to offer some coding support to retain JDK8 as well - but 
(which IMHO did not happened really during past heated exchanges) need 
to agree on support scope before committing. I'd like to emphasize that 
*runtime* compatibility should be treated separately from *development* 
environment requirements. I would also (now) ask to restrict from 
advocating language goodies - as there are different options to achieve 
that, not necessarily requiring the change of the codebase runtime 
requirements.


I will quite from Ernie Rael's post (quoting stats from 2022):

even though Java 11 had been available for more than a year. Since
then, the balance has shifted between these two LTS release versions.
More than 48% of applications are now using Java 11 in production (up
from 11.11% in 2020) with Java 8 a close second, capturing 46.45% of
applications using the version in production.


There was an idea to basically tell users with requirements for older 
JDKs (now 8, 11 in 2024) they should use the last released platform 
(NB18) that supports their environment. This really mean to *abandon the 
users*, as they will not receive any new features or bugfixes. While 
maintenance effort surely requires work if we still support JDK8, 
porting features (albeit selectively) back to old platform requires even 
usually much more effort. The offer that platform users do that for us 
may seem formally correct, but in reality it requires deep knowledge of 
many parts of the IDE, not just knowledge of the 'system parts' affected 
by JDK differences. Exemplified on myself, although I could be able to 
assist to develop bridges for different JDK versions for features 
determined as necessary for the new codebase (with possible graceful 
degradation or function disable on old runtimes), I sincerely doubt I 
would be able to assist with backporting a user-facing feature. I 
believe this is a general case, as the 'domain knowledge' is far more 
scarce than the knowledge of system libraries.
So the seemingly positive approach, it turns out to be rather offensive 
in its implications to platform users, which is an outcome I do not like.


This could be eventually barely acceptable in case of JDK8, I do not see 
reasonable to set minimum JDK to 11 at all. The reason is that while 
JDK8 has support cycle of 11 years (2015 released, 2026 EOLed by RH / 
IBM), JDK 11 has a super short shorter cycle despite being LTS (2021-24) 
and JDK17 just 6 years (2021-2027). From this perspective, forcing the 
users to upgrade JDK 8 > JDK 11 by NB19 in 2023, and then again to JDK17 
by (even if ve move OUR deadlines) right during 2024 given the *upstream 
support ceases for 11* in 10/2024, is ... a very bad idea.


I've read the thread again, and I must think there's a lot of heated 
feelings, but very little of hard data. Let me say I understand (some 
of) the urge to upgrade and I'd like myself to be able to use some 
JDK11+ APIs in NB platform (but also pretty sure that other upgrade 
proponents are interested in *different* sets of APIs). But there are 
different perspectives - so important IMHO that I am willing to offer my 
personal time to support older JDKs, too.


In fact, *we  all* (IMHO and me explicitly included) never went as far 
as to write down the fact and consolidate the info to get the overall 
picture. The consolidated list is important so the maintenance burden 
could become more obvious even to nonbelievers - or, in other hand, the 
JDK8 preservation may turn not such high barrier, and JDK11 features not 
as critical to outweigh the JDK8 drop for the whole codebase. We do not 
have AFAIK such an overview. We did not even start to collect such a 
list, instead of that, the general tone of the discussion was 
exagerrated "march forward, kill all the old stuff, let the (IT) God 
sort it later".


Also note that we can *lower* the guarantees: e.g. not run JDK8 tests 
every commit, to reduce the resource consumption for the test matrix. 
But such negotiation didn't really happen. So far, the major +1s were 
not based on technical details, but rather on emotions or feelings - 
"new is good", or at least the thread reads.


First of all, the 

Re: Compatibility with JDK 8: Shift work to people wanting it (was: Re: Lets talk about JDK 8 (new year edition))

[Svata Dedic]

Speaking for myself personally:

I'd like to step in the discussion, as I see the rapid movement between 
JDK versions that is even increasing with increased frequency of JDK 
releases (with only limited features that make a real difference for NB 
development) as dangerous - but I still lag behind as I am trying to 
read the whole thread.


In my current state of  mind / evaluation of the issue  I'd give -0.5 to 
JDK8 drop and -infinity to JDK11 drop next year. I'll try to catch up 
with the conversation during till next week - the stated position needs 
more elaborate explanation, but I don't want to repeat others (too 
much). Thanks.


-Svata

On 16. 03. 23 12:23, Neil C Smith wrote:

Hi Matthias,

On Sun, 12 Feb 2023 at 22:22, Neil C Smith  wrote:

On Sun, 12 Feb 2023, 19:11 Matthias Bläsing, 
 wrote:


Hi,

Am Freitag, dem 10.02.2023 um 10:12 + schrieb Neil C Smith:

On Thu, 9 Feb 2023 at 19:02, Matthias Bläsing 
 wrote:

- commit to make NetBeans runnable on JDK LTS -1
- build with JDK LTS -1
- be able to be build with the current JDK


+1 as long as that includes the platform.

That is what I suggested in the other thread (I don't see why we need
multiple threads incidentally!)

An LTS-1 strategy seems closest to how NetBeans used to function -
major-1, in a time when it also had more development resources?

Let's also be clear, though, that adopting an LTS-1 strategy means
dropping JDK 11 support either in our first release after JDK 21, or
the first after JDK 22 - so latest May 2024.


why would we do that? I said _runnable_ and _buildable_. As long as the
current JDK support the target release I did not exclude that.



In which case I don't understand what you mean by committing to make NetBeans 
buildable and runnable on LTS-1? That to me means dropping the commitment to 
JDK 11 when it becomes LTS-2.


I'd still really like to see us make some movement here before the
next release freeze in a month.

I'd still like to understand whether we're saying the same or
different things about adopting an LTS-1 strategy here?

Thanks,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 17

[Svata Dedic]

[X] yes / +1
[ ] no / -1 (please justify -1)
[X] binding (member of PMC)

My vote is based on

[X] I have built and tested the source with Oracle JDK 11.0.5 and 19.0.1 
on Ubuntu 22.04.1
[X] I have tested the binary zip with Oracle JDK 11.0.5 and GraalVM CE 
22.3.1 on Ubuntu 22.04.1

[X] I have tested the DEB installer with  on Ubuntu 22.04.1
[X] I have tested the Win installer with 11.0.12 on Windows 10
[ ] I have tested the Maven artefacts
[X] I have tested the VSCode extension on JDK 11.0.5 and 19.0.1 on 
Ubuntu 22.04.1


Additional info (optional) - any specifics on what you've tested

- debugger.jpda.truffle does not compile with GraalVM 19 (truffle 
library incompatibility). Compiles OK on GraalVM 17 or any non-GraalVM JDK


- vscode extension needs an update, see 
https://github.com/apache/netbeans/pull/5503. Does not affect mainline 
use-cases without OCI cloud.



On 16. 02. 23 16:13, Neil C Smith wrote:



Voting requirements

Before voting +1 you are required to download the signed source code
package, compile it as provided, and test the resulting executable on
your own platform, along with also verifying that the package meets
the requirements of the ASF policy on releases -
http://www.apache.org/legal/release-policy.html#management

In particular, you should (at least) follow these steps.

1. Download the artefact to be voted on and unzip it.
2. Check that the artefact does not contain any jar files (there are
branding folders with the name *.jar).
3. Verify the cryptographic signatures, the NOTICE and LICENSE file
4. Build it using the README provided by the artefact.
5. Look in nbbuild/netbeans for the NetBeans installation created by
the build process and try running it.

In addition to checking the sources, you may check the associated
convenience binary zip, installers, nbms and maven staging at the links
above. You are not expected to check every convenience binary.

As well as checking any artefact functions correctly, you
should check that it has been correctly signed by a PMC member, and
that the source being voted on is sufficient to build the relevant
binary.

This vote is going to be open at least 72 hours, vote with +1, 0, and
-1 as usual. (Please justify -1)

Please mark your vote as binding only if you're an Apache NetBeans
PMC member to help with voting admin.

Only respond if you are going to vote - this is NOT a discussion
thread.

Apache NetBeans 17 will be released if and when this vote passes.

---

Voting template

Please copy and paste the answer form below into your email. Fill the
checkboxes as appropriate (eg. [X]). Replace ,  and  as
appropriate.

-- Answer form 

[ ] yes / +1
[ ] no / -1 (please justify -1)
[ ] binding (member of PMC)

My vote is based on

[ ] I have built and tested the source with  on  (required)
[ ] I have tested the binary zip with  on 
[ ] I have tested the  installer(s) with  on 
[ ] I have tested the Maven artefacts
[ ] I have tested the VSCode extension

Additional info (optional) - any specifics on what you've tested

--


Thank you to all contributors for all your hard work!

Apache NetBeans release team

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Launchers enhancement: extra clusters

[Svata Dedic]

On 17. 02. 23 11:17, Neil C Smith wrote:

Definitely in favour of the command line parameter.  But, does it
absolutely need launcher changes to achieve it?  Not achievable by
parsing the command line argument in MainImpl like you're doing with
the system property?


The thing is that the --clusters (+netbeans_extra_clusters config 
option) is processed into "netbeans.dirs" system property by 
launcher(s). That property is read from many places, sadly and is 
public/documented (arch.xml) alghouth as "friend" category.


The implementation could possibly read "--add-clusters" at the very 
start of the bootstrap, using custom code as we need (IMHO) to patch the 
combined value back as soon as possible so that even CLIHandlers observe 
the correct value. No existing code is really prepared for this value to 
be mutable.


That's partially why I/Dusan considered the quickfix just temporary: it 
patches the system property back.




A mirroring subtractive cluster parameter might be useful?

I could imagine it could be - but would be also more tough i.e. we can 
run into path normalization + comparison, in win / shellscript.



Q4: are there other pending issues that could be addressed in the new
launcher release ? I've searched GH issues and didn't found much.

[...]
Would you file those as issues ?

-S.


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Launchers enhancement: extra clusters

[Svata Dedic]

Hi, all,

This e-mail is to solicit possible comments/opinions to the approach ... 
and to get some help as I don't seem to have enough info about the 
launcher release process :)


I'd like to add a small enhancements to the binary launchers, as a 
follow-up to https://github.com/apache/netbeans/pull/5350 that somehow 
has to land in the master and future netbeans releases.


I would like to add --add-clusters commandline option with a path-list 
of cluster based directories as a parameter, that allows to add 
additional code to the NB IDE (vsnetbeans server) runtime temporarily, 
without changing the configuration files.
The option would be *additive* with contents of the current 
netbeans_extra_clusters config file value and netbeans.conf 
configuration file.


Reasons for the change:
Currently NB launchers read netbeans.clusters (or app.clusters) and 
netbeans.conf files for list of clusters in NB installation or possible 
other clusters respectively. But both files are static. In the 
"vsnetbeans" headless LSP server case, the NB process is started in the 
background, and should respect the current _runtime_ environment of the 
LSP client. Specifically in vscode, the extensions can be 
enabled/disabled per workspace, and there can be multiple NetBeans 
servers running for different workspace configurations. But the 
extension's code - that is configuration files like netbeans.clusters 
and netbeans.conf - remain on a shared location. A command-line argument 
allows the wrapper (initiating client) to launch NB process and pass 
apropriate requirements to it.


An alternative would be, for example, a system property, as in the 
remporary fix (https://github.com/apache/netbeans/pull/5350). We 
discussed this approach with Dusan Balek and decided that a commandline 
parameter would be more appropriate.


Now the questions come:

Q1: is there a strong opinion AGAINST using commandline parameter - and 
to use rather a system property (or other technique) ? Please elaborate.


Q2: what's the release process for the binary launchers (since they need 
to be published to maven central) ?
Q3: what is the versioning scheme (launchers released in Nov 2022  are 
versioned 12.5) for the launchers artifact ?


Q4: are there other pending issues that could be addressed in the new 
launcher release ? I've searched GH issues and didn't found much.


Thanks,
-Svata

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

NBLS issue with NB17

[Svata Dedic]

[resend, from gmail address; pls. ignore duplicates]

Hi, Neil, and all,

again I am causing trouble with the release. Approx an hour ago, a 
colleague tested the upcoming release on Windows and found out that DB 
drivers (from other VSCode extension on Marketplace) are not getting 
injected into NBLS as they should.


Mea maxima culpa ... it seems that hotfix 
https://github.com/apache/netbeans/pull/5350/commits/5f137d0a9f2bef979ec26946cf88b4cf8d199dbb 
did not make it into the NB17 branch.


I forgot about that task - since the plan was (see the issue) to change 
*launchers* to have an extra parameter and use that.


I ask you to consider this hotfix to be applied on branch release170 and 
creating a RC4 with that hotfix ... plus apply to the master as a 
temporary solution until I made the appropriate launcher changes (will 
do as a top priority).


The linked patch is already tested as a part of VSNetBeans 1603 and 
should be safe for NetBeans IDE.


-Svata

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans VSCode Extension 16.0.301 voting candidate 2

[Svata Dedic]

Hi,

+1 (binding)

- SHA + GPG checked
- builds cleanly
- LICENSE present, NOTICE looks sane
- tested basic editing, audit,
- tested proxy (nonproxy) detection
- tested deploy of micronaut (old and new), springboot

all seems good.

-S.

On 31. 01. 23 19:51, Martin Balin wrote:

Dear community,

Voting candidate 2 for Apache NetBeans Language Server extension is available 
with one fix over the build (#1446) sent earlier today.
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/16.0.301/

The primary voting artifact is the source
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/16.0.301/apache-netbeans-java-16.0.301-source.zip
built from branch ‘vsnetbeans_1603`
SHA-512 sum is:
f2e5a54ad2692b1cfd8d13e84bdd47e69593b3cb51f979b76faea4aa906eafd1e43e48c18721376843d4659dcb90e5cd2ca05282b86bbff37dcc738353d2
  apache-netbeans-java-16.0.301-source.zip
and PGP signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/16.0.301/apache-netbeans-java-16.0.301-source.zip.asc

Binary artifacts were built by 
https://ci-builds.apache.org/job/Netbeans/view/vscode/job/netbeans-vscode/1448/

Use following commands to build your own 16.0.301 VSIX binary:

tmp$ unzip apache-netbeans-java-16.0.301-source.zip
tmp$ ant build
tmp$ cd java/java.lsp.server
tmp$ ant build-vscode-ext -Dvsix.version=16.0.301 -D3rdparty.modules=none

In addition to the source ZIP file, we are also voting about convenience binary:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/16.0.301/apache-netbeans-java-16.0.301.vsix
SHA-512 sum:
d6c3c419aa70809d76bfd34bc6bcbc353fac364c00a4848b51c1ffa6ca9592d11a1b70544b5b5e4ec610f1d754ed0f7c47c2b7a5f681ea6aef97008d51e52abc
  apache-netbeans-java-16.0.301.vsix
PGP signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/16.0.301/apache-netbeans-java-16.0.301.vsix.asc

The binary has been produced by the same job run #1448, from the same commit.

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as 
usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC 
member.

Thank you and sorry for rebuild...
Martin Balín



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans VSCode Extension 16.0.301

[Svata Dedic]

Hi,

During testing, one somewhat critical bug was discovered: newer 
Micronauts (3.8.x) use newer GraalVM native-image plugin, which default 
goal binding is different from what the NBLS code anticipates, so wrong 
project product artifact(s) are reported.


This PR (for delivery / NB17) should fix that. I would recommend a 
rebuild, as the bug affects the usage of the newest micronaut release in 
user projects. I'd call for a careful review of that PR.


-Svata

On 31. 01. 23 8:37, Martin Balin wrote:

Dear community,
let's update the Apache NetBeans Language Server extension on VSCode 
Marketplace with improved version 16.0.301 and updated 3rd party npms without 
CVEs.
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/16.0.301/

The primary voting artifact is the source
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/16.0.301/apache-netbeans-java-16.0.301-source.zip
built from branch ‘vsnetbeans_1603`
SHA-512 sum is: 
298952756a81d0ce56f7b2a7de577620f09a826ef461ec8cdbc0e54f811f6945a5f0e8712545863e162ee91179cf9b23808f5dfff5cf5a8498cb47b555cbf7a1
 apache-netbeans-java-16.0.301-source.zip
and PGP signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/16.0.301/apache-netbeans-java-16.0.301-source.zip.asc

Binary artifacts were built by 
https://ci-builds.apache.org/job/Netbeans/view/vscode/job/netbeans-vscode/1446/

Use following commands to build your own 16.0.301 VSIX binary:

tmp$ unzip apache-netbeans-java-16.0.301-source.zip
tmp$ ant build
tmp$ cd java/java.lsp.server
tmp$ ant build-vscode-ext -Dvsix.version=16.0.301 -D3rdparty.modules=none

In addition to the source ZIP file, we are also voting about convenience binary:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/16.0.301/apache-netbeans-java-16.0.301.vsix
SHA-512 sum:
d935ca2f6245bd71097d98182bbcc687531e369d546e99f83b66af5fce6dfaed80dab843c801823c47c1f50fd9e62244574f101a920e6dbcf918afc4da6699af
 apache-netbeans-java-16.0.301.vsix
PGP signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/16.0.301/apache-netbeans-java-16.0.301.vsix.asc

The binary has been produced by the same job run #1446, from the same commit.

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as 
usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC 
member.

Thank you,
Martin Balín

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Arrays.asList...stream to Arrays.stream

[Svata Dedic]

And what about old school

List uris = new ArrayList<>(prjs.length);
for (Project p : prjs) {
for (AntArtifact a : 
AntArtifactQuery.findArtifactsByType(p, 
JavaProjectConstants.ARTIFACT_TYPE_JAR)) {

uris.addAll(Arrays.asList(a.getArtifactLocations()));
}
}
return toURLs(uris);
? Streams and lambdas are very modern, fancy and cool, but if it ever 
comes to debugging are just pain in the ass.


-S.

On 29. 01. 23 6:59, name name2 wrote:

toURLs(
Arrays.asList(prjs).stream().flatMap(
 (prj) -> Arrays.asList(
 AntArtifactQuery.findArtifactsByType(prj,
JavaProjectConstants.ARTIFACT_TYPE_JAR)
 ).stream()).
 flatMap((a) -> Arrays.asList(a.getArtifactLocations()).stream()).
 collect(Collectors.toList())
);

to

toURLs(
Arrays.stream(prjs).flatMap(
 (prj) -> Arrays.stream(
 AntArtifactQuery.findArtifactsByType(prj,
JavaProjectConstants.ARTIFACT_TYPE_JAR)
 )).
 flatMap((a) -> Arrays.stream(a.getArtifactLocations())).
 collect(Collectors.toList())
);


Its ProjectClassPathModifier.java

8 files changed:

-

extide\gradle\src\org\netbeans\modules\gradle\loaders\ExtensionPropertiesExtractor.java
-

groovy\groovy.editor\src\org\netbeans\modules\groovy\editor\api\parser\GroovyParser.java
- ide\db\src\org\netbeans\api\db\explorer\ConnectionManager.java
-

java\java.project\src\org\netbeans\api\java\project\classpath\ProjectClassPathModifier.java
- nb\autoupdate.pluginimporter
- src\org\netbeans\modules\autoupdate\pluginimporter\Installer.java
-

test\unit\src\org\netbeans\modules\autoupdate\pluginimporter\InstallerTest.java
- o.n.upgrader\src\org\netbeans\upgrade\AutoUpgrade.java
- test\unit\src\org\netbeans\upgrade\AutoUpgradeTest.java


Can i make PR or not?




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: nb16 source verification

[Svata Dedic]

Hi,

downloaded right now - SHA512 seems correct (did you checked by sha512, 
not sha1 :) ?), and even the GPG signature is OK - but Neil's signing 
key expired just today (signed on 21. Nov 2022)


Maybe the release should be signed next time by a key which is at least 
6 months before expiration or something like that, so it survives to the 
next release.


-S.

On 11. 01. 23 3:37, Ernie Rael wrote:

Just downloaded source from https://netbeans.apache.org/download/nb16/

I'm getting verification failures with both sha and gpg.

I have to figure it out every time, could be cockpit error; but this 
seems like a real failure.


-ernie


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [External] : RE: [DISCUSSION] Gradle Patch Release for NetBeans 16

[Svata Dedic]

Hi,

late Friday, a colleague discovered a bug in NbProjectInfoBuilder - 
mishandled compiler options (compilerArgs / allCompilerArgs / 
freeCompilerArgs) that fails to load the project when NB runs on JDK19. 
I can provide a fix tomorrow.


-S.

On 18. 12. 22 18:28, Neil C Smith wrote:

On Sun, 18 Dec 2022 at 16:58, Laszlo Kishalmi  wrote:

I'm ready to update the netbeansrelease.json. In the 12.0-u1 and 12.0-u2
it was just another entry with git hash, version and position. Would it
be the same this time, or shall I use the vote entry as well. As far as
I remember vote would remove the version suffix from the final artifacts
and other places, that might be not required for 16-uc1.


Yes, try as before and leave out vote.  That does very little now, but
I think will still stop the version suffix being added.  Eric even
better to answer that!  Quite a lot has changed since we did 12.0
updates, but all should hopefully work OK.

Try to update netbeansrelease.json after merging and before building
if you can.  The build process also publishes to
https://nightlies.apache.org/netbeans/candidate/netbeans/ now which
currently has your build without a suffix.  Aside - we should look at
adding -dev as suffix to files for this as fallback.

Nightlies might be a better update centre to share for testing too if
we need to in future.

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans VSCode extension 16.0

[Svata Dedic]

+1 (binding)

- SHA512 and GPG signature OK
- installs OK, provides views and code completion
- tested on Ubuntu 20.04 / Oracle Java 11.

-Svata

On 29. 11. 22 12:48, Martin Balin wrote:

Hello,
Vote for Apache NetBeans VSCode Extension 16.0 to be released.
Primary voting artefact:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/16.0/apache-netbeans-java-16.0.0.vsix
 


SHA512 checksum:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/16.0/apache-netbeans-java-16.0.0.vsix.sha512
 

e5c2649738178fcc3eedd23f6d42bfd2301ad4ebb5cd0f69fb6ea521d5b0de6a5eedfb1deed518be425ce5f92aa73f21345dbc01a6ce33909d6c02d858e09c7f
  apache-netbeans-java-16.0.0.vsix
PGP signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/16.0/apache-netbeans-java-16.0.0.vsix.asc
 


Built by the same jenkins job as main NetBeans 16.0 release and source code 
vote artefacts:
https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/11/
 


This vote is going to be open at least 72 hours, vote with +1, 0, and
-1 as usual. Please mark your vote with (binding) if you're an Apache
NetBeans PMC member.

This vote is dependent on the main Apache NetBeans 16 release vote passing.

Regards,
Martin





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: CI - the final migration

[Svata Dedic]

Hi,

please temporarily disable the java.lsp.server test in the main suite, I 
will take the #4921 over next week.


Great job with the migration !
-Svata


On 05. 11. 22 19:18, Michael Bien wrote:

Hi devs,

at first we weren't sure if we should migrate all travis jobs to github, 
then we weren't sure if we actually can without using up all of apache's 
resources. Well, those fears/concerns don't matter anymore since we have 
to finish migration till the end of this year when travis support for 
apache projects ends:


https://cwiki.apache.org/confluence/display/INFRA/Travis+Migrations


This PR migrates almost all of the remaining jobs to gh actions:

https://github.com/apache/netbeans/pull/4817

feedback appreciated. Esp if you want to run certain jobs on certain 
labels. New label additions are: 'Groovy', 'GraalVM', 'VSCode Extension' 
and 'tests'. Other newly migrated jobs either run always since they 
don't take much time or were mapped to previously used labels.



One job is missing. It turned out that the LSP job is the final boss of 
this endeavor. I tried to replicate the travis environment, bumped 
timeouts, incrementally commented out tests, diffed logs between local 
runs and gh runs, but the job managed to generate new exceptions to keep 
things interesting. Migrating unreliable tests is extra painful since 
you never know if that exception you are looking at is of kind: regular, 
regular-new, sporadic or sporadic-new :)


So I have given up on that one for now until I regain more willpower for 
this task.


A test setup is here if anyone is interested to take a look (feel free 
to push into the PR if you want, its not meant for merging):


https://github.com/apache/netbeans/pull/4921


best regards,

michael


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: NB RC-3 Gradle Issues

[Svata Dedic]

It would greatly help to also supply a minimal build.gradle that 
triggers the failure: I've tried to load several of my gradle samples 
using JDK19 seemingly without any issues.


The printed type/method seems as my changes to gradle loading are the 
culprit: based on the sample I'll be probably able to wrap the internal 
API calls into better guards.


Please run the IDE with the following on the commandline:

-J-Dorg.netbeans.modules.gradle.loaders.LegacyProjectLoader.level=400

that should print (a ton of !) additional gradle-nb communication to the 
log, possibly including the real exception thrown in the daemon.


-Svata

On 05. 11. 22 8:26, Laszlo Kishalmi wrote:
Reverting back to Java 17 or 18 as IDE runtime would be a solution. 
Though it seems this time we reached too deep into the Gradle internals 
an got burned. That means you've found a real bug. Would you report it 
on github? We might be able to do an RC4 for NB-16. Though it is 
possible that it would be NB-17.


[...]

On 11/4/22 21:04, Scott Palmer wrote:
When I edited netbeans.conf to force NB to run with JDK 17, my project 
that uses Gradle 7.6-rc-1 via the Gradle wrapper and JDK 19 (via 
Gradle Java Toolchain support) still claimed that it would not load.  
The only error message shown is:


'boolean 
org.gradle.api.internal.provider.ValueSupplier$ExecutionTimeVaue.isFixedValue()’


I had the Gradle settings in NB set to use that fixed path for Gradle 
and ignore my wrapper settings.  It is the path to my Gradle 7.6-RC-1 
install, though I don’t need it to be 7.6 to run the Gradle script..





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [feedback thread] Label controlled CI pipeline

[Svata Dedic]

On 17. 10. 22 15:13, Michael Bien wrote:


I saw the micronaut tests of the enterprise job fail twice so far. This 
might need to be wrapped into the retry script.





Have you links to those failures ? I've added the whole micronaut 
testsuite recently (PR merged today), maybe it could be better to 
stabilize the tests (?)


-S.




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans VSCode extension 15.0.301

[Svata Dedic]

Hi,

+1 (binding)

- signatures and SHA checked
- built from sources - all OK
- checked vscode Projects view, build, compile, run, test explorer

tested on Ubuntu Linux 20.04.5 LTS / KDE / Oracle JDK11

-S.

On 11. 10. 22 13:41, Martin Balin wrote:

Dear community,
let's update the Apache NetBeans Language Server extension on VSCode 
Marketplace with improved version 15.0.301
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/15.0.301/

The primary voting artifact is the source
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/15.0.301/apache-netbeans-java-15.0.301-source.zip
built from branch ‘vsnetbeans_1503`
SHA-512 sum is: 
1bb5933e23de63f6b4a34d46e0c7bc1599820590c27209564b7bf012bf65fe1ea074f8596c3ea2af5eb40da426880797d4f04c1f9ab196a21c9616648a1ddb06
 apache-netbeans-java-15.0.301-source.zip

and PGP signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/15.0.301/apache-netbeans-java-15.0.301-source.zip.asc

Binary artifacts were built by 
https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/1281/

Use following commands to build your own 15.0.301 VSIX binary:

tmp$ unzip apache-netbeans-java-15.0.301-source.zip
tmp$ $ ant build
tmp$ cd java/java.lsp.server
tmp$ ant build-vscode-ext -Dvsix.version=15.0.301 -D3rdparty.modules=none

In addition to the source ZIP file, we are also voting about convenience binary:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/15.0.301/apache-netbeans-java-15.0.301.vsix
SHA-512 sum:

416ba38e0f255f8f2fd23e2eda8d2cda5b026907757a6cf84719e24256a16b20e39f1f4a67788c16cf2c9dfaab22b4aa5da7d3acbeb864636d8449a6c844aac4
  apache-netbeans-java-15.0.301.vsix

PGG signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/15.0.301/apache-netbeans-java-15.0.301.vsix.asc

The binary has been produced by the same job run #1281, from the same commit.

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as 
usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC 
member.

Thank you,
Martin Balín



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Maven "Graph" functionality

[Svata Dedic]

What  was the project's size (# of dependency closure) ?

-S.

On 07. 10. 22 15:46, Eric Bresie wrote:

OkayI was trying again and wanted to bring it up again.
When opening pom.xml, clicking the Graph button, it seems to get stuck
while "Loading and constructing the graph".  It indicates it may take a
while, but I'm just wondering why this takes so long.  Is this just an old
feature that hasn't been updated/optimized or is it just that big (and
timely task)?

The IDE becomes unresponsive during this.  In Windows Task Manager, it
shows with Netbeans 15 about 1.7 Gigs of memory in use.
After waiting 15 minutes of unresponsiveness I gave up and shut down
Netbeans.
Eric Bresie
ebre...@gmail.com


On Sat, Sep 10, 2022 at 1:07 PM Eric Bresie  wrote:


Never mind, I guess as indicated it takes a while to scan, layout, and
render.

Eric Bresie
ebre...@gmail.com


On Sat, Sep 10, 2022 at 12:58 PM Eric Bresie  wrote:


While trying to debug / update some maven dependencies, while in the
Maven Pom editor.  I noticed the "Graph" button/view which when pressed
shows the message "Loading and constructing graph (this may take a while)."
but then after doing so, it seems to get stuck on this for some reason and
I'm unable to do anything after that.

Has anyone else seen a similar issue?

Running with Netbeans 15, on Windows 11, with

java -version
openjdk version "11.0.12" 2021-07-20
OpenJDK Runtime Environment Microsoft-25199 (build 11.0.12+7)
OpenJDK 64-Bit Server VM Microsoft-25199 (build 11.0.12+7, mixed mode)

mvn -version
Apache Maven 3.8.6 (84538c9988a25aec085021c365c560670ad80f63)
Maven home: C:\..\apache-maven-3.8.6
Java version: 11.0.12, vendor: Microsoft, runtime: C:\Program
Files\Microsoft\jdk-11.0.12.7-hotspot
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"


Eric Bresie
ebre...@gmail.com








-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: netbeans module coding questions

[Svata Dedic]

On 07. 09. 22 19:46, Peter Cheung wrote:

hi
1. I want to customize the editor's side bar (the one showing the line 
number), I want to add some icon to it. Any example for this?


Two ways:
1/ register a sidebar on the 'west' side. See editor.fold.nbui module - 
you're free to paint whatever you want.
2/ make an annotation and assign a glyph to it. See the Editor 
Annotations APIs, e.g. debugger annotations for example.



2. The highlightfactory + highlighter is highlighting the editor by char 
offset. Is it possible to highlight some rows?


At least two ways.
- make an AnnotationType of 'line' type. Use Annoation API to mark the line.
- make the highlight include the terminating newline and include 
HighlightsContainer.ATTR_EXTENDS_EOL = true in its attributes.


-S.

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 15 VSCode Extension

[Svata Dedic]

+1 (binding)

- Signatures verified
- Successfully installed, project features work OK
- Tried basic edit-debug-run scenario, Maven + Gradle projects
tested on Linux Ubuntu 20.04.5 LTS, vscode 1.70.2

-Svata

On 29. 08. 22 18:42, Martin Balin wrote:

Dear community,
Vote for Apache NetBeans 15.0 VSCode Extension (VSNetBeans)

Primary voting arefact:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/15.0.0/apache-netbeans-java-15.0.0.vsix

SHA512 checksum:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/15.0.0/apache-netbeans-java-15.0.0.vsix.sha512

c4df696eea6bc49e4114a9356b4afb34e69715e260bbc49b888eae73d43ba228274e75c1a06b2ebf9990bab532df78af50842dcf236ae353bcf28304cda938a1
  apache-netbeans-java-15.0.0.vsix

PGP Signature file:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/15.0.0/apache-netbeans-java-15.0.0.vsix.asc

Built by same job as main NetBeans 15 artefacts
https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release150/16/artifact/dist/vsix/

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as 
usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC 
member.

This vote is dependent on the main Apache NetBeans 15 release vote passing.

thank you,
Martin




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: my plugins rely on maven plugin but don't know how to load it programatically

[Svata Dedic]

It is, but I'd like at least some time (and ideally some 
colleague/companion for the work - it's big) for +- reviewing / 
polishing the API before publishing


-S.

On 20. 07. 22 17:45, Neil C Smith wrote:

On Tue, 19 Jul 2022 at 21:36, Svata Dedic  wrote:


On 19. 07. 22 18:32, Peter Cheung wrote:

Hi

  I am creating a new project type for RISC-V. The below code only work 
when my netbeans loaded maven plugin. Is it possible to let netbeans load my 
plugin and auto load maven plugin together?



Well, that's bad. Maven module's API is just 'friend API'; so it is only
available to a certain set of modules. Mainly because the API is too
broad and the original author perhaps did not feel (?) it's rock solid
to be published and maintained for good.

If it was a regular API, you could just add a module dependency.


Well, I'll +1 a PR to stop it being a friend API.  It's been like that
for a long time, it's got a friends list as long as your arm, some of
which are external.  It's just API by stealth now.

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: my plugins rely on maven plugin but don't know how to load it programatically

[Svata Dedic]

On 19. 07. 22 18:32, Peter Cheung wrote:

Hi

 I am creating a new project type for RISC-V. The below code only work when 
my netbeans loaded maven plugin. Is it possible to let netbeans load my plugin 
and auto load maven plugin together?



Well, that's bad. Maven module's API is just 'friend API'; so it is only 
available to a certain set of modules. Mainly because the API is too 
broad and the original author perhaps did not feel (?) it's rock solid 
to be published and maintained for good.


If it was a regular API, you could just add a module dependency.

You may consider to make an "implementation dependency" on Maven 
Projects module -- 
https://netbeans.apache.org/wiki/DevFaqImplementationDependency.asciidoc


--%< from project.xml of the dependent module -%<--



org.netbeans.modules.maven



2




--%<%<-%<--
But please read carefully to understand the consequences. But the 
reflection is really ugly


-S.




 How can my netbeans modules got the mvn path? i found "mavenHome = 
EmbedderFactory.getEffectiveMavenHome();" in netbeans source code but I don't have 
class EmbedderFactory

ClassLoader syscl = Lookup.getDefault().lookup(ClassLoader.class);
System.out.println(syscl);

List goals = new ArrayList<>();
goals.add("compile");
ProjectInformation projectInformation = ProjectUtils.getInformation(this);

Class runUtils = 
syscl.loadClass("org.netbeans.modules.maven.api.execute.RunUtils");
Method createRunConfig = runUtils.getMethod("createRunConfig", new 
Class[]{File.class, Project.class, String.class, List.class});
Object rc = createRunConfig.invoke(null, FileUtil.toFile(this.projectDir), 
this, projectInformation.getDisplayName(), goals);

Class runConfig = 
syscl.loadClass("org.netbeans.modules.maven.api.execute.RunConfig");

// maven properties
Method setProperty = runConfig.getMethod("addProperties", new 
Class[]{Map.class});
Map properties = new HashMap<>();
setProperty.invoke(rc, properties);

// maven profile
Method setActivatedProfiles = runConfig.getMethod("setActivatedProfiles", new 
Class[]{java.util.List.class});
List profiles = new ArrayList<>();
profiles.add("dev");
profiles.add("prod");
setActivatedProfiles.invoke(rc, profiles);

Method executeMaven = runUtils.getMethod("executeMaven", new 
Class[]{runConfig});
executeMaven.invoke(null, rc);



Thanks


From Peter (System Architect, Quantr Limited https://www.quantr.hk , Mobile : 
96554595)





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans VSCode extension 14.0.301

[Svata Dedic]

+1 (binding)

- SHA signatures checked, GPG verified
- builds cleanly
- open (gradle, maven) project, generate micronaut entity class, basic 
editing, run,debug


Tested on Kubuntu 20.04.4 LTS x86_64, KDE

Issues found (will report separately, not critical for the release):
- go to library source (maven) fails with NPE. Not critical, will fix 
for NB15
- gradle support seems to work bad with symlinked ~/gradle/cache 
directory; perhaps never worked, will investigate further. NB bug.


-Svata

On 13. 07. 22 16:03, Jan Horvath wrote:

+1

Tested on MacOS 12.4, SHA check is OK.

Jan


On 13. 7. 2022, at 7:42, Martin Balin  wrote:

Dear community,
let's update the Apache NetBeans Language Server extension on VSCode 
Marketplace with significantly improved version 14.0.301
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/14.0.301/

The primary voting artifact is the source
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/14.0.301/apache-netbeans-java-14.0.301-source.zip
built from branch ‘vsnetbeans_1403`
SHA-512 sum is: 
0bcfcd04d58438d7fc06cd73d08fd7b59a80912b47a39ff1e4e5d134f6b05b6aa216a5f8fa604c2f58a35d24232c066d1e637a59ffeede996e3f557e523c3d1f
 apache-netbeans-java-14.0.301-source.zip

and PGP signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/14.0.301/apache-netbeans-java-14.0.301-source.zip.asc

Binary artifacts were built by 
https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/1182/

Use following commands to build your own 14.0.301 VSIX binary:

tmp$ unzip apache-netbeans-java-14.0.301-source.zip
tmp$ $ ant build
tmp$ cd java/java.lsp.server
tmp$ ant build-vscode-ext -Dvsix.version=14.0.301 -D3rdparty.modules=none

In addition to the source ZIP file, we are also voting about convenience binary:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/14.0.301/apache-netbeans-java-14.0.301.vsix
SHA-512 sum:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/14.0.301/apache-netbeans-java-14.0.301.vsix.sha512
PGG signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/14.0.301/apache-netbeans-java-14.0.301.vsix.sha512
The binary has been produced by the same job run #1182, from the same commit.

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as 
usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC 
member.

Thank you,
Martin Balín



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Netbeans 13.0 only supposed to properly runs on GraalVM 17?

[Svata Dedic]

Hi,

NetBeans relies on an embedded Graal.js (which includes Truffle 
libraries) for parsing javascript PAC proxy configuration. There was a 
bug in NB-13 until almost NB14 release in bad metadata in a wrapper jar 
that blocked some classes from loading - they were moved in Truffle to 
another package.


NB14 should be fine AFAIK (or at least I hope - I checked this when 
signing off the release).


The workaround for the earlier releases is to specify proxy settings 
manually in the Tools | Options; the js support is only attempted if the 
autoconfiguration is used && PAC resource is actually available at the 
runtime.


-S.

Dne 12. 06. 22 v 11:05 Jean-Marc Borer napsal(a):

Ok so before filing a bug, I want to retry with NB 14. I was looking for
the packages released for the vote. They are no longer available. Do you
know where I can find them?

JM

PS: I am working in a very complicated (secured) professional environment
and I clearly push NB into certain limits especially what relates to secure
proxies, certificate handling and white listed sites. At home, I don't have
such constraints and would certainly not notice these issues.

We still use NB platform even for new apps. My concern is therefore that
the platform properly runs in our environment and it starts with NB IDE.
Currently I still use 12.4 with JDK 8, which is rather robust.
Unfortunately I still cannot say the same with NB 13 and JDK 17, but I try
to make it happen as much as I can, but there are a lot of areas in the IDE
that clearly don't know yet to properly diagnose my issues.

On Sun, Jun 12, 2022 at 10:55 AM Geertjan Wielenga
 wrote:


Yes, I’m surprised too. And obviously NetBeans is not supposed to run only
on GraalVM, you know the answer to that question, and that this is a bug.

Gj

On Sun, 12 Jun 2022 at 10:53, Jean-Marc Borer  wrote:


Hello Geertjan,

Well yes and no. I am surprised that NB seems to, somehow, rely on

Truffle

classes during startup. As I am not a JVM expert, I was not knowing what
Truffle is. By the way, is NB now supposed to only run on GraalVM? Same
question for NB platform based applications, which is actually my

concern.


JM

On Sun, Jun 12, 2022 at 10:45 AM Geertjan Wielenga
 wrote:


You’re surprised that messages about missing Truffle classes do not

appear

when you use GraalVM?

Gj

On Sun, 12 Jun 2022 at 10:42, Jean-Marc Borer 

wrote:



Hello all,

Since I had several issues with NB 13 (see
https://github.com/apache/netbeans/issues/4050), I tried different

JVMs.


I notice that the only one not generating warnings in the log (for

example

related to missing Truffle classes) is GraalVM 17. I have to say

that I

am

a bit surprise in this regard since it is not specified anywhere and

this

disables the possibility to design or use UI previews with JFX

components.


Is Netbeans not supposed to run on any flavor (JVM) 11+?

Best regards,

JMB












-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Kill ValidateLayerConsistencyTest?

[Svata Dedic]

I have very bad experience with turning off integration tests. And 
consistency of the registrations is ultimately important. We can easily 
go unnoticed to the situation when the IDE simply does not start because 
of broken layer.


I've fixed similar situation in the past (after some time without proper 
tests) and would appreciate not to go through the hell again.


-S.


Dne 09. 06. 22 v 19:10 Michael Bien napsal(a):

On 08.06.22 20:54, Matthias Bläsing wrote:

Hi again,

Am Montag, dem 06.06.2022 um 09:05 +0200 schrieb Jaroslav Tulach:
2022-05-29T17:06:31.9092439Z [junit] java.lang.AssertionError: 
Has to be NbRepository: org.openide.filesystems.Repository@744b325b
2022-05-29T17:06:31.9093232Z [junit] at 
org.netbeans.core.startup.Main.start(Main.java:298)
2022-05-29T17:06:31.9094120Z [junit] at 
org.netbeans.core.startup.TopThreadGroup.run(TopThreadGroup.java:98)
2022-05-29T17:06:31.9094571Z [junit] at 
java.lang.Thread.run(Thread.java:750) 2022-05-29T17:06:31.9095235Z

[junit]

Isn't this caused by some race condition? Temporarily adding
`this.when = new
Exception("initialized")` into `Repository` constructor and printing
the
stacktraces when the `AssertionError` happens might tell us who's
responsible
for the misconfiguration of the test.

This is a very nice way to catch this - thank you for the idea. I had
to slightly alter it, but I got a stack trace.

I decided to go ahead with merging the PR and see how it develops in
the next few days.

I filed an issue to hold information about that problem:

https://github.com/apache/netbeans/issues/4211

Then at least there is a record of it and it can be further analysed.

Greetings

Matthias


Hi,

we are lucky that the test is on a job which doesn't take very long to 
run, but It might be good to consider to disable it anyway for now.


I had to run it 4 times here:

https://github.com/apache/netbeans/actions/runs/2465738672

and twice here:

https://github.com/apache/netbeans/actions/runs/2468718859

since this is in a 4x matrix, basically every commit will likely fail 
and someone has to restart something.


you can see it here:

https://github.com/apache/netbeans/commits/master


no hurry since this is still somewhat manageable i believe, but it would 
be better to turn it off until resolved IMO.


best regards,

michael



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 14

[Svata Dedic]

+1 (binding)

- checked SHA and GPG signatures for all files (platform, netbeans, nbms)
- eyeballed LICENSE, NOTICE - OK
- built from sources (platform, netbeans), Oracle Java 11 / Linux Ubuntu 
19.04

- sanity check of NeBeans build: open maven project, compile, edit
- checked basic operation on Oracle Java 11 + Oracle Java 8 / Linux 
Ubuntu 19.04


-S.

Dne 01. 06. 22 v 19:46 Eric Barboni napsal(a):

This is our first voting candidate for the release of Apache NetBeans 14.

Please note all requirements below for validating sources and
convenience binaries before voting.

Apache NetBeans 14 constitutes all clusters in the Apache NetBeans Git
repository, which together provide the NetBeans Platform (i.e., the
underlying application framework), as well as all the modules that
provide the Java SE, Java EE, PHP, JavaScript and Groovy features of
Apache NetBeans.



Build artefacts are available here :

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/14/
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/14/

They were built by the Jenkins pipeline :

https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/
release140/27/



We are primarily voting on :

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/14/netbeans-14-sour
ce.zip

SHA512 :
1e7185c469e6ddd9c5aaf3ef4860f57b3cbb43f3b9213966e19362f702f03ded0e88906b1750
8c5f9cb6b9c015e6be6123ba1ef6b1fb3b402cf446a0ebbedeea

KEYS file : https://downloads.apache.org/netbeans/KEYS



Associated with the primary source item we have, generated with the
pipeline mentioned above :

-- at https://dist.apache.org/repos/dist/dev/netbeans/netbeans/14/

Binaries associated with the source - netbeans-14-bin.zip as well as
update content under the nbms folder.

-- at https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/14/

The platform cluster build netbeans-platform-14-bin.zip and
netbeans-platform-13-source.zip



Maven Artefacts

The Maven artefacts for Apache NetBeans 14 are ready on staging
associated to this vote.

https://repository.apache.org/content/repositories/orgapachenetbeans-1114/

The version is : RELEASE140



Voting Requirements

Before voting +1 you are required to download the signed source code
package, compile it as provided, and test the resulting executable on
your own platform, along with also verifying that the package meets
the requirements of the ASF policy on releases -
http://www.apache.org/legal/release-policy.html#management

In particular, you should (at least) follow these steps.

1. Download the artefact to be voted on and unzip it.
2. Check that the artefact does not contain any jar files (there are
branding folders with the name *.jar).
3. Verify the cryptographic signatures, the NOTICE and LICENSE file
4. Build it using the README provided by the artefact.
5. Look in nbbuild/netbeans for the NetBeans installation created by
the build process and try running it.

In addition to checking the sources, you should check the associated
convenience binary zips, nbms and maven staging at the artefact links
above. As well as checking any artefact functions correctly, you
should check that it has been correctly signed by a PMC member, and
that the source being voted on is sufficient to build the relevant
binary.

Separate votes will be held on other convenience binaries, including
installers. Those will be dependent on this vote passing.

This vote is going to be open at least 72 hours, vote with +1, 0, and
-1 as usual. (Please justify -1)

Please mark your vote with (binding) only if you're an Apache NetBeans
PMC member to help with voting admin.

Only respond if you are going to vote, i.e., this is NOT a discussion
thread.

Apache NetBeans 14 will be released if and when this vote passes.

Thank you to all contributors for all your hard work!
Thanks again
Best regards,

Eric, Neil and Geertjan
Apache NetBeans release team
PS: there is another voting thread you must vote one too ( :D )
PS2: i hope I replaced all the 13 by 14


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: API change

[Svata Dedic]

Dne 09. 05. 22 v 22:17 Łukasz Bownik napsal(a):


The problem is that another method of this class
*public String processPattern(String newPattern) throws
IllegalArgumentException*
becomes useless now.

I think it should be removed.



In general no API can be *ever* removed once published in a NetBeans 
release. While there's no client of this in the Apache codebase, the 
openide-util is also published as a maven artifact and can be consumed 
by anyone anywhere.



My reasoning is the following (based on original implementation)

(not disputing the reasons at all)


But.. If we want to keep this API structure unchanged then I could provide
a stubbed implementation like

@deprecated 
public String processPattern(String newPattern) throws
IllegalArgumentException {
return newPattern;
}

would it be acceptable?
I don't think so - if the client is expecting some semantics of the 


A (potential) client might expect existing semantic of the return value, 
even de-facto one (since @return is not javadoc-ed); we should not break 
that "contract". The method can be removed in the next release version 
(/x after the codename) of the openide.util - if it ever reaches a next 
release version at all.


Actually removing a method from the API can be done in a binary 
backwards-compatible way; but it would be an overkill in this case, IMHO.


Make the method deprecated, javadoc-explain why, and cut out everything 
except construction of the return value. Let's add it to all our old 
past sins.


-S.

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Build Netbeans from source behind a proxy?

[Svata Dedic]

Or, if you have the usual env vars (http_proxy etc) set up, you can do

ant -autoproxy

-S.

Dne 21. 04. 22 v 20:07 antonio napsal(a):

Try something like

export ANT_OPTS="-Dhttp.proxyHost=proxy -Dhttp.proxyPort=8080"
ant

as explained here:

https://ant.apache.org/manual/proxy.html

HTH,
Antonio

El 21/4/22 a las 19:58, Jean-Marc Borer escribió:

Hello,

I am trying to build Netbeans from the sources. However, I am sitting
behind a proxy to access the internet. Unfortunately, the build process
needs to access the internet to retrieve some items.

How can I configure the build to use my proxy to access the internet?

Thank you in advance for your help.

Cheers,

Jimbo



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans VSCode extension 13.0.301

[Svata Dedic]

Hi,

+1 (binding)

- SHA512 OK, GPG signature verified & is in KEYS file
- LICENSE, NOTICE, DEPENDENCIES seem sane
- build OK (JDK 9)
- extension installs OK from source build & convenience binary
- briefly tested on micronaut-starter, project opens, builds.
- Ubuntu Linux 19.04 + oracle JDK11 runtime

-S.

Dne 15. 04. 22 v 8:12 Martin Balin napsal(a):

Dear community,
let's update the Apache NetBeans Language Server extension on VSCode 
Marketplace with significantly improved version 13.0.301
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/13.0.301/

The primary voting artifact is the source
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/13.0.301/apache-netbeans-java-13.0.301-source.zip
built from branch ‘vsnetbeans_preview_1303’

SHA-512 sum is:
696eb7fc29ed18d455de0018790702218db24067b073fe29834113e421066f28021ead577f2f025286899ef6534f55929ce039fe6bfa26cc5c02976353f1ae24
and PGP signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/13.0.301/apache-netbeans-java-13.0.301-source.zip.asc

Binary artifacts were built by:
https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/1030/

Use following commands to build your own 13.0.301 VSIX  binary:
$ unzip apache-netbeans-java-13.0.301-source.zip
$ ant build
$ cd java/java.lsp.server
$ ant build-vscode-ext -Dvsix.version=13.0.301 -D3rdparty.modules=none

In addition to the source ZIP file, we are also voting about convenience binary:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/13.0.301/apache-netbeans-java-13.0.301.vsix
SHA-512 sum:
f6e2b0d20be21a21bbce8f7afb7ca320a603ee19b40c1c6c61a44aeea951fc67ae4eb6c4b414994e4d04d3edd6b0f64afab462da59d2e32f9697a1ac0b5b5493
PGP signature: 
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/13.0.301/apache-netbeans-java-13.0.301.vsix.asc
The binaries has been produced by the same job run #1030 from the same commit

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as 
usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC 
member.

Thank you,
Martin Balín


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 13.0 VSCode extension

[Svata Dedic]

+1 (binding)

- Checksum OK
- Signature verified
- Runs fine on JDK11, Ubuntu
- Attempted edit-compile-run cycle, all OK


Dne 28. 02. 22 v 11:31 Martin Balin napsal(a):

Dear community,

Vote for NetBeans 13.0 extension for VSCode (VSIX).
Primary voting artefact is :
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/13.0/apache-netbeans-java-13.0.0.vsix

SHA512 sum:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/13.0/apache-netbeans-java-13.0.0.vsix.sha512

PGP signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/13.0/apache-netbeans-java-13.0.0.vsix.asc

Built by Jenkins job
https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release130/20/
from the same sources as main voting artefact or 13.0

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as 
usual. Please mark your vote with (binding) if you're an Apache
NetBeans PMC member.

This vote is dependent on main NetBeans 13.0 voting result.

Thank you,
Martin




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Jira or github?

[Svata Dedic]

How do I record dependencies between GH issues ? I can of course just 
mention it - and the link will be lost somewhere in the issue conversation ?


-S.



Dne 31. 01. 22 v 9:04 Geertjan Wielenga napsal(a):

GitHub, please.

We need to set Jira to readonly soon.

Gj

On Mon, 31 Jan 2022 at 08:03, antonio  wrote:


Hi all,

So, are we expected to report issues in JIRA or in github?

Thanks,
Antonio

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans VSCode extension 12.6.301

[Svata Dedic]

+1 (binding)

- SHA512 OK. .asc signature OK.
- source build OK.
- installed OK.
- Opened Maven project, build, debug OK

-Svata

P.S.: 2022 year update to NOTICE file filed as 
https://github.com/apache/netbeans/pull/3464 for NB13.


Dne 13. 01. 22 v 9:29 Martin Balin napsal(a):

Dear community,
let's update the Apache NetBeans Language Server extension on VSCode 
Marketplace with significantly improved version 12.6.301
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.6.301/

The primary voting artifact is the source
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.6.301/apache-netbeans-java-12.6.301-src.zip
built from branch ‘vsnetbeans_preview_1263`
SHA-512 sum is:
574ef054fe1c792e3f090799122a7269af3fcebe916dc70f9421694fb340b18a94ecd38649ba6e19c5d26e3be339d87eaf431c3abf98cd35a18ac6d1c077134a
and PGP signature: 
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.6.301/apache-netbeans-java-12.6.301-src.zip.asc

Binary artifacts were built by 
https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/807/

Use following commands to build your own 12.6.301 VSIX  binary:

tmp$ unzip apache-netbeans-java-12.6.301-src.zip
tmp$ ant build-source-config -Dmetabuild.branch=release1263 
-Dmetabuild.jsonurl=https://raw.githubusercontent.com/apache/netbeans-jenkins-lib/0f4c351e89e1945ae440f53d0ac7c2ba9c0acae4/meta/netbeansrelease.json

tmp$ cd java/java.lsp.server

java.lsp.server$ ant build-vscode-ext -Dvsix.version=12.6.301 
-D3rdparty.modules=none 
-Dmetabuild.jsonurl=https://raw.githubusercontent.com/apache/netbeans-jenkins-lib/0f4c351e89e1945ae440f53d0ac7c2ba9c0acae4/meta/netbeansrelease.json

In addition to the source ZIP file, we are also voting about convenience binary:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.6.301/apache-netbeans-java-12.6.301.vsix
SHA-512 sum and signature are available next to binaries.
The binary has been produced by the same job run #807, from the same commit.

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as 
usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC 
member.

Thank you,
Martin Balín




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 12.6.0 VSCode extension

[Svata Dedic]

+1 (binding)

- SHA1 & GPG verified
- extension installed OK
- worked briefly with Gradle project (Micronaut-core)

-S.


Dne 26. 11. 21 v 7:24 Martin Balin napsal(a):

Hi,
We can vote for Apache NetBeans 12.6.0 VSCode extension (VSIX) to be released 
on VSCode Marketplace.

Primary voting artifact:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.6.0/apache-netbeans-java-12.6.0.vsix

SHA512 checksum file:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.6.0/apache-netbeans-java-12.6.0.vsix.sha512

PGP signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.6.0/apache-netbeans-java-12.6.0.vsix.asc

It was built from the same source code we are voting for in main VOTE started 
by Neil C. Smith, git revision: 9cacf1fd305b775b176576c8b633b10b73524861 . 
Built by Jenknins pipeline:
https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/713/

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as 
usual.
Please mark your vote with (binding) if you're an Apache NetBeans PMCmember.
Apache NetBeans VSIX 12.6.0 will be released to VSCode marketplace  if and when 
this vote passes.

Thank you,
Martin Balin




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 12.6 Linux installer

[Svata Dedic]

+1 (binding)

- SHA512 & GPG signatures checked
- installation OK, starts with the selected JDK.
- opened & compiled maven project


Dne 24. 11. 21 v 15:20 Neil C Smith napsal(a):

Hi,

Vote for Apache NetBeans 12.6 Linux installer.

Primary voting artefact :

https://dist.apache.org/repos/dist/dev/netbeans/netbeans-installers/12.6/Apache-NetBeans-12.6-bin-linux-x64.sh

SHA512 checksum :

https://dist.apache.org/repos/dist/dev/netbeans/netbeans-installers/12.6/Apache-NetBeans-12.6-bin-linux-x64.sh.sha512
d6617b90eb2e32d7037d136e6cef6c2753c856f036a831157473b9da5fcb258ca0a92e6590d4ff2a385572bd6bbe1e163f5daa81655c6bc1e7690c474c5cbca9

KEYS file :

https://dist.apache.org/repos/dist/release/netbeans/KEYS

PGP signature file :

https://dist.apache.org/repos/dist/dev/netbeans/netbeans-installers/12.6/Apache-NetBeans-12.6-bin-linux-x64.sh.asc

Built by Jenkins job :

https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release126/14/

This vote is going to be open at least 72 hours, vote with +1, 0, and
-1 as usual. Please mark your vote with (binding) if you're an Apache
NetBeans PMC member.

This vote is dependent on the main Apache NetBeans 12.6 release vote passing.

Thanks and best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 12.6

[Svata Dedic]

+1 (binding)

- ZIP and NBMs SHA512 checked, GPG signatures OK.
- LICENSE, NOTICE and DEPENDENCIES present & sane in the tarball
- build from sources (JDK 8, JDK 11) - Ubuntu 18.04
- basic test (open project, compile run + debug), editing OK
- Maven + gradle projects

-Svata

Dne 22. 11. 21 v 18:21 Neil C Smith napsal(a):

Dear community,

This is our first voting candidate for the 12.6 release of Apache NetBeans.

Please note all requirements below for validating sources and
convenience binaries before voting.

Apache NetBeans 12.6 constitutes all clusters in the Apache NetBeans
Git repository, which together provide the NetBeans Platform (i.e.,
the underlying application framework), as well as all the modules that
provide the Java SE, Java EE, PHP, JavaScript and Groovy features of
Apache NetBeans.

Release specific wiki page :
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+12.6



Build artifacts are available here :

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.6/
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/12.6/

They were built by the Jenkins pipeline :

https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release126/14/



We are primarily voting on :

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.6/netbeans-12.6-source.zip

SHA512 : 
2e8064c603ea134df00984a1ac7221ddb0b91e1175a04f11b26e59a39530418499634b28cd64174a5a946f7237479fbb01ce09253fca354aed1fe56052b55edf

KEYS file : https://downloads.apache.org/netbeans/KEYS



Associated with the primary source item we have, generated with the
pipeline mentioned above :

-- at https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.6/

Binaries associated with the source - netbeans-12.6-bin.zip as well as
update content under the nbms folder.

-- at https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/12.6/

The platform cluster build netbeans-platform-12.6-bin.zip and
netbeans-platform-12.6-source.zip



Maven Artefacts

The Maven artefacts for Apache NetBeans 12.6 are ready on staging
associated to this vote.

https://repository.apache.org/content/repositories/orgapachenetbeans-1092/

The version is : RELEASE126



Voting Requirements

Before voting +1 you are required to download the signed source code
package, compile it as provided, and test the resulting executable on
your own platform, along with also verifying that the package meets
the requirements of the ASF policy on releases -
http://www.apache.org/legal/release-policy.html#management

In particular, you should (at least) follow these steps.

1. Download the artefact to be voted on and unzip it.
2. Check that the artefact does not contain any jar files (there are
branding folders with the name *.jar).
3. Verify the cryptographic signatures, the NOTICE and LICENSE file
4. Build it using the README provided by the artefact.
5. Look in nbbuild/netbeans for the NetBeans installation created by
the build process and try running it.

In addition to checking the sources, you should check the associated
convenience binary zips, nbms and maven staging at the artefact links
above. As well as checking any artefact functions correctly, you
should check that it has been correctly signed by a PMC member, and
that the source being voted on is sufficient to build the relevant
binary.

Separate votes will be held on other convenience binaries, including
installers. Those will be dependent on this vote passing.

This vote is going to be open at least 72 hours, vote with +1, 0, and
-1 as usual. (Please justify -1)

Please mark your vote with (binding) only if you're an Apache NetBeans
PMC member to help with voting admin.

Only respond if you are going to vote, i.e., this is NOT a discussion thread.

Apache NetBeans 12.6 will be released if and when this vote passes.

Thank you to all contributors for all your hard work!

Best wishes,

Neil, Eric and Geertjan
Apache NetBeans release team

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: NetBeans 12.6-rc2 NPE opening project

[Svata Dedic]

Scott,

if you use VisualVM, you can save the sampler data: press Snapshot (last 
icon above the data table), and then on the Snapshot tab that appears, 
there is "Export Snapshot Data" icon (again above the data table, looks 
like a diskette). The benefit of that is that we can do drill-down to 
the hotspots with that data file.


-S.

Dne 05. 11. 21 v 18:19 Scott Palmer napsal(a):
VisualVM indicates that "W32 File Monitor" is constantly using CPU, 
regardless of what is happening in the IDE, like it is in a busy loop.


org.netbeans.modules.masterfs.watcher.windows.WindowsNotifier$1.run 
()30,109 ms (100%)30,109 ms (100%)
   
org.netbeans.modules.masterfs.watcher.windows.WindowsNotifier.access$100 
()30,109 ms (100%)30,109 ms (100%)
 
org.netbeans.modules.masterfs.watcher.windows.WindowsNotifier.waitForChange 
()30,109 ms (100%)30,109 ms (100%)
   
org.netbeans.modules.masterfs.watcher.windows.$Proxy4.GetQueuedCompletionStatus 
()30,109 ms (100%)30,109 ms (100%)
         com.sun.jna.Library$Handler.invoke ()30,109 ms (100%)30,109 ms 
(100%)



The key difference is that when waiting for the Open Project dialog, CPU 
time is also accumulating elsewhere.  e.g. in "Inactive Request 
Processor Thread"
Inactive RequestProcessor thread [Was:Explorer 
Actions/org.netbeans.modules.openide.explorer.ExplorerActionsImpl$ActionStateUpdater]173,499 
ms (100%)36,594 ms (100%)
   org.openide.util.RequestProcessor$Processor.run ()190,800 ms 
(100%)36,594 ms (100%)

     java.lang.Object.wait[native] ()163,209 ms (81.1%)0.0 ms (0%)
       org.openide.util.lookup.Lookups.executeWith ()37,990 ms 
(23.4%)36,594 ms (100%)


Here is a list of hotspots... note that the top 4 items are just 
constantly increasing every second.
All I have done since starting the sampling is show the open Project 
dialog and cancel it a few times.


image.png

(Hopefully the screenshot comes through)

Scott

On Fri, Nov 5, 2021 at 4:57 AM Svata Dedic <mailto:svatopluk.de...@gmail.com>> wrote:


Hi,

When it happens again, either run VisualVM in parallel & monitor, or
take a few thread dumps in sequence (CTRL + \ in console or SIGQUIT
signal). Maybe the thread dumps could lead us to what blocks project
open or takes so much time. File a JIRA issue + attach the visualvm
snapshots or thread dumps. Thanks.

-S.


Dne 05. 11. 21 v 4:29 Scott Palmer napsal(a):
 > I've hit this exception a couple times now...  I'm just trying to
open
 > Gradle projects.  Note that the Open Project... dialog takes a
very long
 > time to appear, unacceptably long - tens of seconds.
 >
 > java.lang.NullPointerException: Cannot invoke "String.equals(Object)"
 > because "value" is null
 > at
 >

org.netbeans.core.startup.preferences.NbPreferences.put(NbPreferences.java:154)
 > at
 >

org.netbeans.core.startup.preferences.NbPreferences.put(NbPreferences.java:149)
 > at
 >

org.netbeans.modules.project.ui.OpenProjectListSettings.setStringList(OpenProjectListSettings.java:169)
 > at
 >

org.netbeans.modules.project.ui.OpenProjectListSettings.setOpenProjectsDisplayNames(OpenProjectListSettings.java:219)
 > at
 >

org.netbeans.modules.project.ui.OpenProjectList.saveProjectList(OpenProjectList.java:1462)
 > at
 >

org.netbeans.modules.project.ui.OpenProjectList.access$2300(OpenProjectList.java:116)
 > at
 >

org.netbeans.modules.project.ui.OpenProjectList$10.run(OpenProjectList.java:873)
 > at
 >

org.netbeans.modules.project.ui.OpenProjectList$10.run(OpenProjectList.java:870)
 > at
 >

org.netbeans.modules.openide.util.DefaultMutexImplementation.writeAccess(DefaultMutexImplementation.java:229)
 > at org.openide.util.Mutex.writeAccess(Mutex.java:252)
 > at
 >

org.netbeans.modules.project.ui.OpenProjectList.open(OpenProjectList.java:870)
 > at
 >

org.netbeans.modules.project.ui.OpenProjectList$6.run(OpenProjectList.java:672)
 > at
org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
 > at
 >
org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)
 > at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)
 > [catch] at
 >
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)
 >


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
<mailto:dev-unsubscr...@netbeans.apache.org>
For additional commands, e-mail: dev-h...@netbeans.apache.org
<mailto:dev-h...@netbeans.apache.org>

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NE

Re: NetBeans 12.6-rc2 NPE opening project

[Svata Dedic]

Hi,

When it happens again, either run VisualVM in parallel & monitor, or 
take a few thread dumps in sequence (CTRL + \ in console or SIGQUIT 
signal). Maybe the thread dumps could lead us to what blocks project 
open or takes so much time. File a JIRA issue + attach the visualvm 
snapshots or thread dumps. Thanks.


-S.


Dne 05. 11. 21 v 4:29 Scott Palmer napsal(a):

I've hit this exception a couple times now...  I'm just trying to open
Gradle projects.  Note that the Open Project... dialog takes a very long
time to appear, unacceptably long - tens of seconds.

java.lang.NullPointerException: Cannot invoke "String.equals(Object)"
because "value" is null
at
org.netbeans.core.startup.preferences.NbPreferences.put(NbPreferences.java:154)
at
org.netbeans.core.startup.preferences.NbPreferences.put(NbPreferences.java:149)
at
org.netbeans.modules.project.ui.OpenProjectListSettings.setStringList(OpenProjectListSettings.java:169)
at
org.netbeans.modules.project.ui.OpenProjectListSettings.setOpenProjectsDisplayNames(OpenProjectListSettings.java:219)
at
org.netbeans.modules.project.ui.OpenProjectList.saveProjectList(OpenProjectList.java:1462)
at
org.netbeans.modules.project.ui.OpenProjectList.access$2300(OpenProjectList.java:116)
at
org.netbeans.modules.project.ui.OpenProjectList$10.run(OpenProjectList.java:873)
at
org.netbeans.modules.project.ui.OpenProjectList$10.run(OpenProjectList.java:870)
at
org.netbeans.modules.openide.util.DefaultMutexImplementation.writeAccess(DefaultMutexImplementation.java:229)
at org.openide.util.Mutex.writeAccess(Mutex.java:252)
at
org.netbeans.modules.project.ui.OpenProjectList.open(OpenProjectList.java:870)
at
org.netbeans.modules.project.ui.OpenProjectList$6.run(OpenProjectList.java:672)
at org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
at
org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)
at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)
[catch] at
org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans Language Server 12.5.301 VSCode Extension

[Svata Dedic]

+1 (binding)

* ZIP and VSIX sha-checked, signatures verified
* built from sources (OK), installed into vscode (OK)
* used as an editor for several hours
* basic run / debug / stop at breakpoint works

Ubuntu 19.04 / KDE / JDK8+11

-S.

Dne 14. 10. 21 v 9:31 Martin Balin napsal(a):

Dear community,
let's update the Apache NetBeans Language Server extension on VSCode 
Marketplace 
https://marketplace.visualstudio.com/items?itemName=ASF.apache-netbeans-java to 
significantly improved version 12.5.301.

https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.5.301/

The primary voting artifact is the source
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.5.301/apache-netbeans-java-12.5.301-src.zip
with SHA-512 sum:
11b460cfaa8d98f9612320c0040e7f928d0b6af904427ad92867ef64c5df3ec7d12192b3980e10f04e15033d0f5ddd57ec0cdda3bdec8c706be541b8f722ff13
and PGP signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.5.301/apache-netbeans-java-12.5.301-src.zip.asc

The artifacts have been generated by
https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/650/ from git 
revision b19730846d986575f26b3b70236d2142dde18157

Use following commands to build your own 12.5.301 VSIX  binary:

tmp$ unzip apache-netbeans-java-12.5.301-src.zip

tmp$ ant build 
-Dmetabuild.jsonurl=https://raw.githubusercontent.com/JaroslavTulach/netbeans-jenkins-lib/jtulach/vsnetbeans_preview_1253/meta/netbeansrelease.json

tmp$ cd java/java.lsp.server

java.lsp.server$ ant build-vscode-ext -Dvsix.version=12.5.301 
-D3rdparty.modules=.*nbjavac.*

The special netbeansrelease.json is needed now (and was used in build job #650) 
due to pending PR to netbeans-jenkins-lib 
https://github.com/apache/netbeans-jenkins-lib/pull/35

In addition to the source ZIP file, we are also voting about convenience binary:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.5.301/apache-netbeans-java-12.5.301.vsix
with SHA512  checksum:
ed94506362a3f6add8e3cd6f4f50f94178d761701001045158ee9d2a7935136fe706ff8a3e3c6c04be2b2feb422e72219959435ddec93c512cfb79ca3b30108b
and
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.5.301/apache-netbeans-java-12.5.301.vsix.asc
 PGP signature.
  
The binary has been produced by the same job run #650, from the same commit.


This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as 
usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC 
member.

Thank you,
Martin Balín
-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: travis build unstable

[Svata Dedic]

Dne 04. 10. 21 v 15:20 Eric Barboni napsal(a):

But now the sub job "Test Java modules with nb-javac on Java 8" fail with
the following on regular basis on several PR.
"hide-logs.sh ant $OPTS -f java/gradle.java test" exited with 1.


In several of my PRs the Gradle's JavaExecToken* test is failing. Will 
fix as soon as I finish my current task.


-S.


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 12.5 Linux Installer

[Svata Dedic]

+1 (binding)

- signature and SHA verified
- complete / incomplete / custom dir installation succeeded
- installed IDE worked OK for maven
- attempted to install using JDK8,13,16 on the system

Linux Ubuntu 19.04 / KDE

-Svata


Dne 13. 09. 21 v 18:00 Eric Barboni napsal(a):

Hi,

We can vote for Apache NetBeans 12.5 Linux installer.

Primary voting artefact:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.5-installers/lin
ux/Apache-NetBeans-12.5-bin-linux-x64.sh

KEYS file:
https://dist.apache.org/repos/dist/release/netbeans/KEYS

PGP signature file:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.5-installers/lin
ux/Apache-NetBeans-12.5-bin-linux-x64.sh.asc

SHA512 checksum file:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.5-installers/lin
ux/Apache-NetBeans-12.5-bin-linux-x64.sh.sha512
6522c0be433765bb0eea6b75a35e120498574fa8be32d4f571be0b09964c744cc0f838d7148a
7307e55e8bf24b5afbfedaf7299afdb1de27dc45819e23d6d550
Apache-NetBeans-12.5-bin-linux-x64.sh

Built locally using the artefacts found in the Jenkins job:

https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/
release125/11/

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as
usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC
member.

  
Apache NetBeans-12.5 Linux Installer will be released if and when this vote

passes.


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans VSCode extension - 12.5 VSIX

[Svata Dedic]

+1 (binding)

- SHA512 and GPG signatures verified
- installs OK
- project creation, basic editing OK

Linux Ubuntu 19.04 / KDE

-S.

Dne 14. 09. 21 v 8:21 Martin Balin napsal(a):

Dear community,
We can now vote for Apache Netbeans 12.5.0 VSCode extension (VSIX).

Primary voting artefact:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.5/apache-netbeans-java-12.5.0.vsix

Keys file:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.5/apache-netbeans-java-12.5.0.vsix.asc

SHA512 checksum file:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.5/apache-netbeans-java-12.5.0.vsix.sha512

Built by Apache NetBeans CI from using already voted on 12.5.0 sources by
https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/569/

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as 
usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC 
member.

Thank you,
Martin Balín




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [DISCUSS] JAR files in Apache NetBeans 12.5 release

[Svata Dedic]

Neil, Matthias at all,

Let me present a different opinion. I understand the policy that 
"compiled code should not be part of the relase (that is: sources that 
are used to build the convenience binary).


I suppose the main philosophy behind objections against *compiled code* 
is that it is an unknown (potentially) executable sequence that is 
hard-to-modify would appear in 'open source' codebase. Or even if not 
directly 'executable', the compiled code cannot be (easily) analysed, 
inspected, edited. Which sounds rather as a nonsesne in an O/S 
ecosystem; it's rational decision to avoid such black boxes in the 
codebase. But the JARs which are presented as a big problem for the 
release do not fit to that pattern.


With this approach - what should we do, if we had for example PDF or DXF 
(autocad) as input for some of our tests ?


Note the wording "compiled code" above. But your effort seems as a fight 
against ANY archives. For example, Matthias' list:


./java/maven/test/unit/data/mavenmock/**
./enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar
...

Please also note that all remaining pre-built binary files are
- tests
- archives
- readable AND writable (= modifiable) by standard CLI or desktop tools
- entries of the binaries have a well defined format and CAN be modified.

There are a NUMBER of counter-examples in other Apache projects that 
have "compiled binaries" (ZIPs, JARs or even other binaries) in their 
GITs. Just few examples:
- Apache Common Compress: tars (even containing .so !!), ZIPs, 7z 
archives, ...

- Apache Tomcat: test resource JARs
- Apache Hadoop: test resources in JARs
...

As part of the crusade against archives, for example,
https://github.com/apache/netbeans/pull/3162/files#diff-e836c4a30a43c7356caff2498fad06d3346e406508a1c724e3ba6a308a03c680R90
replicates what Maven's jar packager does. Sort of. For example META-INF 
is not generated (but luckily it's not tested either), which should be 
part of any JAR archive.


Let me say that I am not in favour of such ad hoc code. If this is 
really an issue (which I personally doubt), then the Harness or NBJUnit 
library should be enhanced (just an idea) to process directories that 
follow certain naming convention to create test data ZIPs or JARs: It's 
IMHO more maintainable to have test data apart from the test code, 
file-based and versioned separately.


Regards,
-Svata



Dne 13. 09. 21 v 9:25 Laszlo Kishalmi napsal(a):
I'm sorry for stirring up the waters. I was acting on my memories of 
release 10.0.


https://issues.apache.org/jira/browse/NETBEANS-1719

I do not think that the release process shall be hanged upon my +0, it's 
not a -1 after all (as the jars does not contain compiled code). 
Honestly, I like the idea presented by Matthias in 
https://github.com/apache/netbeans/pull/3162 as a way forward in 12.6


On 9/11/21 11:10 AM, Neil C Smith wrote:

On Sat, 11 Sept 2021 at 18:58, Matthias Bläsing
 wrote:

I'm mildly irritated, that trivial JARs are considered a problem for
the 12.5 release, while  a huge pile of files is completely excluded
from RAT scanning.

+1, but don't be irritated! :-)

Part of the problem is that we haven't updated our release emails to
cover them, or the branding folders with jar names that have also
caused similar concerns.  It's something to look at, along with some
of the other text, before 12.6.


There is IMHO _nothing_ in this, that warrants doubts on the
cleanliness of the release.

+1  I did similar checks for 12.4.


I'll see if I can remove them all all, but for 12.5 IMHO this is out of
scope and also unnessary.

It's unnecessary anyway, except possibly on the point that was made on
legal-disuss about harder to review, and that's minor.  And probably
pointless unless we decided to address all the other archive formats?

Best wishes,

Neil

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Properties for Gradle tasks

[Svata Dedic]

Laszlo -

I've tried to find out how could a plugin inspect details of a Task 
configured for a gradle project -- but so far I haven't found a way how 
to dig out e.g. properties (primitive ones could be sufficient, maybe) ?
Is there a way or model in current Gradle support that I've missed ? The 
tooling groovy script could be capable of getting task configuration(s) 
from the live buildscript, so I would prefer that before some groovy 
parsing magic.


Thanks,
-S.

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans Language Server 12.4.301 VSCode Extension

[Svata Dedic]

+1 (binding)

- signatures OK
- build OK
- tested new project, build, debug, continuous mode run (gradle). basic 
editing.


-Svata



-Message d'origine-
De : Martin Balin 
Envoyé : jeudi 15 juillet 2021 15:01
À : dev@netbeans.apache.org
Objet : [VOTE] Release Apache NetBeans Language Server 12.4.301 VSCode
Extension

Dear community,
let's update  the Apache NetBeans Language Server extension on [VSCode
Marketplace](
https://marketplace.visualstudio.com/items?itemName=ASF.apache-netbeans-java)
to significantly improved version 12.4.301!

The primary voting artifact is the source
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.4.301/apache-netbeans-java-12.4.301-src.zip
with its
dfe47958cbabf768afe6d5e3b6ed79a88a53ee3724234bd62cf8d9c6d283ea8581d3cfbe144fe0211f1c3ae5c5e3fa12f7465caa413d2a30324a108703dcefef

SHA-512 checksum and
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.4.301/apache-netbeans-java-12.4.301-src.zip.asc
PGP signature.

The artifacts have been generated by [job run #498](
https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/498/) -
from commit
https://github.com/apache/netbeans/commit/cd6bfbc00a8ae58191e3c442492aa9e4fd5137bb-
just the ZIP file has been renamed to match the name of generated `.vsix`
binary.

Use following commands to build your own 12.4.301 VSIX  binary:

```bash

tmp$ unzip apache-netbeans-java-12.4.301-src.zip

tmp$ ant build

tmp$ cd java/java.lsp.server

java.lsp.server$ ant build-vscode-ext -Dvsix.version=12.4.301
-D3rdparty.modules=.*nbjavac.*

```

In addition to the source ZIP file, we are also voting about convenience
binary
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.4.301/apache-netbeans-java-12.4.301.vsix
with SHA512  checksum

e8074e41c78c422a4a19152251e278f97b994ba08ae8125fb004cd21f1b26c07bb7cabf1a2ea71695c175d941f80589bfb823ed038051f0df123612f2a00
apache-netbeans-java-12.4.301.vsix

and
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.4.301/apache-netbeans-java-12.4.301.vsix.asc
PGP signature. The binary has been produced by the same job run #498, from
the same commit
https://github.com/apache/netbeans/commit/cd6bfbc00a8ae58191e3c442492aa9e4fd5137bbusing
the above given steps.

This vote is going to be open at least 72 hours, vote with +1, 0, and -1
as usual. Please mark your vote with (binding) if you're an Apache NetBeans
PMC member.

Thank you,
Martin Balín


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans Language Server 12.4 VSCode ext

[Svata Dedic]

+1 (binding)

- SHA512, GPG signature verified.
- installable into vscode
- basic open-edit-debug-run scenario works

-Svata

Dne 19. 05. 21 v 14:09 Martin Balin napsal(a):

Dear community,
This is the voting for Apache NetBeans Language Server 12.4 release - VSIX for 
VSCode marketplace.
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.4/

Primary voting artefact:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.4/apache-netbeans-java-12.4.0.vsix

SHA512 check sum and PGP signature:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.4/apache-netbeans-java-12.4.0.vsix.sha512

https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.4/apache-netbeans-java-12.4.0.vsix.asc

Source code is part of already completed 12.4 voting done by Geertjan.

This version of VSIX includes nb-javac as it was discussed and finally voted by 
this thread
http://mail-archives.apache.org/mod_mbox/netbeans-dev/202104.mbox/%3c8341251.T7Z3S40VBb@logout%3e

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as
usual. Please mark your vote with (binding) if you're an Apache NetBeans PMC
member.


Thank you,
Martin Balin




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 12.4 (vote candidate 1)

[Svata Dedic]

+1 (binding)

- SHA verified, signatures valid
- LICENSE and NOTICE ok in src/binary zip
- builds OK (JDK 8, Ubuntu 19.04)
- basic sanity checks on java/maven project editing passed.

-Svata

Dne 14. 05. 21 v 23:28 Geertjan Wielenga napsal(a):

Build artifacts are available here:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.4/vc1
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/12.4/v1

They were built by the Jenkins pipeline:
https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release124/22/

We are primarily voting on:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.4/vc1/netbeans-12.4-source.zip

SHA512:
f8ee78d9ccba513234f855fc516bf251746eb030f6c747239b0db3da2f32932dc9431898fc334a22ebb25f4caec58c292b04d261736bc8de4eb6ead585dffc04



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: How to test code changes in NetBeans source

[Svata Dedic]

Dne 13. 05. 21 v 18:36 Laszlo Kishalmi napsal(a):
What I need to know is how do you test any changed code? I can't 
believe it is necessary to rebuild the app every time that would 
surely take too long and possibly not very informative. For my system 
it varies between 25 to 30 minutes. So when you change a 
class/module/cluster what do you do to see if it works correctly or 
needs more modifications.




- patch small changes during debugging using Debug | Apply Code Changes 
to patch the code immediately within the running application. Cannot 
change class structure/method signatures and has some other limitations. 
Use Debug | Stack > Pop topmost call to reexecute the changed method 
(though done for you in most cases).


- set Main Project to the module you're changing. Upon run, only that 
module (+ its necessary dependencies, if not built already) are 
compiled. Takes a few seconds + the time to boot the application.


- when chaning layer registrations, make Clean & Rebuild of the affected 
module. If you suspect something is stale in the running app, erase 
nbbuild/testuserdir/var/cache directory (or its part relevant to what 
you suspect was improperly cached).


... and when satisfied, write tests (if possible) to make sure you 
covered the corner cases too and ensure that the Travis shouts loud if 
someone breaks your new functionality in the future :)


-S.

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Status of 12.4 rc2

[Svata Dedic]

Hi,

would it be possible to tag git revisions of the RC builds as it was 
done for 12.2 release in the past ?


Thanks,
-Svata

Dne 29. 04. 21 v 16:18 Geertjan Wielenga napsal(a):

Hi all,

Here's our schedule, we're (Neil and I) are working on putting rc2
together, we're not far off from hitting the target as outlined below:

April   2: 12.4 Beta
April 16: 12.4 Feature freeze
April 21: Weekly Release Candidate 1
April 28: Weekly Release Candidate 2 (if needed)
May   5: Weekly Release Candidate 3 (if needed)
May   7 - 14: Voting
May 15 - 30: Release

All the fixes that were in the 12.4 milestone queue (10 of them) will be
included, after we merge delivery into release124, which we'll do once this
goes green:

https://github.com/apache/netbeans/pull/2925

Then we'll build rc2 and after that sync release124 with master.

Probably the issue described here by Patrik Karlstrom is the biggest issue
solved for most people, out of the 10 solved for rc2:

https://lists.apache.org/thread.html/r4190ef1ad15bbd8b1e880bdbb6aef3339a6a0f0905ceec8973fc%40%3Cdev.netbeans.apache.org%3E

Once we have rc2 available, hopefully tomorrow, we'll let everyone know --
  however, if you provided a fix for rc2, we expect you to verify that it
works as expected, i.e., we are not going to check that for you.

Thanks,

Gj




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [External] : Re: 12.4 Feature Freeze: 18:00 CET tomorrow (Friday 16 April)

[Svata Dedic]

Dne 29. 04. 21 v 9:06 Martin Balin napsal(a):

What about something like this which Svata merged to master and labeled as 12.4?
https://github.com/apache/netbeans/pull/2897
Does this need a new PR to “delivery” branch?


The commits from PR 2897 (checked 8cd30f3) seem to be already part of 
delivery branch.


-S.

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Netbeans "owning" Maven archetypes

[Svata Dedic]

BTW - looking at the JavaFX archetype resources[1], there's 
javafx-maven-plugin configured ...
... which could nicely plug into 
https://issues.apache.org/jira/browse/NETBEANS-5394 that will be 
probably implemented.


Additional action mappings would be then activated by e.g. plugin 
presence in POM. Seems to me quite similar to changing the archetype 
itself - but NB IDE would then inject its own actions on the fly, and 
the user can customize them.


If looks interesting, share your requirements in NETBEANS-5394.

[1] 
https://github.com/openjfx/javafx-maven-archetypes/blob/master/javafx-archetype-simple/src/main/resources/archetype-resources/pom.xml


Dne 21. 04. 21 v 21:21 Ernie Rael napsal(a):

IMHO, NB should
"own" that archetype, publish, and maintain it


Couldn't agree more.

But here's one case study that shows some of the problems that might be 
faced.


When I fixed javafx-maven to "run/debug out of the box", I created a 
very small independent (not a fork) github project for javafx maven 
archetypes, published it to maven central, to replace the ones (from 
gluon) used by NetBeans.


I think the PR that used those archetypes was merged somewhat by 
accident, since there was immediate objection from some senior PMC 
members (it stayed in, probably because there were frequent posts about 
it not working; and there's the permission/forgiveness pov). I think the 
objections primarily came from a desire to depend more on using 3rd 
party stuff and also to encourage bundlers to customize and include 
NetBeans.


But using 3rd party maven archetypes is not well supported in NetBeans. 
For example see the issue "Extend ArchetypeWizards.definedArchetype to 
include optional nbactions" 
https://issues.apache.org/jira/browse/NETBEANS-3104. Since I provided 
the maven archetype I was able to include an nbactions. BTW, being able 
to provide an nbactions.xml is not sufficient; some executions had to be 
added to the pom.xml. And then I opened a PR on the the 3rd party 
archetypes. The idea was that if the NetBeans issue 3104 was fixed so 
that nbactions could be specified *and* the 3rd party had the new 
executions added to the pom.xml, then NetBeans could stop using my 
archetype. There was some initial discussion and updates to the PR, then 
it sat there and was finally merged, as is, after a *year*. And in the 
meantime, a profile execution was added to the pom used by NetBeans, 
sigh. FYI: https://github.com/openjfx/javafx-maven-archetypes/pull/10


The point is that depending on a 3rd party project for functionality 
that NetBeans provides is a problem. But there is push back to provide 
even simple maven archetypes. And, at least possibly until now, little 
interest in supplying archetypes from NetBeans project.


It's understandable that there's a push to get some support from outside 
the project, considering that NetBeans is such a huge project. It seems 
it will be years, if ever, that there's a sufficient support team built 
to really take care of it through apache. I'm glad there's still new 
stuff going in and it's disappointing that [at times] base 8.2 seems 
barely supported.


-ernie

On 4/21/2021 10:56 AM, Will Hartung wrote:

I touched on this talking about the EJB new project support and how it's
currently broken.

Fundamental to this is that the IDE relies on the Maven archetype
templating system to generate project artifacts. It also wraps that 
process

up in some wizard code, and it may well do some other things, I haven't
gone into it that deeply.

However, the archetype ownership is, to me, a core issue.

It seems untoward for the IDE to have "core" functionality that 
depends on

external artifacts.

Simply put, if someone wanted to change the archetype for a project, in
this case, an Apache/NB committer can not do that. The actual owner of 
the

archetype has to do that.

It's kind that they share that with the NB community, but IMHO, NB should
"own" that archetype, publish, and maintain it, rather than relying on an
external source.

But I do not know what or if there is a process for accepting these kinds
of artifacts and getting them published to the maven repositories. Many
apache projects certainly publish to Maven Central, I don't know if NB 
does

or not (is the Lookup library published, for example?).

I'm hardly an expert on archetype authoring or publishing.

Just curious what others feel about this and what perhaps a path forward
would be.

Regards,

Will Hartung




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: 

Re: [VOTE] Release Apache VSNetBeans 12.4 Beta 2 (VSIX)

[Svata Dedic]

+1 (binding)

- sha + gpg signature checked
- tested on Ubuntu Linux 19.04 / KDE, works as expected

-Svata


Dne 12. 04. 21 v 17:19 Martin Balín napsal(a):

Dear community,

As discussed here some time ago I would like to release VSCode NetBeans 12.4 
Beta2 on VSCode marketplace.

Therefore I’m opening the voting for complimentary binaries. Source code was a 
part of previous 12.4 Beta2 voting organized and closed by Geertjan W. already. 
Thank you.

Build artefacts are here:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.4-beta2/

We are primarily voting on VSIX complimentary binaries available here:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.4-beta2/apache-netbeans-java-12.3.991.vsix

PGP signature and SHA 512 are available along the binaries:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.4-beta2/apache-netbeans-java-12.3.991.vsix.asc
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.4-beta2/apache-netbeans-java-12.3.991.vsix.sha512

Version of 12.4 Beta2 VSIX is 12.3.991 as VSCode does not support versions like 
“12.4.Beta2”.

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as 
usual. (Please justify -1.) Please mark your vote with (binding) if, and
only, if you're an Apache NetBeans PMC member to help with voting admin. Only 
respond if you are going to vote*, i.e., this is *NOT* a discussion thread.

Thank you,
Martin Balin





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 12.4 Beta 2

[Svata Dedic]

Hi,

+1 (binding)

* SHA512 ok
* GPG signature verified (geert...@apache.org)
* source contains LICENSE and NOTICE
* source builds into a binary with LICENSE + NOTICE (+3rd party) - JDK8 
used.


Happy testing,
-Svata


Dne 08. 04. 21 v 12:43 Geertjan Wielenga napsal(a):

Dear community,

Here's Apache NetBeans 12.4 Beta 2, a new vote thread, because in the
previous one we pointed to the convenience binary and SHA for the
convenience binary instead of the source and its SHA as the voting
artifact. We've created a new beta to fix one issue we had in Beta 1:

https://github.com/apache/netbeans/pull/2864

Please read the below and vote.

Note: Feature freeze for 12.4 is some way away (April 16), so please do go
ahead scheduling content for 12.4 and providing pull requests for that
purpose, with end of May being the release date for 12.4.

Build artifacts are available here:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.4-beta2/

https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/12.4-beta2/

They were built by the Jenkins pipeline, signed, and moved to their place
above:

https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release124/4/

We are primarily voting on:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.4-beta2/netbeans-12.4-beta2-source.zip

In the first two links above, you'll also find convenience binaries and
installers (though not for Mac OS X) are available too:

https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release124/4/artifact/dist/installers/

SHA512:

aa04f0610978aa23e4d82c92436abe0301f4a7117b4dfec22e96e86305dfc9acb0615ef215a9dd879bb93ceb8849e38e2ce7d3ffcae51d3bcf1c5cba6dc723e9

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.4-beta2/netbeans-12.4-beta2-source.zip.sha512

KEYS file:
https://downloads.apache.org/netbeans/KEYS

What's new in 12.4 so far:

https://github.com/apache/netbeans/milestone/12?closed=1

--

Voting Requirements

Before voting +1 you are required to download the signed source code
package, compile it as provided, and test the resulting executable on your
own platform, along with also verifying that the package meets the
requirements of the ASF policy on releases - see:

http://www.apache.org/legal/release-policy.html#management

In particular, you should (at least) follow these steps.

1. Download the artefact to be voted on and unzip it.

2. Check that the artefact does not contain any jar files, using find .
-type f -name "*.jar", except for:
 -
platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/empty.jar
 - enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar
 - enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar
 - enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar
 - enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar
 which are only JARs by their name

3. Verify the cryptographic signatures, the NOTICE and LICENSE file.

4. Build it using the README provided by the artifact.

5. Look in nbbuild/netbeans for the NetBeans installation created by the
build process and try running it.

As well as checking any artifact functions correctly, you should check that
it has been correctly signed by a PMC member, and that the source being
voted on is sufficient to build the relevant binary.

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as
usual. (Please justify -1.) Please mark your vote with (binding) if, and
only, if you're an Apache NetBeans PMC member to help with voting admin.

*Only respond if you are going to vote*, i.e., this is *NOT* a discussion
thread.

NetBeans 12.4 Beta 2 will be released if and when this vote passes.

Thank you to all contributors for all your hard work!

Geertjan and Neil
Release Managers for Apache NetBeans 12.4 Beta 2 (and beyond)




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Gradle Project Loading Changes, Call for Test/Review

[Svata Dedic]

Dne 31. 03. 21 v 17:31 Scott Palmer napsal(a):


That was exactly it.  Why don’t we just update the requirements to Ant 1.10.8 
and close that issue?

Scott


1/ the issue is closed/fixed already
2/ IMHO not worth to bump requirements now, but sooner or later we may 
need some new _feature_ of Ant ;)


-S.


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Error opening project - prime command

[Svata Dedic]

Dne 30. 03. 21 v 21:31 Svata Dedic napsal(a):
getSupportedActions() nor whether it is enabled. And PHP seems to be 


Really too late. Does check for enabled, but not for its existence. Sorry.

-S

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Error opening project - prime command

[Svata Dedic]

https://github.com/apache/netbeans/pull/2822

is the likely culprit; it does not check for the action being among 
getSupportedActions() nor whether it is enabled. And PHP seems to be 
'picky' for unknown/unhandled actions :)


I'll try to fix that tomorrow, too late today (or maybe Jarda will do 
earlier). If you file a JIRA issue, blocker for 12.4, it won't be 
forgotten for sure.


-S.

Dne 30. 03. 21 v 20:44 Bläsing, Matthias napsal(a):
[Resend to mailinglist (at some point I'll remeber to use the right 
option in thunderbird)]


Hi,


these PRs might be related:

https://github.com/apache/netbeans/pull/2795
https://github.com/apache/netbeans/pull/2816
https://github.com/apache/netbeans/pull/2822

Greetings

Matthias

Am 29.03.2021 um 20:57 schrieb Tomáš Procházka:

Hi,
running NetBeans from current master branch I got following error.
Compiled after clean with -Dcluster.config=php, select Open project 
and then select directory with PHP project and error is presented.


Tom

java.lang.AssertionError: prime
at 
org.netbeans.modules.php.project.PhpActionProvider.getCommand(PhpActionProvider.java:140) 

at 
org.netbeans.modules.php.project.PhpActionProvider.isActionEnabled(PhpActionProvider.java:135) 

at 
org.netbeans.modules.project.ui.ProjectChooserAccessory.countPrimable(ProjectChooserAccessory.java:349) 

at 
org.netbeans.modules.project.ui.ProjectChooserAccessory.access$100(ProjectChooserAccessory.java:66) 

at 
org.netbeans.modules.project.ui.ProjectChooserAccessory$1$1.run(ProjectChooserAccessory.java:251) 


at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:311)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:758)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at 
java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:74) 


at java.awt.EventQueue.dispatchEvent(EventQueue.java:728)
at 
org.netbeans.core.TimableEventQueue.dispatchEvent(TimableEventQueue.java:136) 

[catch] at 
java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:205) 

at 
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:116) 

at 
java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:109) 


at java.awt.WaitDispatchSupport$2.run(WaitDispatchSupport.java:190)
at java.awt.WaitDispatchSupport$4.run(WaitDispatchSupport.java:235)
at java.awt.WaitDispatchSupport$4.run(WaitDispatchSupport.java:233)
at java.security.AccessController.doPrivileged(Native Method)
at java.awt.WaitDispatchSupport.enter(WaitDispatchSupport.java:233)
at java.awt.Dialog.show(Dialog.java:1084)
at javax.swing.JFileChooser.showDialog(JFileChooser.java:758)
at javax.swing.JFileChooser.showOpenDialog(JFileChooser.java:656)
at 
org.netbeans.modules.project.ui.actions.OpenProject.show(OpenProject.java:105) 

at 
org.netbeans.modules.project.ui.actions.OpenProject.actionPerformed(OpenProject.java:78) 

at 
javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:2022)
at 
javax.swing.AbstractButton$Handler.actionPerformed(AbstractButton.java:2348) 

at 
javax.swing.DefaultButtonModel.fireActionPerformed(DefaultButtonModel.java:402) 

at 
javax.swing.DefaultButtonModel.setPressed(DefaultButtonModel.java:259)

at javax.swing.AbstractButton.doClick(AbstractButton.java:376)
at 
javax.swing.plaf.basic.BasicMenuItemUI.doClick(BasicMenuItemUI.java:842)
at 
javax.swing.plaf.basic.BasicMenuItemUI$Handler.mouseReleased(BasicMenuItemUI.java:886) 


at java.awt.Component.processMouseEvent(Component.java:6539)
at javax.swing.JComponent.processMouseEvent(JComponent.java:3324)
at java.awt.Component.processEvent(Component.java:6304)
at java.awt.Container.processEvent(Container.java:2239)
at java.awt.Component.dispatchEventImpl(Component.java:4889)
at java.awt.Container.dispatchEventImpl(Container.java:2297)
at java.awt.Component.dispatchEvent(Component.java:4711)
at 
java.awt.LightweightDispatcher.retargetMouseEvent(Container.java:4904)
at 
java.awt.LightweightDispatcher.processMouseEvent(Container.java:4535)

at java.awt.LightweightDispatcher.dispatchEvent(Container.java:4476)
at java.awt.Container.dispatchEventImpl(Container.java:2283)
at java.awt.Window.dispatchEventImpl(Window.java:2746)
at java.awt.Component.dispatchEvent(Component.java:4711)
at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:760)
at java.awt.EventQueue.access$500(EventQueue.java:97)
at java.awt.EventQueue$3.run(EventQueue.java:709)
at java.awt.EventQueue$3.run(EventQueue.java:703)
at java.security.AccessController.doPrivileged(Native Method)
at 

Re: Minimize NetBeans vs. LSP diferences was: Gradle "Run with Parameters"

[Svata Dedic]

Hi, Lazslo, Jardo,

Dne 11. 03. 21 v 10:32 Jaroslav Tulach napsal(a):

Hello Laszlo.

I do not think that having an LSP Gradle module for customizing actions
would mean a "fork".


...new module we are duplicating the amount of work and reducing the
synergy. If we go that path, then
it may happen that some features are going to be available only in
VSNetBeans. I would find that unfortunate.

[...]


True, there is a different UI in VSNetBeans to customize execution. However
there is nothing VSCode/LSP specific on that. The `java/java.lsp.server` is
just reusing the well established
https://bits.netbeans.org/12.0/javadoc/org-netbeans-modules-extexecution/org/netbeans/api/extexecution/startup/StartupExtender.html
requested by tools like JRebel & co. in the past. The startup extender is
an API implemented by Ant projects, Maven projects. By using it in

[...]

It would be great if this startup extender and the `ExplicitProcessParameters`
were also supported by Gradle projects. At least my assumption (when
approving #2731) was that it would happen eventually.


Yes, this was my assumption as well.

... thoughts on the topic are formalized in 
https://issues.apache.org/jira/browse/NETBEANS-5482


The PR will be ready for review shortly. Cummulatively with #2731 this 
took considerable effort and - including the communication delays, 
trying to give appropriate time for feedback or response - enormous 
length already.


-Svata



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 12.3 (vote candidate 1)

[Svata Dedic]

+1 (binding)

- SHAs and ASCs verified for binary, sources and NBMs
- checked LICENSE and NOTICE files
- built from sources on Ubuntu 19.04 / x86_64, Oracle JDK 8
- opened a project (maven), checked basic editing
- briefly checked the convenience binary; looks sane; LICENSE and NOTICE 
files present.


-Svata

Dne 27. 02. 21 v 11:21 Geertjan Wielenga napsal(a):

Dear community,

This is our first voting candidate for the 12.3 release of Apache NetBeans.
It is built off the same commit as 12.3-beta3. Please note all requirements
below for validating sources and convenience binaries before voting.

Apache NetBeans 12.3 constitutes all clusters in the Apache NetBeans Git
repository, which together provide the NetBeans Platform (i.e., the
underlying application framework), as well as all the modules that provide
the Java SE, Java EE, PHP, JavaScript and Groovy features of Apache
NetBeans.

Build artifacts are available here:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.3
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/12.3

We should probably have put them in a 'vc1' folder, rather than the root
folder, on the other hand, we're optimistic that multiple vote candidates
won't be needed. :-)

They were built by the Jenkins pipeline and moved to their place:
https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release123/14/

We are primarily voting on:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.3/netbeans-12.3-source.zip

SHA512:
22bc542432f5810692757178a8b2f6e7a5729e7a422e637beb22c80603f685345030db90dce5ddc467bd26659e48ddbc3cadaf4fab4d41a8bd7de421f030d67f

KEYS file:
https://downloads.apache.org/netbeans/KEYS

Associated with the primary source item we have, generated with the
pipeline mentioned above:

-- under https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.3
binaries associated with the source
netbeans-12.3-bin.zip
as well as update content under nbms folder

-- under
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/12.3
you will find the platform cluster build
netbeans-platform-12.3-bin.zip
netbeans-platform-12.3-source.zip

Release specific wiki page:
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+12.3



Voting Requirements

Before voting +1 you are required to download the signed source code
package, compile it as provided, and test the resulting executable on your
own platform, along with also verifying that the package meets the
requirements of the ASF policy on releases - see:

http://www.apache.org/legal/release-policy.html#management

In particular, you should (at least) follow these steps.

1. Download the artefact to be voted on and unzip it.

2. Check that the artefact does not contain any jar files, except for:
  -
platform/autoupdate.services/test/unit/src/org/netbeans/api/autoupdate/data/empty.jar
  - enterprise/glassfish.common/test/unit/data/nottaDir-4_1_2.jar
  - enterprise/glassfish.common/test/unit/data/subdir/nottaDir-5.0.jar
  - enterprise/payara.common/test/unit/data/nottaDir-4_1_2.jar
  - enterprise/payara.common/test/unit/data/subdir/nottaDir-5.0.jar
  which are only jars by their name

3. Verify the cryptographic signatures, the NOTICE and LICENSE file

4. Build it using the README provided by the artifact.

5. Look in nbbuild/netbeans for the NetBeans installation created by the
build process and try running it.

In addition to checking the sources, you should check the associated
convenience binary zips and nbms at the artifact links above. As well as
checking any artifact functions correctly, you should check that it has
been correctly signed by a PMC member, and that the source being voted on
is sufficient to build the relevant binary.

Separate votes will be held on other convenience binaries, including
installers and Maven artifacts. Those will be dependent on this vote
passing.

This vote is going to be open at least 72 hours, vote with +1, 0, and -1 as
usual. (Please justify -1)

Please mark your vote with (binding) only if you're an Apache NetBeans PMC
member to help with voting admin.

Only respond if you are going to vote, i.e., this is NOT a discussion
thread.

NetBeans 12.3 will be released if and when this vote passes.

Thank you to all contributors for all your hard work!

Geertjan and Neil
Release Managers for Apache NetBeans 12.3




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Gradle "Run with Parameters" [was: Re: Gradle fixes & heads up]

[Svata Dedic]

A sidenote: splitting the conversation, as it really deserves two 
threads. This one should discuss the proposed "Run with Parameters 
feature for gradle.


But the original thread ("Gradle fixes & heads up") contains also other 
stuff related to the existing stalled PRs[2],[3] - Laszlo, would you 
please look at the mail[1] again - I think there are still some 
questions unanswered that would help me to finish the implementation.


=

Dne 23. 02. 21 v 6:50 Laszlo Kishalmi napsal(a):


That was meant to be as, just another way of do the things which already 
can be done. It is possible for modules to register their own 
GradleActionMappingProvider which can return an command line for an 
action. Right now the only issue that the usage at this provider the 


GradleActionMappingProvider ... I could only find 
ProjectActionMappingProvider and GradleActionsProvider; I suppose it's 
ProjectActionMappingProvider as that one actually creates the 
implementation.


I saw a complete replacement as quite heavyweight ... but looking at the 
ProjectActionMappingProviderImpl, the impl is very lightweight (unlike 
Maven ;)).


So at worst, a supposed "LSP Gradle" module would provide a replacement 
for project run, debug, profile actions + suck (somehow) the rest of 
actions from standard Gradle support ?


Still I could need (somehow) to tunnel down to GradleDaemonExecutor so I 
could eventually affect its buildLauncher.setEnvironmentVariables() [see 
below]. Can you think of a feasible way ?


code treats as only one provider can be active at a given time and does 
not allow fallback chaining. (Probably introducing a lookup merger would 
do for that)




Also in Gradle run task does not really take arguments unless --debug-vm 
parameter processing shall be done in the Gradle build file instead.


Well, I though that --args="application arguments" can be passed on the 
commandline (documented since Gradle 4.9).


For client JVM arguments, this will be tougher. Searching through 
documentation, it MAY be possible to use JAVA_OPTS environemnt variable. 
According to the documentation, gradle daaemon would use that one when 
launching client JVM. Granted, this approach would be only applicable 
for Java execution at the moment.


The question is how can the IDE know / parse the default JVM args 
(applicationDefaultJvmArgs) so it can decorate it ?


Anyway, I am going to prototype it (somehow), maybe I've misunderstood 
the docs.


Let me put the question other way around. Imagine an action that allows 
the user to parametrize the application ad-hoc:


+-+
| |
| Mode:[Run v]}
| App parameters:  [.]|
| Extra VM params: [.]|
|
|[  OK  ]   [ Cancel] |
+-+

but written in a way *that can be scripted, or automated* from another 
module, so no GUI is displayed by the action itself (if it gets right 
instructions) - perhaps the caller has its own GUI. Can execute run, 
debug, profile, eventually even debug-single (if run on a file).


This action can now be implemented, depending on Project API + Execution 
API only and will work for Maven projects. I guess I could (and probably 
should, for consistency) change Ant projects to support the abstract 
'parameters' interface.


So let's try to explore how that could be achieved with Gradle. It may 
even require some specific property to be introduced in the project (its 
build.gradle), so this level of integration could work ! But that's 
"just" a matter of documentation for the supposed action (well, in our 
current case for the VSCode client).


Cheers,
-Svata

[1] 
https://lists.apache.org/thread.html/rdcf2ce3f11ee4a46bdeb030f9b8309570d9f5007a8b099f77445c06c%40%3Cdev.netbeans.apache.org%3E

[2] https://github.com/apache/netbeans/pull/2769
[3] https://github.com/apache/netbeans/pull/2768

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Gradle fixes & heads up

[Svata Dedic]

Dne 22. 02. 21 v 17:37 Laszlo Kishalmi napsal(a):
That's Ok, though I'm going to put the dev list in the cc. There is 
nothing secret on this, and I do not mind if someone else would give 
feedback on the topics. But at least these discussions are open.


Perfect. I sent it off the list just as a "wake-up ping", but the tech 
details should be discussed here.


1. NetBeans does not use tri-state checkboxes. Introducing one here 
would be a bit alien. Combo box would be Ok for the UI.


I though we've already agreed to change the UI to a combo - I'll do 
that, but if you have some preferred wording, please suggest, so we can 
avoid some iterations over that.


2. I would go as simple as it can be detecting the LSP (or just 
headlessness, by checking java.awt.headless property), for putting up 


Then I'd propose to use the 'branding API'. We had headlessness check on 
other places, either historically or introduced in early LSP 
implementation, and we are already converting those checks to checks for 
a brandable bundle key. A distributor assmebling the app then can tweak 
the behaviour the way needed.


I'd then keep the dialog re-implementation as it is in PR#2769, but let 
it include individual buttons (except cancel :) based on resource keys; 
the default would be just as in NB 12.3 - OK, Turst, Cancel. Would it be 
OK ?


That's a good question. First I'd like to ask what kind of usecases do 
we want to support. If it just a generic Gradle build command line 


For the LSP client, the usecase is just to "run user application" with 
parameters specified in a way native for the client. For example VScode 
has its own configuration (in ./.vscode) that its UI interacts with 
somehow From the perspective of LSP client (vscode) user, she/he may 
edit certain parameters in his/her favourite editor and use standard 
Run/Debug actions.


For other IDE users, this makes a possibility for maven/gradle/whatever 
other project to allow an action that launches an app with specific 
parameters without modifying the project files. Such an action is surely 
possible even now - with fully separated implementations in Maven / Ant 
/ Gradle. With the new API in place and supports done, the action UI can 
be shared.


I do not plan to implement such features at the moment, however.

decorator, then it's probably fine. What I would like to mention, that 
this might add a parallel path to the existing ActionMappingProvider API.


I thought about the feature as a decorator. Even the API is designed so 
that the ExplicitProcessParameters instructions *modify* the existing 
ones (append or replace).


Could you please elaborate more on the 'parallel path' concept ?

I was thinking the action mapping was much more powerful, and actually 
create a complete environment for the user code execution. Application 
arguments (or launcher aguments = VM params) is just a well-defined part 
of such action definition, which can be passed separately; if there was 
some well-defined concept of 'verbosity' or 'error level', that would 
fall into the same pattern. I believe that if such things are needed in 
the future, the ExplicitProcessParameters can be compatibly extended to 
cover it.


Regards,
-Svata


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 12.2 u2 VSCode Extension

[Svata Dedic]

Hi,

+1 (binding)

- sha512 checked
- signatures checked
- build succeeded
- vsix installable, works
- update centers point to 12.2

Let's work toghether to make the 12.3 release really smooth :)
-Svata


Dne 14. 02. 21 v 6:52 Jaroslav Tulach napsal(a):

Dear community,
please accept my apology for this emergency vote. The work on release 12.3
revealed a problem with autoupdate catalogs (see
https://github.com/apache/netbeans/pull/2757) which prevents existing
Apache NetBeans VSCode Extension to launch properly. That renders it
useless for all its early adopters and may negatively impact their
experience when using our technology. As such I have backported the
necessary changes, tagged them and I am calling for a vote for 12.2 u2
emergency update:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/netbeans-vscode-ext-12.2.2/netbeans-12.2.2-source.zip
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/netbeans-vscode-ext-12.2.2/netbeans-12.2.2-source.zip.asc
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/netbeans-vscode-ext-12.2.2/netbeans-12.2.2-source.zip.sha512

The sources are associated with a convenience binary containing the VSCode
extension file
for Apache NetBeans Language Server 12.2.2 extension:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/netbeans-vscode-ext-12.2.2/apache-netbeans-java-12.2.2.vsix
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/netbeans-vscode-ext-12.2.2/apache-netbeans-java-12.2.2.vsix.asc
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/netbeans-vscode-ext-12.2.2/apache-netbeans-java-12.2.2.vsix.sha512

The source ZIP as well as the `.vsix` file come from tag 12.2.2 in our
repository: https://github.com/apache/netbeans/tree/12.2.2 - e.g. from
commit 1fb82a99c5e633. The source ZIP has been produced by running `ant
build-source-config`. The `.vsix` file has been produced by
https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/290/ job run.
Both artifacts were signed by my 2021 GPG key.

To build the Apache NetBeans Language Server extension please follow the
instruction in [java/java.lsp.server/vscode/BUILD.md](https://github.com/
apache/netbeans/blob/c8e0cec5edcbfbd61f22e07eb92fcdbad17f345b/java/
java.lsp.server/vscode/BUILD.md), e.g.:

```bash
netbeans$ ant build
netbeans$ cd java/java.lsp.server
java.lsp.server$ ant build-vscode-ext
```

To test the resulting convenience `.vsix` file, please follow the [wiki
page](https://cwiki.apache.org/confluence/display/NETBEANS/
Apache+NetBeans+extension+for+Visual+Studio+Code) instructions that
describe
the typical scenarios the extension is supposed to support.


Let's the testing and voting start!
-jt




-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: Missing platform-launchers-12.2.zip?

[Svata Dedic]

Hi, Joerg, Christian,

in fact all the binaries are present at 
https://ftp.osuosl.org/pub/netbeans/binaries/ but are not linked from 
the web (see note at 
https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115507251).


If someone suggests a procedure how to refresh the index file info, I'll 
do that (neither README or confluence page gave a guidance). The 
'index.html*' files regenerated somehow today, but do not include link 
for the added files.


-Svata

Dne 27. 01. 21 v 16:55 Christian Oyarzun napsal(a):

Hi Joerg,

You are correct, it seems these binaries were never uploaded to
https://ftp.osuosl.org/pub/netbeans/binaries/.

I've created two bugs on JIRA to track this.

launchers: https://issues.apache.org/jira/browse/NETBEANS-5294

asm: https://issues.apache.org/jira/browse/NETBEANS-5295

--Christian

On Wed, Jan 27, 2021 at 9:48 AM Joerg Michelberger 
wrote:


Hi all,

in the 12.2 platform there was a switch from the
platform-launchers-10.0.zip to platform-launchers-12.2.zip. I have the
great pleasure since years to build the NetBeans platform in an offline
Windows environment. So I need to download the external libraries manually
and put them in my environment. As a source for the download of the
external libraries I use https://ftp.osuosl.org/pub/netbeans/binaries/.
I am not sure if this is the first place for the binaries, but in the past
the libraries were there.
For the 12.2 I missed the 3 asm dependencies there, which I could
compensate with an alternative source with the same jar fingerprint.
But the platform-launchers-12.2.zip is missing there.
12.1 refers to platform-launchers-10.0.zip which is there.

Is there a primary download source for these binaries, or is
platform-launchers-12.2.zip and the asm files missing there?

Cheers
Jörg Michelberger






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 12.2 u1 VSCode Extension

[Svata Dedic]

+1 (binding)

* verified source zip digests and signatures
* build from sources according to the instructions
* vsix contents corresponds to the vsix built on my machine
* LICENSE & NOTICES ok
* tested basic operations with the lang server (completion, refactor, 
build, execute, debug)


Dne 11. 01. 21 v 12:35 Jaroslav Tulach napsal(a):

Dear community,
many improvements have been made to [VSNetBeans](https://cwiki.apache.org/
confluence/display/NETBEANS/Apache+NetBeans+extension+for+Visual+Studio+Code)
during last few weeks. The fixes include stability improvements as well as many
new refactoring features and infrastructure enhancements[1].

To follow the gold open source rule to "release early, release offten" I've
just packed what has been done and I am calling for a vote on sources for
Apache NetBeans 12.2 u1:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/netbeans-vscode-ext-12.2.1/netbeans-12.2.1-source.zip
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/netbeans-vscode-ext-12.2.1/netbeans-12.2.1-source.zip.asc
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/netbeans-vscode-ext-12.2.1/netbeans-12.2.1-source.zip.sha512

As well as associated convenience binary containing the VSCode extension file
for Apache NetBeans Language Server 12.2.1 extension:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/netbeans-vscode-ext-12.2.1/apache-netbeans-java-12.2.1.vsix
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/netbeans-vscode-ext-12.2.1/apache-netbeans-java-12.2.1.vsix.asc
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/netbeans-vscode-ext-12.2.1/apache-netbeans-java-12.2.1.vsix.sha512

The source ZIP as well as the `.vsix` file come from tag 12.2.1 in our
repository: https://github.com/apache/netbeans/tree/12.2.1 - e.g. from commit
7220262.

The source ZIP has been produced by TLP job (I've just renamed it to contain
12.2.1 version):
https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/
release122/28/artifact/dist/netbeans/

The `.vsix` file has been produced by https://ci-builds.apache.org/job/
Netbeans/job/netbeans-vscode/257/ job run.

I've signed both files with my new GPG key (lost previous one during hard drive
crash) which can be found at the end of https://downloads.apache.org/netbeans/
KEYS - hopefully the signing went OK.

To build the Apache NetBeans Language Server extension please follow the
instruction in [java/java.lsp.server/vscode/BUILD.md](https://github.com/
apache/netbeans/blob/c8e0cec5edcbfbd61f22e07eb92fcdbad17f345b/java/
java.lsp.server/vscode/BUILD.md), e.g.:

```bash
netbeans$ ant build
netbeans$ cd java/java.lsp.server
java.lsp.server$ ant build-vscode-ext
```

To test the resulting or convenience `.vsix` file, please follow the [wiki
page](https://cwiki.apache.org/confluence/display/NETBEANS/
Apache+NetBeans+extension+for+Visual+Studio+Code) instructions that describe
the typical scenarios the extension is supposed to support.


Let's give us 72h for testing and voting. Thanks everyone who contributed and
everyone who supported this exceptional irregular 12.2 u1 release.

-jt

[1] Changelog is available https://github.com/apache/netbeans/blob/
c8e0cec5edcbfbd61f22e07eb92fcdbad17f345b/java/java.lsp.server/vscode/
CHANGELOG.md





-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans Language Server for VSCode 12.2 (vote candidate 2)

[Svata Dedic]

+1 (binding)

Installed on a pristine vscode profile, went smooth, completion was 
working. Tested on Linux Kubuntu 19.04 / x86_64


-Svata

Dne 25. 11. 20 v 9:31 Martin Balin napsal(a):

Dear community,

As suggested by Laszlo Kishalmi I've started a new thread to vote on 
Apache NetBeans Language Server VSCode extension convenience binary for 
12.2 release of Apache NetBeans. It is built off the main Apache 
NetBeans 12.2 voting candidate 2 which passed the voting recently.


Build description is here
https://github.com/apache/netbeans/blob/master/java/java.lsp.server/vscode/BUILD.md#building 



Build artifacts of NetBeans VSCode extension are available here:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.2.0/

The primary convenience binary is:
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.2.0/apache-netbeans-java-12.2.0-vc2.vsix 


SHA512:
297be45741aecf32d19e32c61214a8e56ca034a6594ddfd76e77761bac83a9af7747263e61f403753c18abb7918494600247e258061e8be4a5d526eedd25efeb 



Description how it can be used is here:
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+NetBeans+Extension+for+Visual+Studio+Code 



Please vote.

Thank you,
Martin Balin

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 12.2 (vote candidate 2)

[Svata Dedic]

+1 (binding)

* SHA512 of source zip checked
* verified netbeans-12.2-source.zip.asc signature
* LICENSE, NOTICE files present and contains expected content
* built from the sources
* the product contains LICENSE, NOTICE
* opened [java] project, built run, edited source
* verified netbeans-12.2-bin.zip.asc signature
* verified the LICENSE, NOTICE, DEPENDENCIES in the build product 
matches the netbeans-12.2-bin.zip contents

* verified nbm signatures

* downloaded netbeans-platform*
* sha512 checked for -bin and -source
* signatures verified for -bin and -source
* LICENSE, NOTICE, DEPENDENCIES present and look sane in both -bin and 
-source

* built from sources
* LICENSE, NOTICE, DEPENDENCIES in the build product match the ones in 
-bin.zip


Tested on kubuntu Linux 19.04 / x86_64, compiled and run using JDK 
1.8.0_241-b07


-Svata

Dne 21. 11. 20 v 9:06 Laszlo Kishalmi napsal(a):

Dear community,

This is our second voting candidate for the 12.2 release of Apache
NetBeans. It is built off the same commit as 12.2-rc3. Please note

Build artifacts are available here :
https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.2/vc2
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/12.2/vc2

They were built by the Jenkins pipeline and moved to their place :
https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release122/20/ 



We are primarily voting on :
https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.2/vc2/netbeans-12.2-source.zip 



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: building 12.2 vc1 from source

[Svata Dedic]

apache-rat-0.12.jar is the first binary (my) build downloads. It 
succeeded on my machine with build 11.0.5+10-LTS.


If the 1st binary fails, then it's quite likely you're experiencing some 
network issues, rather than a build error.


Doublecheck your network setup, if there's not a HTTP proxy (your 
environment does not define any - see http(s)_proxy in the log.


-S.

Dne 17. 11. 20 v 18:36 Glenn Holmer napsal(a):

On 11/17/20 10:57 AM, Matthias Bläsing wrote:

Am Dienstag, den 17.11.2020, 10:40 -0600 schrieb Glenn Holmer:

I tried building 12.2 vc1 from source under JDK 11.0.8 using Ant
1.10.9 with this command:

ant -Dpermit.jdk9.builds=true build

and got:

/mnt/common/netbeans-12.2-src/nbbuild/build.xml:72: Failed to
download binaries - see log message for the detailed reasons.

Did I take a wrong step? Where to find the mentioned log file?



The invocation looks sane. The build system downloads resources from
the https://netbeans.osuosl.org/ and maven central. There could be a
downtime of one of these or a temporary problem in your network
environment.

Errors while downloading should be displayed above the final message
you quoted. It might help to redirect the build log to a file:

ant -Dpermit.jdk9.builds=true build 2>&1 | tee build.log

Please retry the build and if it still fails, please provide the
build.log.


https://www.lyonlabs.org/build.log

Not out of disk space, and I did get seven files in ~/.hgexternalcache/.



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 12.2 (vote candidate 1)

[Svata Dedic]

+1 (binding)

* SHA512 of source zip checked
* verified netbeans-12.2-source.zip.asc signature
* LICENSE, NOTICE files present and contains expected content
* built from the sources
* the product contains LICENSE, NOTICE
* opened [java] project, built run, edited source
* verified netbeans-12.2-bin.zip.asc signature
* verified the LICENSE, NOTICE, DEPENDENCIES in the build product 
matches the netbeans-12.2-bin.zip contents

* verified nbm signatures

* downloaded netbeans-platform*
* sha512 checked for -bin and -source
* signatures verified for -bin and -source
* LICENSE, NOTICE, DEPENDENCIES present and look sane in both -bin and 
-source

* built from sources
* LICENSE, NOTICE, DEPENDENCIES in the build product match the ones in 
-bin.zip


Tested on kubuntu Linux 19.04 / x86_64

Thanks everyone involved in the release ! And special thanks to Laszlo 
for the improved release process.


-Svata

Dne 16. 11. 20 v 8:57 Laszlo Kishalmi napsal(a):

Dear community,

This is our first voting candidate for the 12.2 release of Apache
NetBeans. It is built off the same commit as 12.2-rc2. Please note
all requirements below for validating sources and convenience binaries
before voting.


[...]


Build artifacts are available here :
https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.2/vc1
https://dist.apache.org/repos/dist/dev/netbeans/netbeans-platform/12.2/vc1

We are primarily voting on :
https://dist.apache.org/repos/dist/dev/netbeans/netbeans/12.2/vc1/netbeans-12.2-source.zip 


KEYS file :
https://downloads.apache.org/netbeans/KEYS



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [LAZY CONSENSUS] Branching Change in the Release Process

[Svata Dedic]

Hi,

+1 from me. I was waiting for such a change towards more collaborative 
environment since the former release process was defined.


-S.

Dne 07. 10. 20 v 16:23 Laszlo Kishalmi napsal(a):

Dear all,

While the current release process we have seems to work, the review 
shows that the freeze on master branch takes longer than being 
convenient. So I'd propose a new freeze-less branching strategy for the 
release of 12.2.


On 15th of October, master will be branched, and two new branch would be 
created 'release122' and 'delivery'. From that point the following rules 
are applied to the PR-s:


PR-s wished to be included into the 12.2 release:
   - Based on the delivery branch
   - Shall be marked for Milestone 12.2
   - Add the RM of 12.2 to the reviewers (That would be me: @lkishalmi)

PR-s with features other fixes:
   - Based on the master branch
   - Shall be reviewed and merged the usual way
   - If possible stay aside from big cluster refactoring.


*The delivery branch will be merged into the master branch weekly by the 
RM.* Also it would be merged into the release122 branch for creating 
beta-s, rc and occasionally the release. After the release the delivery 
branch would be deleted. If there would be PR-s left for that branch, 
those would be rebased to master.


This is a lazy consensus vote thread. If no one raise concerns against 
it in 72 hours from now, this change will take effect, and I'll update 
the release management pages on the wiki with this change.


P.S.:

Right now it seems that creating the odd-named 'delivery' branch could 
be spared. We are going to test that during this release cycle. If we 
found no unresolveable issues around that, then the 12.3 cycle we would 
use the release123 branch directly for release specific PR-s.






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Fixing commit validation: ordering of MIME registrations

[Svata Dedic]

Hi,

I am trying to fix "commit-validation" test that (among other things) 
ensures some consistency in registration layers, in particular order of 
registrations in MIME Lookup.


The explanation got terribly long, so I put up a Wiki page, see 
https://cwiki.apache.org/confluence/display/NETBEANS/File+Ordering+Change+proposal 
for full details.


Short summary:
- there's NO WAY how to register a service in Editors/ (unspecified 
mimetype), that would pass current commit-validation
-  the unspecified mimetype ("") was specifically designed to define 
universal services, for all editors (without that, this is what the 
entire MIME inheritance is about)
- once some obscure module registers a service in "" MIME type, it is 
likely to force all distribution modules to use positions in their 
registrations from that time onwards.


POSSIBLE SOLUTIONS:
* Change test
* Define positions in the whole codebase + maintain
* Improve FileUtil.getOrder() contract

Again, please see 
https://cwiki.apache.org/confluence/display/NETBEANS/File+Ordering+Change+proposa 
for all the details.


Relevant PRs and branches:
* https://github.com/apache/netbeans/pull/2359
* https://github.com/apache/netbeans/pull/2360
* 
https://github.com/apache/netbeans/compare/master...sdedic:origin/bugfix/commitvalidation-fixes3


Please share your thoughts, help me select (or discover) the best (or at 
least effective) solution.


Thanks,
-Svata

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: AW: NETBEANS-1678: Option for coloring EOL - Could someone point at similar code?

[Svata Dedic]

Hi,

I do not follow exactly from the start, but ...

Dne 23. 06. 20 v 23:48 Dmitry Semikin napsal(a):

Nevertheless, meanwhile I updated the example implementation, so that it 
implements now HighlightsContainer directly instead of using OffsetsBag. If 
someone is interested it is still available on GitHub here: 
https://github.com/DmitrySemikin/nb-eol-highlighter



Looking at the impl, there will be slight performance issues, especially 
with large documents w/ lots of small lines (xml, html, ...).


You probably do not need to keep *complete* index of all EOLs in the 
text here; the HightlightSequence is only called for a limited amount of 
text that is visible during drawing.


If you do not modify directly the WhitespaceHighlighting, which computes 
the chunks lazily, consider using the OffsetsBag: callbacks like 
insertUpdate/removeUpdate may happen in any thread, while hightlight 
sequences are likely to execute in EDT thread. Your code is not 
thread-safe maintaining highlightsStartOffsets; at least, the 
EolHighlightSequence should get an immutable copy of the list.


As for concurrency: highlighters AFAIK collect events from document / 
other modifications and fire highlight change *at any time* even while 
the highlight sequence might be interated through by editor's painting 
code (from EDT) . I think the code that throws ConcurrentModException in 
your sequence will break things somewhat.



- Handle them together with whitespaces in WhitespaceHighlighting.java.
I'd suggest to incorporate the changes into WhitespaceHighlighting; the 
newline is always part of 'traling whitespace', although not painted by 
default.



- In the provided example the font settings are retrieved using 
“org.netbeans.api.settings.FontColorSettings.getFontColors()”. But I cannot 
easily find, where can I add my own setting “EOL”, so that it is configurable 
from the Options dialog?


Do you want to color EOLs separately from the regular 'traling 
whitespace', or do you want rather to include EOL character in the 
traling whitespace (when it is printed) ?



- When I change the background of the EOL symbol, this background spans till 
the very right edge of the text editor. Is it expected? In my opinion it does 
not look nice. Can it be fixed somehow? I tried to pass the option 
HighlightsContainer.ATTR_EXTENDS_EOL = Boolean.FALSE, but it did not help.


It's strange, but I could not find even a bit of code that _reads_ that 
attribute; maybe I missed something.


Note that EOL painting is quite peculiar: the character may or may not 
be displayed - which is handled by NewlineView that optionally paints 
the character. IMHO ATTR_EXTENDS_EOL should be handled there, since that 
code paints background to editorView.getMaxX() if the hightlight item 
covers the newline character.



- If this functionality is going to ever be integrated into Netbeans, how 
should it be implemented: as separate module, or as part of existing module?
IMHO the current state seems more like omission (combination: paint 
trailing whitespace + show nonprintables). So I think yes.



- If existing module, which one?

Whitespace stuff is handled in editor.lib2


- Are any automated tests needed for this particular case? What is considered 
to be useful to test?
Yes !! Absolutely. In this case, you need to check various the highlight 
layer + editor view paint combinations. To ensure the rest of line is 
NOT painted; you're likely the first after LONG time to use 
ATTR_EXTENDS_EOL = false.


-Svata

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: NetBeans tests and character encoding

[Svata Dedic]

Hi,

the IDE respects file.encoding property as the ultimate default, but 
usually(!) a file resides in a Project which can decide on the encoding 
(see e.g. org.netbeans.modules.maven.queries.MavenFileEncodingQueryImpl) 
or the DataObject (= file type) may have its own mechanism to detect 
encoding (xml, html).


For testing purposes, I'd suggest to place a FileEncodingQueryImpl into 
MockLookup in the tests, as here:

org.openide.text.DataEditorSupportEncodingTest

You could (I think) also hardcode the encoding for qa-functional/unit 
tests as

test-{unit,qa-functional}-sys-prop.file.encoding=UTF-8

in the module's (?) project.properties

IMHO, the mock lookup approach is "more polite" ;)

-Svata

Dne 23. 06. 20 v 20:29 Tomáš Procházka napsal(a):

Hi,

some tests fail on Windows when test file contains accented characters.

All files in NetBeans repository have UTF-8 encoding, but my Windows 7 
machine uses Windows-1252 encoding. Test files are then not read with 
correct encoding and test fails.


For example file 
https://github.com/apache/netbeans/blob/master/php/php.latte/test/unit/data/testfiles/indent/testIssue241118_01.latte 



I found that default encoding for java can be changed with parameter 
"-Dfile.encoding=UTF-8".


Is there any way how to force NetBeans build to use UTF-8 encoding?

Regards,

Tom


-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [NETBEANS-3346] Upgrade asm to 5.2+

[Svata Dedic]

Dne 06. 11. 19 v 16:17 Peter Hull napsal(a):

On Wed, 6 Nov 2019 at 15:13, Jose Ch  wrote:
For some reason I've got both 7.2 and 5.0.1 on the startup classpath -


Yes, that was it. You probably didn't do "ant clean" (neither did I). 
The NPE should be fixed by 
https://github.com/pepness/incubator-netbeans/pull/2


-S.

-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Re: [VOTE] Release Apache NetBeans 11.2 Linux Installer

[Svata Dedic]

+1 (binding)

Checksum matches.
Installer tested on Ubuntu 19.04 / KDE 5; on JDK 8; 11.0.5; 13 - 
consistent, working.


Similar findings as Laszlo, no blockers.

-Svata

Dne 25. 10. 19 v 17:47 reema.tan...@oracle.com napsal(a):

Hi,

Artifacts are available here:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1

Built using Jenkins job:

https://builds.apache.org/view/M-R/view/NetBeans/job/netbeans-installers/

Primary voting artifact:

https://dist.apache.org/repos/dist/dev/netbeans/netbeans/11.2-vc1/Apache-NetBeans-11.2-bin-linux-x64.sh 



SHA512:

a02206dc569ef00c2e08ecb799604a0cae21d9204894e9432a51ff89981266d097a6f5d0b7c3c90be663cfced5ead7f37f7fe286a2a0e1569c972178a89c3f9e 
Apache-NetBeans-11.2-bin-linux-x64.sh


KEYS file:

https://dist.apache.org/repos/dist/release/netbeans/KEYS

Installer build steps:

https://cwiki.apache.org/confluence/display/NETBEANS/Installer+Build+Steps

Please check that the artifact functions correctly and has been 
correctly signed by a PMC member.


This vote is going to be open at least 72 hours, vote with +1, 0, and -1 
as usual. Please mark your vote with (binding) if you're an Apache 
NetBeans PMC member.


Apache NetBeans 11.2 Linux Installer will be released if and when this 
vote passes.



Thanks,

Reema






-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.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.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists

Issues for NB 11.1 (was: Re: [Lazy Consensus] Release schedule)

[Svata Dedic]

Hi,

I want to ask - how should we mark issues which are intended to be 
solved in NetBeans 11.1 ?


Right now, I have:
https://issues.apache.org/jira/browse/NETBEANS-2361
https://issues.apache.org/jira/browse/NETBEANS-2565
https://issues.apache.org/jira/browse/NETBEANS-2577

Two of them are already fixed in master. We may need "11.1" version in 
JIRA so the issues can be marked as fixed for the upcoming release ?


Just to make sure: 11.1 will be released from the *master* branch, did I 
understand that well ?


Dne 23. 05. 19 v 11:21 Neil C Smith napsal(a):

* All commits to master are intended for the release - only required
PRs should be merged between feature-freeze and release dates.  Master


[...]

* Jan raised important point of whether freezing master hinders
development, and whether we need a "next" branch.  I would suggest we
start with freezing master and review after NB 11.1 release, but
during release process if it becomes a real problem.  Personally I



-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional commands, e-mail: dev-h...@netbeans.apache.org

For further information about the NetBeans mailing lists, visit:
https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists