Re: [VOTE] Release Apache NetBeans 20

2023-11-30 Thread Junichi Yamamoto 
[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 11 on Ubuntu 22.04
(required)
[ ] I have tested the binary zip with  on 
[X] I have tested the DEB installer with OpenJDK 19 on Ubuntu 22.04
[ ] I have tested the Maven artefacts
[ ] I have tested the VSCode extension

Thanks, everyone,
Junichi
On Tue, Nov 28, 2023 at 6:47 PM Eric Barboni  wrote:
>
> This is our first voting candidate for the release of Apache NetBeans 20.
>
> Please follow the NEW voting template at the bottom of this email,
> and note all requirements below for validating sources and convenience
> binaries before voting.
>
> Apache NetBeans 19 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/20/
>
> They were built by the Jenkins pipeline :
>
> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/release200/16
> /
>
> 
>
> We are primarily voting on :
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/20/netbeans-20-sour
> ce.zip
>
> SHA512 :
> e795875918022541354213b03d7c4515db81c384f43d0b87029666583064e3093ca1a6ebe8f6
> ffa633c62d02a551be8df52703dfefb830efb8654558ddec5f28
>
> 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/20/
>
> Binaries associated with the source - netbeans-20-bin.zip as well as
> update content under the nbms folder.
>
> -- at
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans-installers/20/
>
> A PKG installer for macOS built and signed with NBPackage on a PMC member's
> macOS machine.
> An EXE installer for Windows signed by a PMC member using binaries created
> during the build process.
> DEB and RPM packages for Linux signed by a PMC member using binaries created
> with NBPackage during the build process.
>
> -- at
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/20.0/
>
> The VSCode extension signed by a PMC member using binaries created during
> the build process.
>
>
>
> Maven Artefacts
>
> The Maven artefacts for Apache NetBeans 20 are staged at :
>
> https://repository.apache.org/content/repositories/orgapachenetbeans-1137/
>
> The release of maven artefacts is based on a secondary build at
> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/release200/17
> / changing only the plugin nb-repository-plugin that was not populating
> pom.xml
>
> The version is : RELEASE200
>
> 
>
> 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 20 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

Re: Project dependencies - add/remove ability

2023-11-30 Thread Michael Bien 

Hi Svata,

lets say project A sets a dependency on project B and project 
dependencies are an IDE feature. How will project A build outside of the 
IDE?


And why is it not sufficient to (mvn) install the dependency into the 
local repo, and then depend on it the regular way?


I don't doubt that this can be useful but NB has a long tradition of not 
creating IDE dependent project structures. Other IDEs became less 
invasive too which makes picking an IDE no longer a team decision.


(I likely don't fully understand what the feature is since 
refactoring+hints were also mentioned)


best regards,
michael


On 29.11.23 20:22, Svata Dedic wrote:

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






-
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 20

2023-11-30 Thread Josh Juneau 
[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 Runtime Environment
11.0.14.1+1-LTS on Mac OS X version 14.1.1 running on x86_64
[ ] 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) - Tested Jakarta EE applications and deployment
to locally configured servers.

Thanks for all of the work on this release!

Josh Juneau


On Tue, Nov 28, 2023 at 3:47 AM Eric Barboni  wrote:

> This is our first voting candidate for the release of Apache NetBeans 20.
>
> Please follow the NEW voting template at the bottom of this email,
> and note all requirements below for validating sources and convenience
> binaries before voting.
>
> Apache NetBeans 19 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/20/
>
> They were built by the Jenkins pipeline :
>
>
> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/release200/16
> /
>
> 
>
> We are primarily voting on :
>
>
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans/20/netbeans-20-sour
> ce.zip
> 
>
> SHA512 :
>
> e795875918022541354213b03d7c4515db81c384f43d0b87029666583064e3093ca1a6ebe8f6
> ffa633c62d02a551be8df52703dfefb830efb8654558ddec5f28
>
> 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/20/
>
> Binaries associated with the source - netbeans-20-bin.zip as well as
> update content under the nbms folder.
>
> -- at
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans-installers/20/
>
> A PKG installer for macOS built and signed with NBPackage on a PMC member's
> macOS machine.
> An EXE installer for Windows signed by a PMC member using binaries created
> during the build process.
> DEB and RPM packages for Linux signed by a PMC member using binaries
> created
> with NBPackage during the build process.
>
> -- at
> https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/20.0/
>
> The VSCode extension signed by a PMC member using binaries created during
> the build process.
>
>
>
> Maven Artefacts
>
> The Maven artefacts for Apache NetBeans 20 are staged at :
>
> https://repository.apache.org/content/repositories/orgapachenetbeans-1137/
>
> The release of maven artefacts is based on a secondary build at
>
> https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/release200/17
> / changing only the plugin nb-repository-plugin that was not populating
> pom.xml
>
> The version is : RELEASE200
>
> 
>
> 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 20 will be released if and when this vote passes.
>
> ---
>
> Voting template
>
> Please copy and paste the answer form below into your

Re: /src/it/java and  /src/it/resources support

2023-11-30 Thread Benjamin Asbach 

On 2023-11-23 21:43, Alex Orlov wrote:

Hi all!
 
As I understand nobody reads NB github discussions so I will ask here. 
Could anyone say — why NB doesn’t support /src/it/java 
and /src/it/resources folders for integration tests and their 
resources? There is such issue  
https://issues.apache.org/jira/browse/NETBEANS-2470  but it seems to be 
obsolete.  Should it be reopened in github issue tracker or there is no 
chance that it will be fixed.

 
--
Best regards, Alex Orlov


I think it's not supported as this directory structure is most like used 
for maven plugin development [1]. So I guess the user base which are 
also using NetBeans are quite limited.


[1]: 
https://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html


-
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