date:20220114

út 11. 1. 2022 v 13:54 odesílatel Neil C Smith 
napsal:

> Hi,
>
> Anyone know if there's a non-hacky way to exclude a module from being
> included at all if building the IDE on JDK 8?


There was an agreement to require JDK-11 to build NetBeans code.


> I was under the
> impression there might be in the conversations about support of
> --release 11, but I now think I might have misinterpreted something
> that was said.
>
> Ideally all our tests would be building on JDK 11 now,


Our tests shall continue to run on JDK-8. There was no consensus to move
away from JDK-8 when running tests, as far as I can tell.

The ideal setup is shown at
https://github.com/apache/netbeans/blob/master/.github/workflows/ensure-jdk8.yml

E.g. build with JDK-11, but test on JDK-8. That's what needs to happen to
all CI jobs, before one can use `--release 11`.
-jt

Re: JavaFX classpath warning when building NB RCP with Maven

FYI: https://github.com/apache/netbeans/commit/1b96b56 & co.

It gets interpreted by the NetBeans runtime system.
-jt


čt 13. 1. 2022 v 21:30 odesílatel Jean-Marc Borer 
napsal:

>
> https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
>
> But still, it is a very special case here since I have never seen URL such
> as "%24%7Bjava.home%7D%2F/lib/ext/jfxrt.jar". ${xxx} is a dynamic value
> that shall be replaced at runtime. I really wonder if the manifest gets
> properly interpreted with such a construction.
>
> On Thu, Jan 13, 2022 at 8:25 PM Jean-Marc Borer  wrote:
>
> > True. Then the issue lies in the maven nbm plugin that doesn't understand
> > the URL escaping.
> >
> > I tested by manually modifying the manifest to restore the old values.
> The
> > warning message is gone.
> >
> > On Thu, Jan 13, 2022 at 7:04 PM Matthias Bläsing <
> > mblaes...@doppel-helix.eu> wrote:
> >
> >> Hi,
> >>
> >> Am Donnerstag, dem 13.01.2022 um 17:54 + schrieb Jean-Marc Borer:
> >> > When building my NB RCP application with Maven, I get:
> >> >
> >> > Could not resolve Class-Path item in
> >> > org.netbeans.api:org-netbeans-libs-javafx:nbm-file:RELEASE124, path
> >> > is:%24%7Bjava.home%7D/lib/ext/jfxrt.jar, skipping
> >> >
> >> > I checked the manifest of module org-netbeans-libs-javafx.jar
> >> > And actually I found:
> >> > 
> >> > OpenIDE-Module-Requires: org.openide.modules.ModuleFormat1
> >> > Class-Path: %24%7Bjava.home%7D/lib/ext/jfxrt.jar
> >> >
> >> > Which is an url encoded string of ${java.hom}/lib/ext/jfxrt.jar
> >> >
> >> > I build on zulu8.58.0.13-ca-fx-jdk8.0.312-win_x64\jre\lib\ext
> >> > where jfxrt.jar exists... and JFX works in the application later. Just
> >> > wondering why such warning is generated.
> >> >
> >> > I suspect that the Maven checker is somehow not understanding properly
> >> this
> >> > classpath entry in the manifest.
> >> >
> >> > Any idea?
> >>
> >> The commit that changes this is here:
> >>
> >>
> >>
> https://github.com/apache/netbeans/commit/1b96b56ac3bfda8bd9b97f36c25901e84289cb23
> >>
> >> And is part of this:
> >>
> >> https://github.com/apache/netbeans/pull/2761
> >>
> >> The TL;DR version is (if I remember correctly): the JAR File
> >> Specification says, that the Class-Path attribute is a list of URLs and
> >> since javac 11 this is actually enforced.
> >>
> >> Try this:
> >>
> >> new URI("%24%7Bjava.home%7D%2F/lib/ext/jfxrt.jar");
> >> new URI("${java.home}/lib/ext/jfxrt.jar");
> >>
> >> It blows for the second line.
> >>
> >> Hope that clears it up.
> >>
> >> 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
> >>
> >>
> >>
> >>
>

Re: Log4J and its consequences for NetBeans and open source in general

pá 14. 1. 2022 v 12:08 odesílatel Geertjan Wielenga 
napsal:

> Hi all,
>
> Some interesting reading:
>
> https://www.theregister.com/2022/01/13/opensource_apacheplc4x_payment/
>
>
> https://www.theregister.com/2021/12/14/log4j_vulnerability_open_source_funding/
>
> As established thus far, there is no impact on NetBeans for the log4j
> situation in terms of attack vectors, since NetBeans doesn't use v2 and the
> v1 scenario doesn't apply to NetBeans.
>
> However, there are other issues involved here, as described in the links
> above.
>
> When I see out of nowhere e-mails arriving here from addresses that we've
> never heard of, with domain names that are clearly large multinational
> enterprises, who we never hear of except now that there is potentially a
> security hole in the software they've been freeloading without contributing
> anything to, well, it's unacceptable. And we never hear from those e-mail
> addresses again after calming their concern, until the next time, etc.
>

+1


> For me personally, I may be arriving at a situation where I'm going to be
> ignoring e-mails clearly coming from corporations and (to avoid those
> people switching to gmail accounts) to people not participating at all
> other than raising issues and demanding immediate assistance and asking for
> help in one way or another.
>
> The choices you have are simple: pay money to a commercial provider or pay
> time to the open source projects you're using. Time does not mean filing an
> issue and it does not mean writing a mail voicing your frustration. It
> means responding to other people when they have questions and at least
> investigating the issue you're reporting since after all you're a developer
> on all of NetBeans is on GitHub for you to investigate.
>
> I'm not writing this on behalf of the PMC but just under my own name and
> title. :-)
>

Apply lazy consensus and publish an official NetBeans blog post!

Eric:
> link / ...  to provide a way of donations

FYI: https://www.apache.org/foundation/contributing.html
-jt

Re: [DISCUSS] Compiling against internal JDK classes was: Let's require NetBeans to be built with JDK11

Hello Antonio,
I am changing the title to discuss usage of JDK internals.

> 1. Question I: "sun.awt/sun.swing" classes.

I suggest to avoid using the JDK internals as much as possible. E.g.

> B) comment/remove this jdk-internal specific features in NetBeans?

I'd encouraged you to rather create a pull request for OpenJDK project.
Small changes like https://github.com/openjdk/jdk/pull/3939 have a chance
to be integrated. Then NetBeans could rely on proper API rather than
continue to hack around JDK limitations.
-jt



pá 14. 1. 2022 v 8:26 odesílatel antonio  napsal:

> Hi all,
>
> Regarding the adoption of JDK 11 and the future stragety we want to
> follow, I have several questions:
>
> 1. Question I: "sun.awt/sun.swing" classes.
>
> We're using sun.awt and sun.swing classes in one "dlight" module we're
> receiving in the 4th/5th donation. This is because there is an
> implementation of BasicFileChooser for remote systems. These classes are
> _not_ exported in the new java.awt.desktop module.
>
> Do we want to:
>
> A) continue using these by adding some "--add-exports" to the build
> system to gain access to internal module classes?
>
> B) comment/remove this jdk-internal specific features in NetBeans?
>
> C) Use reflection (and possibly an "--add-opens", note this will have an
> ugly runtime dependency, not a build dependency).
>
> 2. Question II: Builds depend on the compiler, not the runtime.
>
> As Jaroslav points out in his email below, we're using Ant's " property/classname" ([2] for reference) in some places [1].
>
> This makes the build dependent on the version of our _compiler_, and not
> in on the version of our _target runtime_.
>
> Questions are:
>
> A) Is this correct? Do we want the build to depend on the version of our
> _compiler_?
>
> B) If not, do we want to add a:
> classpath="${nbjdk.bootclasspath}"
> property to these "available" Ant task so the build system depends on
> the target runtime?
>
> C) If so, is "nbjdk.bootclasspath" the correct property to use?
> "nbjdk.home" instead? Is there any other one? Do we want a new property
> "nb.target.jdk"?
>
>
> Any clarifications most welcome!
>
> Thanks,
> Antonio
>
>
> [1]
> A not exhaustive list:
>
> platform/applemenu:
>
> https://github.com/apache/netbeans/blob/d2ae8ba167c659458deca4a8cea3177af8450947/platform/applemenu/build.xml#L26
>
> nbi/engine:
>
> https://github.com/apache/netbeans/blob/d2ae8ba167c659458deca4a8cea3177af8450947/nbi/engine/build.xml#L74
>
> platform/openide.util.enumerations:
>
> https://github.com/apache/netbeans/blob/d2ae8ba167c659458deca4a8cea3177af8450947/platform/openide.util.enumerations/build.xml#L24
>
> ide/db:
>
> https://github.com/apache/netbeans/blob/d2ae8ba167c659458deca4a8cea3177af8450947/ide/db/build.xml#L30
>
>
> [2]
> https://ant.apache.org/manual/Tasks/available.html
>
> El 1/10/21 a las 16:44, Jaroslav Tulach escribió:
> >> I like this proposal in principle.
> >> In case i am missing something - what module would be a candidate for
> >> java.target=11 (as example)?
> >>
> > I see the applemenu module as a really nice example:
> >
> https://github.com/apache/netbeans/blob/master/platform/applemenu/build.xml#L26
> > it has two implementations of
> >
> https://github.com/apache/netbeans/blob/master/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapter.java
> > one is for JDK8 using some external binary Apple classes
> >
> https://github.com/apache/netbeans/blob/master/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK8.java
> > and the second is using official JDK9 API like `java.awt.desktop.
>
> -
> 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: Serious issue with the web site

2022-01-14 Thread Michael Bien


On 14.01.22 23:18, Brad Hards wrote:

On Saturday, 15 January 2022 5:28:17 AM AEDT antonio wrote:

All tutorials have this at the top:

"This tutorial needs a review. You can open a JIRA issue, or edit it in
GitHub following these contribution guidelines."

With a proper link to the documentation contribution guidelines, which
has a nice video explaining how to contribute (thanks, Gj!).

Sadly, it seems people is lazy enough to read the contribution
guidelines / watch the video, and prefer to send emails instead.

I did the review and updated some of them in the platform stream (new
screenshots, etc) about a year ago. So it is not quite true that they all have
it.

  However as an external contributor, I found it took a while for those PRs to
get reviewed and merged. So I moved on while I waited to see if I was doing it
right. I'm not suggesting that this is a common case (because I haven't seen a
lot of other people try it), just describing my impression.

Brad


the website repo might not be on the radar for many since it has low 
traffic and is not a code repo. If you think your PR is getting 
overlooked just ping someone directly or drop a mail here to speed 
things up.



-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

Re: Serious issue with the web site

2022-01-14 Thread Brad Hards

On Saturday, 15 January 2022 5:28:17 AM AEDT antonio wrote:
> All tutorials have this at the top:
> 
> "This tutorial needs a review. You can open a JIRA issue, or edit it in
> GitHub following these contribution guidelines."
> 
> With a proper link to the documentation contribution guidelines, which
> has a nice video explaining how to contribute (thanks, Gj!).
> 
> Sadly, it seems people is lazy enough to read the contribution
> guidelines / watch the video, and prefer to send emails instead.
I did the review and updated some of them in the platform stream (new 
screenshots, etc) about a year ago. So it is not quite true that they all have 
it.

 However as an external contributor, I found it took a while for those PRs to 
get reviewed and merged. So I moved on while I waited to see if I was doing it 
right. I'm not suggesting that this is a common case (because I haven't seen a 
lot of other people try it), just describing my impression.

Brad



-
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] Let's require NetBeans to be built with JDK11 was: reviving old thread

Not really familiar with the usage or code, but don't suppose
BasicFileChooserUI which is in java.desktop serves a similar purpose does
it?

Eric Bresie
ebre...@gmail.com


On Fri, Jan 14, 2022 at 2:49 PM antonio  wrote:

> Of course not. Otherwise we'd be using the java.desktop APIs :-).
>
> I believe this dependency with sun.swing and sun.awt internals was
> something that was added to NetBeans long ago [1], possibly to solve
> some bugs in JFileChooser in Windows back then.
>
> Cheers,
> Antonio
>
> [1]
>
> https://github.com/emilianbold/netbeans-releases/commit/33b45cbeada48c2b84bcd3283b8ae2366c0b9600#diff-ed4bc55bdf7e65b31bcff39ddde6083c8bc264946964025515b66a036b7ff007
>
>
> El 14/1/22 a las 20:58, Eric Bresie escribió:
> > Are the needed calls available in the java.desktop [1] module and/or the
> > applicable API associated [2] in it?
>
> -
> 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
>
>
>
>

Github Autolinking

>From a separate email thread:

Not sure if this would help in integration between existing systems but is
"autolink" enabled on github to ease references to NETBEANS JIRA tickets?
If not [enabled] and the github product (pro, enterprise, etc.) in use
allows its use, it seems like it might help a little to put in a ticket
reference which automatically links to the JIRA ticket. For more see
https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/managing-repository-settings/configuring-autolinks-to-reference-external-resources
Assume if setup with a prefix of NETBEANS pointing to a URL something like
https://issues.apache.org/jira/browse/NETBEANS- then references
starting with NETBEANS may automatically link up. That does assume a ticket
exists to do so.


So the use case is as a commenter while commenting in the github netbeans
project context, if referencing an existing JIRA ticket like "NETBEANS-123"
it would automatically add a link to the equivalent JIRA ticket.

There is still the question:

   1. What kind of "github product" is in use (i.e. pro, enterprise, etc.)?
   2. Is this a candidate for a NETBEANSINFRA ticket (
   https://issues.apache.org/jira/projects/NETBEANSINFRA ) or a request to
   github admin with privileges to enable this or a combination of both (i.e.
   need an NETBEANSINFRA ticket which would be performed by the github admin)?

Eric Bresie
ebre...@gmail.com

Re: Aw: Re: GitHub issues - initial templates and labels

2022-01-14 Thread Neil C Smith

On Fri, 14 Jan 2022, 20:42 Eric Bresie,  wrote:

> (2) it is different for a "Feature",
>

Yes, the forms are quite different.

Neil

Re: Log4J and its consequences for NetBeans and open source in general

Would it be worth putting a link / page maybe from the contribute" to
provide a way of donations and/or links to "service providers for hire for
Netbeans and/or Apache"?

Eric Bresie
ebre...@gmail.com


On Fri, Jan 14, 2022 at 9:56 AM antonio  wrote:

> Related (Apache PLC4x)
>
> "Your free trial version of “open-source” has expired, please update to
> a commercial plan"
>
> https://github.com/chrisdutz/blog/blob/main/plc4x/free-trial-expired.adoc
>
> Have fun,
> Antonio
>
> El 14/1/22 a las 14:06, antonio escribió:
> > Agreed!
> >
> > Now onto the task: let's kick butt and have fun!
> >
> > Cheers,
> > Antonio
> >
> > On 14/01/2022 12:07, Geertjan Wielenga wrote:
> >> For me personally, I may be arriving at a situation where I'm going to
> be
> >> ignoring e-mails clearly coming from corporations and (to avoid those
> >> people switching to gmail accounts) to people not participating at all
> >> other than raising issues and demanding immediate assistance and
> >> asking for
> >> help in one way or another.
> >>
> >> The choices you have are simple: pay money to a commercial provider or
> >> pay
> >> time to the open source projects you're using. Time does not mean
> >> filing an
> >> issue and it does not mean writing a mail voicing your frustration. It
> >> means responding to other people when they have questions and at least
> >> investigating the issue you're reporting since after all you're a
> >> developer
> >> on all of NetBeans is on GitHub for you to investigate.
>
> -
> 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] Let's require NetBeans to be built with JDK11 was: reviving old thread


Of course not. Otherwise we'd be using the java.desktop APIs :-).

I believe this dependency with sun.swing and sun.awt internals was 
something that was added to NetBeans long ago [1], possibly to solve 
some bugs in JFileChooser in Windows back then.


Cheers,
Antonio

[1]
https://github.com/emilianbold/netbeans-releases/commit/33b45cbeada48c2b84bcd3283b8ae2366c0b9600#diff-ed4bc55bdf7e65b31bcff39ddde6083c8bc264946964025515b66a036b7ff007


El 14/1/22 a las 20:58, Eric Bresie escribió:

Are the needed calls available in the java.desktop [1] module and/or the
applicable API associated [2] in it?


-
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: Re: GitHub issues - initial templates and labels

I added a few comments to the initial test issue [1].  Not sure if this is
of help.

Not sure if I missed it or if something was done by others, but I created a
test ticket for a Feature [2].I didn't see any of the suggested
"fields" (i.e. areas, priorities, etc.) on the create page; how do the
labels and other attributes get set?

Is this
(1) by design (i.e. these may not be included on initial creation but will
be added following triage by people with specific permissions),
(2) it is different for a "Feature", or
(3) something else is going on

In the template, would it be worth adding a link to a confluence page for
"help documentation" on how this is expected to be used?

Eric Bresie
ebre...@gmail.com

[1] https://github.com/codelerity/netbeans-issues-test/issues/1
[2] https://github.com/codelerity/netbeans-issues-test/issues/4

On Fri, Jan 14, 2022 at 11:09 AM Michael Bien  wrote:

> tbh I think we should probably make this a text field. Everyone looking
> at the report will have to second guess what "latest" means in context
> of the date. (I do know that it is mentioned in the guiding text that
> the reporter should mention the version somewhere - not sure if this is
> enough)
>
> alternatively we could periodically update the items on the combo box as
> you mentioned before - this might be interesting if we ever wanted to
> automatically label issues with a version label.
>
> I rarely see text fields for versions on issues, but i think it could be
> useful. e.g (12.3-12.6 and latest master)
>
> -mbien
>
> On 14.01.22 16:40, Christian Lenz wrote:
> > Hey Matthias,
> >
> > sure I got your point. I just gave my opinion and see also problems when
> we will not have this.
> > I think it will be just fine to talk to the people and let them know
> enough that they shouldn't expect anything at all.
> >
> >
> > Cheers
> >
> > Chris
> >
> >> Gesendet: Freitag, 14. Januar 2022 um 12:19 Uhr
> >> Von: "Neil C Smith" 
> >> An: dev@netbeans.apache.org
> >> Betreff: Re: GitHub issues - initial templates and labels
> >>
> >> On Wed, 12 Jan 2022 at 21:09, Benjamin Asbach  wrote:
> >>> I'm a little bit curious how this "latest Release" field is supposed to
> >>> work? Is this moved automatically when a new release was pumped out?
> >> No, nothing is moved automatically.  Bear in mind that the forms here
> >> only structure the text that the poster submits, ensuring they have to
> >> fill in some information, and giving them guidance as they do.  It's
> >> still text at the end of the day, which has its pros and cons.
> >>
> >> All metadata (milestone, labels, etc.) is committer only access.
> >> Although we can do various things with parsing text to labels, etc.
> >> automatically if we really find we need to.
> >>
> >> Now, on the version specifically, I didn't copy Airflow's form exactly
> >> because that involves adding each version manually.  We also need to
> >> know whether it's a bug in a release candidate or daily build.  And I
> >> wanted to put something top of the form that's clear that if it's not
> >> a bug in the latest release or later build, it's the person posting
> >> the bug's job to check.
> >>
> >> I'm not sure what's there is correct - we can easily change it for
> >> future issues if it proves problematic.
> >>
> >> Also I noticed in the bug you opened and closed that you selected
> >> Third-party package.  I'm curious what that is, and whether that field
> >> selection makes sense / needs work too?
> >>
> >> 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
>
>
>
>

Re: [DISCUSS] Let's require NetBeans to be built with JDK11 was: reviving old thread

I'm sure some of this is a repeat but...

Eric Bresie
ebre...@gmail.com


On Fri, Jan 14, 2022 at 1:26 AM antonio  wrote:

> Regarding the adoption of JDK 11 and the future stragety we want to
> follow, I have several questions:
>
> 1. Question I: "sun.awt/sun.swing" classes.
>
> We're using sun.awt and sun.swing classes in one "dlight" module we're
> receiving in the 4th/5th donation. This is because there is an
> implementation of BasicFileChooser for remote systems. These classes are
> _not_ exported in the new java.awt.desktop module.
>

Are the needed calls available in the java.desktop [1] module and/or the
applicable API associated [2] in it?


> Do we want to:
>
> A) continue using these by adding some "--add-exports" to the build
> system to gain access to internal module classes?
>
> B) comment/remove this jdk-internal specific features in NetBeans?
>

if I'm not mistaken, I believe that was one of the driving intents of
modularity to move away from internal APIs

>From JEP 396 in JDK 16 [3]

   -

   Encourage developers to migrate from using internal elements to using
   standard APIs, so that both they and their users can upgrade without fuss
   to future Java releases.


C) Use reflection (and possibly an "--add-opens", note this will have an
> ugly runtime dependency, not a build dependency).
>

Not immediate concern but I believe there are future plans on updates in
reflections [4] so be aware.

There are plenty of resources for migrating out there [5] [6] [7] [10] [11].

Have to be mindful of API deprecation/removals  [8], like javax.xml which
was deprecated in Java 9 then removed in Java 11

Tried to document some of these sorts of things here [9]

Cheers

References
[1]
http://cr.openjdk.java.net/~iris/se/10/pfd/java-se-10-pfd-spec-01/api/java.desktop-summary.html
[2]
http://cr.openjdk.java.net/~iris/se/10/pfd/java-se-10-pfd-spec-01/api/java/awt/desktop/package-summary.html

[3] http://openjdk.java.net/jeps/396 JEP 396: Strongly Encapsulate JDK
Internals by Default
[4] https://openjdk.java.net/jeps/416
[5] https://www.infogain.com/blog/java-8-to-11-a-migration-story/
[6]
https://stackoverflow.com/questions/60166816/migrating-java-8-project-to-java-11
[7]
https://medium.com/@daniel.panagio18/first-steps-of-migrating-from-java-8-to-java-11-98ea9a5eafff
[8] https://docs.oracle.com/en/java/javase/11/docs/api/deprecated-list.html
[9] https://issues.apache.org/jira/browse/NETBEANS-5349
[10] https://docs.oracle.com/en/java/javase/11/migrate/index.html
[11] https://docs.oracle.com/javase/9/migrate/toc.htm

[NETBEANS-189] Updates for Sql autocomplete / [NETBEANS-5831] Create a SQL Standard Quoter for Use with Connectionless Cases / PR-3074

Regarding
[NETBEANS-189] Updates for Sql autocomplete

The original ticket had this child ticket created which is also included as
part of the request.
[NETBEANS-5831] Create a SQL Standard Quoter for Use with Connectionless
Cases

Based on input from Matthias (thanks for the help), I updated and believe
the PR (https://github.com/apache/netbeans/pull/3074) is ready.

Eric Bresie
ebre...@gmail.com

Re: [VOTE] Release Apache NetBeans VSCode extension 12.6.301

2022-01-14 Thread Martin Entlicher

+1 (binding)

Signatures checked, the built extension tested on Linux.
Projects creation, ordinary editing/debugging and GraalVM's native image 
debugging.

Martin

From: Martin Balin 
Sent: Thursday, January 13, 2022 09:29
To: dev@netbeans.apache.org 
Subject: [External] : [VOTE] Release Apache NetBeans VSCode extension 12.6.301

Dear community,
let's update the Apache NetBeans Language Server extension on VSCode 
Marketplace with significantly improved version 12.6.301
https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.6.301/__;!!ACWV5N9M2RV99hQ!d8Tg714VISIxL7F-odw9Ak4tw3loB2sEXslrTHidLSnGQAEAKgwGv30Tb1iLfiho8mkx$

The primary voting artifact is the source
https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.6.301/apache-netbeans-java-12.6.301-src.zip__;!!ACWV5N9M2RV99hQ!d8Tg714VISIxL7F-odw9Ak4tw3loB2sEXslrTHidLSnGQAEAKgwGv30Tb1iLfnMzZixy$
built from branch ‘vsnetbeans_preview_1263`
SHA-512 sum is:
574ef054fe1c792e3f090799122a7269af3fcebe916dc70f9421694fb340b18a94ecd38649ba6e19c5d26e3be339d87eaf431c3abf98cd35a18ac6d1c077134a
and PGP signature: 
https://urldefense.com/v3/__https://dist.apache.org/repos/dist/dev/netbeans/netbeans-vscode-ext/12.6.301/apache-netbeans-java-12.6.301-src.zip.asc__;!!ACWV5N9M2RV99hQ!d8Tg714VISIxL7F-odw9Ak4tw3loB2sEXslrTHidLSnGQAEAKgwGv30Tb1iLfgxEhuzJ$

Binary artifacts were built by 
https://urldefense.com/v3/__https://ci-builds.apache.org/job/Netbeans/job/netbeans-vscode/807/__;!!ACWV5N9M2RV99hQ!d8Tg714VISIxL7F-odw9Ak4tw3loB2sEXslrTHidLSnGQAEAKgwGv30Tb1iLfgHCZSGa$

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://urldefense.com/v3/__https://raw.githubusercontent.com/apache/netbeans-jenkins-lib/0f4c351e89e1945ae440f53d0ac7c2ba9c0acae4/meta/netbeansrelease.json__;!!ACWV5N9M2RV99hQ!d8Tg714VISIxL7F-odw9Ak4tw3loB2sEXslrTHidLSnGQAEAKgwGv30Tb1iLfjPquzmb$

tmp$ cd java/java.lsp.server

java.lsp.server$ ant build-vscode-ext -Dvsix.version=12.6.301 
-D3rdparty.modules=none 
-Dmetabuild.jsonurl=https://urldefense.com/v3/__https://raw.githubusercontent.com/apache/netbeans-jenkins-lib/0f4c351e89e1945ae440f53d0ac7c2ba9c0acae4/meta/netbeansrelease.json__;!!ACWV5N9M2RV99hQ!d8Tg714VISIxL7F-odw9Ak4tw3loB2sEXslrTHidLSnGQAEAKgwGv30Tb1iLfjPquzmb$

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/12.6.301/apache-netbeans-java-12.6.301.vsix__;!!ACWV5N9M2RV99hQ!d8Tg714VISIxL7F-odw9Ak4tw3loB2sEXslrTHidLSnGQAEAKgwGv30Tb1iLfgefojAS$
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

Re: Serious issue with the web site


All tutorials have this at the top:

"This tutorial needs a review. You can open a JIRA issue, or edit it in 
GitHub following these contribution guidelines."


With a proper link to the documentation contribution guidelines, which 
has a nice video explaining how to contribute (thanks, Gj!).


Sadly, it seems people is lazy enough to read the contribution 
guidelines / watch the video, and prefer to send emails instead.


Cheers,
Antonio

El 14/1/22 a las 18:59, Geertjan Wielenga escribió:

All the documents can be accessed by clicking the link to GitHub at the
bottom of the page.

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: Serious issue with the web site


On my way!

It seems the web archive is currently down, so'll have to wait a little 
bit to have those "dzone" links we're talking about.


Also there's some nice content at blogs.sun.com/blogs.oracle.com we may 
want to point to.


Cheers,
Antonio

El 14/1/22 a las 18:57, Geertjan Wielenga escribió:

Will you fix the issue or shall I? I know as much about it as you do.

Gj

On Fri, Jan 14, 2022 at 6:54 PM Jean-Marc Borer  wrote:


DONE https://issues.apache.org/jira/browse/NETBEANS-6390

On Fri, Jan 14, 2022 at 5:29 PM antonio  wrote:


Hi Jean-Marc,

You can either open a JIRA issue or send us a pull-request at
https://github.com/apache/netbeans-website/.

Kind regards,
Antonio

El 14/1/22 a las 18:07, Jean-Marc Borer escribió:

Hi,

While looking for documentation, I was browsing the apache web site and

it

seems seriously broken. When I follow the pages from
https://netbeans.apache.org/ I get:
https://netbeans.apache.org/kb/docs/platform.html
   where a lot of links are broken. Even the images where when I go

trough

google on page
https://netbeans.apache.org/kb/docs/platform/
the page is fine!!

Notice the difference? Currently the site is not properly browsable.

Only

google allows you to find the proper pages, if you know what you are
looking for...

The links to the previously package info are broken as well...



-
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: Serious issue with the web site

2022-01-14 Thread Jean-Marc Borer

The site that currently online is not the latest version. I compared the
sources. Not the same. The one on github master seems fine.

For example

https://raw.githubusercontent.com/apache/netbeans-website/master/netbeans.apache.org/src/content/kb/docs/platform/index.asciidoc

is supposed to render this page:

https://netbeans.apache.org/kb/docs/platform.html

but why does the one above not work and the following one yes:

https://netbeans.apache.org/kb/docs/platform/

Probably related the way asciidoctor generates its sites (sound familiar to
me). The .html file must an older one. However, the site still references
the old pages...

On Fri, Jan 14, 2022 at 5:53 PM Jean-Marc Borer  wrote:

> DONE https://issues.apache.org/jira/browse/NETBEANS-6390
>
> On Fri, Jan 14, 2022 at 5:29 PM antonio  wrote:
>
>> Hi Jean-Marc,
>>
>> You can either open a JIRA issue or send us a pull-request at
>> https://github.com/apache/netbeans-website/.
>>
>> Kind regards,
>> Antonio
>>
>> El 14/1/22 a las 18:07, Jean-Marc Borer escribió:
>> > Hi,
>> >
>> > While looking for documentation, I was browsing the apache web site and
>> it
>> > seems seriously broken. When I follow the pages from
>> > https://netbeans.apache.org/ I get:
>> > https://netbeans.apache.org/kb/docs/platform.html
>> >   where a lot of links are broken. Even the images where when I go
>> trough
>> > google on page
>> > https://netbeans.apache.org/kb/docs/platform/
>> > the page is fine!!
>> >
>> > Notice the difference? Currently the site is not properly browsable.
>> Only
>> > google allows you to find the proper pages, if you know what you are
>> > looking for...
>> >
>> > The links to the previously package info are broken as well...
>> >
>>
>> -
>> 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: Serious issue with the web site

2022-01-14 Thread Neil C Smith

On Fri, 14 Jan 2022 at 17:08, Jean-Marc Borer  wrote:
> When I follow the pages from
> https://netbeans.apache.org/ I get:
> https://netbeans.apache.org/kb/docs/platform.html

Follow which pages?  There is no direct link from the homepage to
there that I can tell.

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

Re: Serious issue with the web site

All the documents can be accessed by clicking the link to GitHub at the
bottom of the page.

Gj

On Fri, Jan 14, 2022 at 6:59 PM Eric Bresie  wrote:

> I believe a lot of the documents is in asciidoc format.
>
> As I recall a job is run to regenerate the web site based on this.
>
> Not familiar with how this is done but maybe some here knows better
>
> Get Outlook for iOS
> 
> From: Jean-Marc Borer 
> Sent: Friday, January 14, 2022 11:53:51 AM
> To: dev@netbeans.apache.org 
> Subject: Re: Serious issue with the web site
>
> DONE https://issues.apache.org/jira/browse/NETBEANS-6390
>
> On Fri, Jan 14, 2022 at 5:29 PM antonio  wrote:
>
> > Hi Jean-Marc,
> >
> > You can either open a JIRA issue or send us a pull-request at
> > https://github.com/apache/netbeans-website/.
> >
> > Kind regards,
> > Antonio
> >
> > El 14/1/22 a las 18:07, Jean-Marc Borer escribió:
> > > Hi,
> > >
> > > While looking for documentation, I was browsing the apache web site and
> > it
> > > seems seriously broken. When I follow the pages from
> > > https://netbeans.apache.org/ I get:
> > > https://netbeans.apache.org/kb/docs/platform.html
> > >   where a lot of links are broken. Even the images where when I go
> trough
> > > google on page
> > > https://netbeans.apache.org/kb/docs/platform/
> > > the page is fine!!
> > >
> > > Notice the difference? Currently the site is not properly browsable.
> Only
> > > google allows you to find the proper pages, if you know what you are
> > > looking for...
> > >
> > > The links to the previously package info are broken as well...
> > >
> >
> > -
> > 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: Serious issue with the web site

I believe a lot of the documents is in asciidoc format.

As I recall a job is run to regenerate the web site based on this.

Not familiar with how this is done but maybe some here knows better

Get Outlook for iOS

From: Jean-Marc Borer 
Sent: Friday, January 14, 2022 11:53:51 AM
To: dev@netbeans.apache.org 
Subject: Re: Serious issue with the web site

DONE https://issues.apache.org/jira/browse/NETBEANS-6390

On Fri, Jan 14, 2022 at 5:29 PM antonio  wrote:

> Hi Jean-Marc,
>
> You can either open a JIRA issue or send us a pull-request at
> https://github.com/apache/netbeans-website/.
>
> Kind regards,
> Antonio
>
> El 14/1/22 a las 18:07, Jean-Marc Borer escribió:
> > Hi,
> >
> > While looking for documentation, I was browsing the apache web site and
> it
> > seems seriously broken. When I follow the pages from
> > https://netbeans.apache.org/ I get:
> > https://netbeans.apache.org/kb/docs/platform.html
> >   where a lot of links are broken. Even the images where when I go trough
> > google on page
> > https://netbeans.apache.org/kb/docs/platform/
> > the page is fine!!
> >
> > Notice the difference? Currently the site is not properly browsable. Only
> > google allows you to find the proper pages, if you know what you are
> > looking for...
> >
> > The links to the previously package info are broken as well...
> >
>
> -
> 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: Serious issue with the web site

Will you fix the issue or shall I? I know as much about it as you do.

Gj

On Fri, Jan 14, 2022 at 6:54 PM Jean-Marc Borer  wrote:

> DONE https://issues.apache.org/jira/browse/NETBEANS-6390
>
> On Fri, Jan 14, 2022 at 5:29 PM antonio  wrote:
>
> > Hi Jean-Marc,
> >
> > You can either open a JIRA issue or send us a pull-request at
> > https://github.com/apache/netbeans-website/.
> >
> > Kind regards,
> > Antonio
> >
> > El 14/1/22 a las 18:07, Jean-Marc Borer escribió:
> > > Hi,
> > >
> > > While looking for documentation, I was browsing the apache web site and
> > it
> > > seems seriously broken. When I follow the pages from
> > > https://netbeans.apache.org/ I get:
> > > https://netbeans.apache.org/kb/docs/platform.html
> > >   where a lot of links are broken. Even the images where when I go
> trough
> > > google on page
> > > https://netbeans.apache.org/kb/docs/platform/
> > > the page is fine!!
> > >
> > > Notice the difference? Currently the site is not properly browsable.
> Only
> > > google allows you to find the proper pages, if you know what you are
> > > looking for...
> > >
> > > The links to the previously package info are broken as well...
> > >
> >
> > -
> > 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: Serious issue with the web site

2022-01-14 Thread Jean-Marc Borer

DONE https://issues.apache.org/jira/browse/NETBEANS-6390

On Fri, Jan 14, 2022 at 5:29 PM antonio  wrote:

> Hi Jean-Marc,
>
> You can either open a JIRA issue or send us a pull-request at
> https://github.com/apache/netbeans-website/.
>
> Kind regards,
> Antonio
>
> El 14/1/22 a las 18:07, Jean-Marc Borer escribió:
> > Hi,
> >
> > While looking for documentation, I was browsing the apache web site and
> it
> > seems seriously broken. When I follow the pages from
> > https://netbeans.apache.org/ I get:
> > https://netbeans.apache.org/kb/docs/platform.html
> >   where a lot of links are broken. Even the images where when I go trough
> > google on page
> > https://netbeans.apache.org/kb/docs/platform/
> > the page is fine!!
> >
> > Notice the difference? Currently the site is not properly browsable. Only
> > google allows you to find the proper pages, if you know what you are
> > looking for...
> >
> > The links to the previously package info are broken as well...
> >
>
> -
> 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: Serious issue with the web site


Hi Jean-Marc,

You can either open a JIRA issue or send us a pull-request at 
https://github.com/apache/netbeans-website/.


Kind regards,
Antonio

El 14/1/22 a las 18:07, Jean-Marc Borer escribió:

Hi,

While looking for documentation, I was browsing the apache web site and it
seems seriously broken. When I follow the pages from
https://netbeans.apache.org/ I get:
https://netbeans.apache.org/kb/docs/platform.html
  where a lot of links are broken. Even the images where when I go trough
google on page
https://netbeans.apache.org/kb/docs/platform/
the page is fine!!

Notice the difference? Currently the site is not properly browsable. Only
google allows you to find the proper pages, if you know what you are
looking for...

The links to the previously package info are broken as well...



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

Hi Danijel,

AFAIU this should work as follows:

1. NetBeans is built as a set of modules.

2. Each module has a "manifest.mf" file (see [1] for an example)

3. Some of these files have an entry named
"OpenIDE-Module-Localizing-Bundle" (see [2] for an example)

4. This means that the module has a "localizing bundle" which is a Java
bundle (properties file) such as [3] that you have to localize.

5. The NetBeans source code has a "l10n-kit" Ant task that you can run
to collect and group these localizing bundles.

5.1.- Clone the Apache NetBeans repo as in "Building from source" in [4].

5.2.- Run "ant l10n-kit" there. You should have the english version of
the kit to localize to your preferred language.

I think it's ages since we last run "l10n-kit", so it could be it
doesn't run well for you. If so please either

6.a) Try to send us a PR with improvements.

6.b) Open a ticket detailing the problem.

Hope this helps,
Antonio

[1]
https://github.com/apache/netbeans/blob/master/platform/core.ui/manifest.mf

[2]
https://github.com/apache/netbeans/blob/561409b8b64ce23a65b73a37e79305efd5d155f8/platform/core.ui/manifest.mf#L3

[3]
https://github.com/apache/netbeans/blob/master/platform/core.ui/src/org/netbeans/core/ui/resources/Bundle.properties

[4]
https://netbeans.apache.org/download/dev/index.html

El 14/1/22 a las 14:00, Danijel Mišanovič escribió:

Greetings all!

We have interest in localizing the platform to Slovenian language and we came
to a hold on how to continue. We managed to checkout
https://github.com/apache/netbeans-l10n build and prepare a few projects
(Italian, Polish) for which there were already some translation sources but we
are lost from where to get the English bundles that we would use as a base for
our Slovenian translation. Currently most of info on how to setup I got from
discussion from last year which we found here
https://www.mail-archive.com/dev@netbeans.apache.org/msg08390.html but as there
is no source localization files in netbeans-l10n-zip/src/ for English we don't
know what to use as a template for Slovenian language translations.

Best regards!

Danijel Mišanović

-
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] Let's require NetBeans to be built with JDK11 was: reviving old thread

2022-01-14 Thread Michael Bien

i would always vote for remove/replace if it causes so much dependency 
trouble (its "just" a file chooser, right?).


reducing complexity is important, esp for old projects.

-mbien


On 14.01.22 08:26, antonio wrote:

Hi all,

Regarding the adoption of JDK 11 and the future stragety we want to 
follow, I have several questions:


1. Question I: "sun.awt/sun.swing" classes.

We're using sun.awt and sun.swing classes in one "dlight" module we're 
receiving in the 4th/5th donation. This is because there is an 
implementation of BasicFileChooser for remote systems. These classes 
are _not_ exported in the new java.awt.desktop module.


Do we want to:

A) continue using these by adding some "--add-exports" to the build 
system to gain access to internal module classes?


B) comment/remove this jdk-internal specific features in NetBeans?

C) Use reflection (and possibly an "--add-opens", note this will have 
an ugly runtime dependency, not a build dependency).


2. Question II: Builds depend on the compiler, not the runtime.

As Jaroslav points out in his email below, we're using Ant's 
"

This makes the build dependent on the version of our _compiler_, and 
not in on the version of our _target runtime_.


Questions are:

A) Is this correct? Do we want the build to depend on the version of 
our _compiler_?


B) If not, do we want to add a:
classpath="${nbjdk.bootclasspath}"
property to these "available" Ant task so the build system depends on 
the target runtime?


C) If so, is "nbjdk.bootclasspath" the correct property to use? 
"nbjdk.home" instead? Is there any other one? Do we want a new 
property "nb.target.jdk"?



Any clarifications most welcome!

Thanks,
Antonio


[1]
A not exhaustive list:

platform/applemenu:
https://github.com/apache/netbeans/blob/d2ae8ba167c659458deca4a8cea3177af8450947/platform/applemenu/build.xml#L26 



nbi/engine:
https://github.com/apache/netbeans/blob/d2ae8ba167c659458deca4a8cea3177af8450947/nbi/engine/build.xml#L74 



platform/openide.util.enumerations:
https://github.com/apache/netbeans/blob/d2ae8ba167c659458deca4a8cea3177af8450947/platform/openide.util.enumerations/build.xml#L24 



ide/db:
https://github.com/apache/netbeans/blob/d2ae8ba167c659458deca4a8cea3177af8450947/ide/db/build.xml#L30 




[2]
https://ant.apache.org/manual/Tasks/available.html

El 1/10/21 a las 16:44, Jaroslav Tulach escribió:

I like this proposal in principle.
In case i am missing something - what module would be a candidate for
java.target=11 (as example)?


I see the applemenu module as a really nice example:
https://github.com/apache/netbeans/blob/master/platform/applemenu/build.xml#L26 


it has two implementations of
https://github.com/apache/netbeans/blob/master/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapter.java 


one is for JDK8 using some external binary Apple classes
https://github.com/apache/netbeans/blob/master/platform/applemenu/src/org/netbeans/modules/applemenu/NbApplicationAdapterJDK8.java 


and the second is using official JDK9 API like `java.awt.desktop.


-
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: Aw: Re: GitHub issues - initial templates and labels

2022-01-14 Thread Michael Bien

tbh I think we should probably make this a text field. Everyone looking 
at the report will have to second guess what "latest" means in context 
of the date. (I do know that it is mentioned in the guiding text that 
the reporter should mention the version somewhere - not sure if this is 
enough)


alternatively we could periodically update the items on the combo box as 
you mentioned before - this might be interesting if we ever wanted to 
automatically label issues with a version label.


I rarely see text fields for versions on issues, but i think it could be 
useful. e.g (12.3-12.6 and latest master)


-mbien

On 14.01.22 16:40, Christian Lenz wrote:

Hey Matthias,

sure I got your point. I just gave my opinion and see also problems when we 
will not have this.
I think it will be just fine to talk to the people and let them know enough 
that they shouldn't expect anything at all.


Cheers

Chris


Gesendet: Freitag, 14. Januar 2022 um 12:19 Uhr
Von: "Neil C Smith" 
An: dev@netbeans.apache.org
Betreff: Re: GitHub issues - initial templates and labels

On Wed, 12 Jan 2022 at 21:09, Benjamin Asbach  wrote:

I'm a little bit curious how this "latest Release" field is supposed to
work? Is this moved automatically when a new release was pumped out?

No, nothing is moved automatically.  Bear in mind that the forms here
only structure the text that the poster submits, ensuring they have to
fill in some information, and giving them guidance as they do.  It's
still text at the end of the day, which has its pros and cons.

All metadata (milestone, labels, etc.) is committer only access.
Although we can do various things with parsing text to labels, etc.
automatically if we really find we need to.

Now, on the version specifically, I didn't copy Airflow's form exactly
because that involves adding each version manually.  We also need to
know whether it's a bug in a release candidate or daily build.  And I
wanted to put something top of the form that's clear that if it's not
a bug in the latest release or later build, it's the person posting
the bug's job to check.

I'm not sure what's there is correct - we can easily change it for
future issues if it proves problematic.

Also I noticed in the bug you opened and closed that you selected
Third-party package.  I'm curious what that is, and whether that field
selection makes sense / needs work too?

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

Serious issue with the web site

2022-01-14 Thread Jean-Marc Borer

Hi,

While looking for documentation, I was browsing the apache web site and it
seems seriously broken. When I follow the pages from
https://netbeans.apache.org/ I get:
https://netbeans.apache.org/kb/docs/platform.html
 where a lot of links are broken. Even the images where when I go trough
google on page
https://netbeans.apache.org/kb/docs/platform/
the page is fine!!

Notice the difference? Currently the site is not properly browsable. Only
google allows you to find the proper pages, if you know what you are
looking for...

The links to the previously package info are broken as well...

Re: Log4J and its consequences for NetBeans and open source in general


Related (Apache PLC4x)

"Your free trial version of “open-source” has expired, please update to 
a commercial plan"


https://github.com/chrisdutz/blog/blob/main/plc4x/free-trial-expired.adoc

Have fun,
Antonio

El 14/1/22 a las 14:06, antonio escribió:

Agreed!

Now onto the task: let's kick butt and have fun!

Cheers,
Antonio

On 14/01/2022 12:07, Geertjan Wielenga wrote:

For me personally, I may be arriving at a situation where I'm going to be
ignoring e-mails clearly coming from corporations and (to avoid those
people switching to gmail accounts) to people not participating at all
other than raising issues and demanding immediate assistance and 
asking for

help in one way or another.

The choices you have are simple: pay money to a commercial provider or 
pay
time to the open source projects you're using. Time does not mean 
filing an

issue and it does not mean writing a mail voicing your frustration. It
means responding to other people when they have questions and at least
investigating the issue you're reporting since after all you're a 
developer

on all of NetBeans is on GitHub for you to investigate.


-
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

Aw: Re: GitHub issues - initial templates and labels

2022-01-14 Thread Christian Lenz

Hey Matthias,

sure I got your point. I just gave my opinion and see also problems when we 
will not have this.
I think it will be just fine to talk to the people and let them know enough 
that they shouldn't expect anything at all.


Cheers

Chris

> Gesendet: Freitag, 14. Januar 2022 um 12:19 Uhr
> Von: "Neil C Smith" 
> An: dev@netbeans.apache.org
> Betreff: Re: GitHub issues - initial templates and labels
>
> On Wed, 12 Jan 2022 at 21:09, Benjamin Asbach  wrote:
> > I'm a little bit curious how this "latest Release" field is supposed to
> > work? Is this moved automatically when a new release was pumped out?
>
> No, nothing is moved automatically.  Bear in mind that the forms here
> only structure the text that the poster submits, ensuring they have to
> fill in some information, and giving them guidance as they do.  It's
> still text at the end of the day, which has its pros and cons.
>
> All metadata (milestone, labels, etc.) is committer only access.
> Although we can do various things with parsing text to labels, etc.
> automatically if we really find we need to.
>
> Now, on the version specifically, I didn't copy Airflow's form exactly
> because that involves adding each version manually.  We also need to
> know whether it's a bug in a release candidate or daily build.  And I
> wanted to put something top of the form that's clear that if it's not
> a bug in the latest release or later build, it's the person posting
> the bug's job to check.
>
> I'm not sure what's there is correct - we can easily change it for
> future issues if it proves problematic.
>
> Also I noticed in the bug you opened and closed that you selected
> Third-party package.  I'm curious what that is, and whether that field
> selection makes sense / needs work too?
>
> 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: Netbeans localization

Downloaded it here: http://www.ancestris.org/index.html#featured-services

And found many languages supported, a long list, but when a different
language is chosen, everything changes to that language except... the
NetBeans Platform parts.

Probably they'd be interested in fixing that, together with you, the idea
would be to see how they translated everything else and then see if we
could somehow hook into that.

Gj

On Fri, Jan 14, 2022 at 2:12 PM Geertjan Wielenga <
geertjan.wiele...@googlemail.com> wrote:

> Awesome! And welcome. :-)
>
> There's an interesting application on the NetBeans Platform called
> Ancestris: http://www.ancestris.org/index.html
>
> It comes in several languages: https://docs.ancestris.org
>
> I've been meaning to for a long time to get in touch with them to learn
> from them how they translate their tool (including the NetBeans Platform,
> somehow) to several different languages.
>
> That could be your starting point, i.e., I recommend reinventing the wheel
> from scratch because the repos you refer to above are suboptimal even if
> they were alive.
>
> Gj
>
>
>
> On Fri, Jan 14, 2022 at 2:01 PM Danijel Mišanovič 
> wrote:
>
>> Greetings all!
>>
>> We have interest in localizing the platform to Slovenian language and we
>> came to a hold on how to continue. We managed to checkout
>> https://github.com/apache/netbeans-l10n build and prepare a few projects
>> (Italian, Polish) for which there were already some translation sources but
>> we are lost from where to get the English bundles that we would use as a
>> base for our Slovenian translation. Currently most of info on how to setup
>> I got from discussion from last year which we found here
>> https://www.mail-archive.com/dev@netbeans.apache.org/msg08390.html but
>> as there is no source localization files in netbeans-l10n-zip/src/ for
>> English we don't know what to use as a template for Slovenian language
>> translations.
>>
>> Best regards!
>>
>> Danijel Mišanović
>>
>>

Re: Netbeans localization

Awesome! And welcome. :-)

There's an interesting application on the NetBeans Platform called
Ancestris: http://www.ancestris.org/index.html

It comes in several languages: https://docs.ancestris.org

I've been meaning to for a long time to get in touch with them to learn
from them how they translate their tool (including the NetBeans Platform,
somehow) to several different languages.

That could be your starting point, i.e., I recommend reinventing the wheel
from scratch because the repos you refer to above are suboptimal even if
they were alive.

Gj

On Fri, Jan 14, 2022 at 2:01 PM Danijel Mišanovič 
wrote:

> Greetings all!
>
> We have interest in localizing the platform to Slovenian language and we
> came to a hold on how to continue. We managed to checkout
> https://github.com/apache/netbeans-l10n build and prepare a few projects
> (Italian, Polish) for which there were already some translation sources but
> we are lost from where to get the English bundles that we would use as a
> base for our Slovenian translation. Currently most of info on how to setup
> I got from discussion from last year which we found here
> https://www.mail-archive.com/dev@netbeans.apache.org/msg08390.html but as
> there is no source localization files in netbeans-l10n-zip/src/ for English
> we don't know what to use as a template for Slovenian language translations.
>
> Best regards!
>
> Danijel Mišanović
>
>

Re: Log4J and its consequences for NetBeans and open source in general


Agreed!

Now onto the task: let's kick butt and have fun!

Cheers,
Antonio

On 14/01/2022 12:07, Geertjan Wielenga wrote:

For me personally, I may be arriving at a situation where I'm going to be
ignoring e-mails clearly coming from corporations and (to avoid those
people switching to gmail accounts) to people not participating at all
other than raising issues and demanding immediate assistance and asking for
help in one way or another.

The choices you have are simple: pay money to a commercial provider or pay
time to the open source projects you're using. Time does not mean filing an
issue and it does not mean writing a mail voicing your frustration. It
means responding to other people when they have questions and at least
investigating the issue you're reporting since after all you're a developer
on all of NetBeans is on GitHub for you to investigate.


-
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

Netbeans localization

2022-01-14 Thread Danijel Mišanovič

Greetings all!

We have interest in localizing the platform to Slovenian language and we came 
to a hold on how to continue. We managed to checkout 
https://github.com/apache/netbeans-l10n build and prepare a few projects 
(Italian, Polish) for which there were already some translation sources but we 
are lost from where to get the English bundles that we would use as a base for 
our Slovenian translation. Currently most of info on how to setup I got from 
discussion from last year which we found here 
https://www.mail-archive.com/dev@netbeans.apache.org/msg08390.html but as there 
is no source localization files in netbeans-l10n-zip/src/ for English we don't 
know what to use as a template for Slovenian language translations.

Best regards!

Danijel Mišanović

RE: [VOTE] Release Apache NetBeans VSCode extension 12.6.301

2022-01-14 Thread Eric Barboni

Hi
 -1 because of NOTICE file outdated.
 
Would have been ok otherwise.

Best Regards
Eric
 
-Message d'origine-
De : Jaroslav Tulach  
Envoyé : jeudi 13 janvier 2022 10:57
À : dev 
Objet : Re: [VOTE] Release Apache NetBeans VSCode extension 12.6.301

+1 (binding)

Checked SHA signatures. Checked .asc signatures. Used the complementary binary 
successfully. I also built from the source with (slightly changed ant command) 
successfully:
```bash
$ ant build -Dmetabuild.branch=release1263 -Dmetabuild.jsonurl= 
https://raw.githubusercontent.com/apache/netbeans-jenkins-lib/0f4c351e89e1945a
e440f53d0ac7c2ba9c0acae4/meta/netbeansrelease.json
$ cd java/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
```
A `.vsix` is created. I can install such `.vsix` into VSCode and use it on my 
JDK 1.8.0_301.
-jt

čt 13. 1. 2022 v 9:30 odesílatel Martin Balin 
napsal:

> 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:
>
> 574ef054fe1c792e3f090799122a7269af3fcebe916dc70f9421694fb340b18a94ecd3
> 8649ba6e19c5d26e3be339d87eaf431c3abf98cd35a18ac6d1c077134a
> 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/0f4c351e
> 89e1945ae440f53d0ac7c2ba9c0acae4/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/0f4c351e
> 89e1945ae440f53d0ac7c2ba9c0acae4/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
>  2.6.301/apache-netbeans-java-12.6.301.vsixSHA-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: Log4J and its consequences for NetBeans and open source in general

2022-01-14 Thread Brett Ryan

You just shook my tree to start contributing again, I have been a bit quiet
lately due to time constraints, but I do mean to get back on the horse.

On Fri, 14 Jan 2022 at 22:08, Geertjan Wielenga  wrote:

> Hi all,
>
> Some interesting reading:
>
> https://www.theregister.com/2022/01/13/opensource_apacheplc4x_payment/
>
>
> https://www.theregister.com/2021/12/14/log4j_vulnerability_open_source_funding/
>
> As established thus far, there is no impact on NetBeans for the log4j
> situation in terms of attack vectors, since NetBeans doesn't use v2 and the
> v1 scenario doesn't apply to NetBeans.
>
> However, there are other issues involved here, as described in the links
> above.
>
> When I see out of nowhere e-mails arriving here from addresses that we've
> never heard of, with domain names that are clearly large multinational
> enterprises, who we never hear of except now that there is potentially a
> security hole in the software they've been freeloading without contributing
> anything to, well, it's unacceptable. And we never hear from those e-mail
> addresses again after calming their concern, until the next time, etc.
>
> For me personally, I may be arriving at a situation where I'm going to be
> ignoring e-mails clearly coming from corporations and (to avoid those
> people switching to gmail accounts) to people not participating at all
> other than raising issues and demanding immediate assistance and asking for
> help in one way or another.
>
> The choices you have are simple: pay money to a commercial provider or pay
> time to the open source projects you're using. Time does not mean filing an
> issue and it does not mean writing a mail voicing your frustration. It
> means responding to other people when they have questions and at least
> investigating the issue you're reporting since after all you're a developer
> on all of NetBeans is on GitHub for you to investigate.
>
> I'm not writing this on behalf of the PMC but just under my own name and
> title. :-)
>
> Gj
>

Re: GitHub issues - initial templates and labels

2022-01-14 Thread Neil C Smith

On Wed, 12 Jan 2022 at 21:09, Benjamin Asbach  wrote:
> I'm a little bit curious how this "latest Release" field is supposed to
> work? Is this moved automatically when a new release was pumped out?

No, nothing is moved automatically.  Bear in mind that the forms here
only structure the text that the poster submits, ensuring they have to
fill in some information, and giving them guidance as they do.  It's
still text at the end of the day, which has its pros and cons.

All metadata (milestone, labels, etc.) is committer only access.
Although we can do various things with parsing text to labels, etc.
automatically if we really find we need to.

Now, on the version specifically, I didn't copy Airflow's form exactly
because that involves adding each version manually.  We also need to
know whether it's a bug in a release candidate or daily build.  And I
wanted to put something top of the form that's clear that if it's not
a bug in the latest release or later build, it's the person posting
the bug's job to check.

I'm not sure what's there is correct - we can easily change it for
future issues if it proves problematic.

Also I noticed in the bug you opened and closed that you selected
Third-party package.  I'm curious what that is, and whether that field
selection makes sense / needs work too?

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

Log4J and its consequences for NetBeans and open source in general