JGIT failure

[Greenberg, Gary]

I need to add new feature to my project from last year.
Using NB 12.4 I did create a new branch in my local repo, made modification to 
couple classes,
but when I tried to build the project I got following exception in the build 
log:

evalCommit is [b0294507104d99294a3956fecfa6a8ec93c70184]
Tag refs [[]]
Created map: [{}]
Collected git.closest.tag.commit.count with value
Collected git.total.commit.count with value 44
Failed to perform fetch
org.eclipse.jgit.api.errors.TransportException: https://my-repo-url.git: 
Authentication is required but no CredentialsProvider has been registered
at org.eclipse.jgit.api.FetchCommand.call (FetchCommand.java:254)
at pl.project13.maven.git.JGitProvider.fetch (JGitProvider.java:352)
at pl.project13.maven.git.JGitProvider.getAheadBehind 
(JGitProvider.java:339)
at pl.project13.maven.git.GitDataProvider.lambda$loadGitData$17 
(GitDataProvider.java:174)
at pl.project13.maven.git.GitDataProvider.lambda$memoize$23 
(GitDataProvider.java:272)
at pl.project13.maven.git.GitDataProvider.lambda$loadGitData$18 
(GitDataProvider.java:175)
at pl.project13.maven.git.GitDataProvider.maybePut 
(GitDataProvider.java:255)
at pl.project13.maven.git.GitDataProvider.loadGitData 
(GitDataProvider.java:175)
at pl.project13.maven.git.GitCommitIdMojo.loadGitDataWithJGit 
(GitCommitIdMojo.java:604)
at pl.project13.maven.git.GitCommitIdMojo.loadGitData 
(GitCommitIdMojo.java:563)
at pl.project13.maven.git.GitCommitIdMojo.execute (GitCommitIdMojo.java:458)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo 
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:210)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:156)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute 
(MojoExecutor.java:148)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject 
(LifecycleModuleBuilder.java:81)
at 
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
 (SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute 
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:957)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:289)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:193)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke 
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke 
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced 
(Launcher.java:282)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch 
(Launcher.java:225)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode 
(Launcher.java:406)
at org.codehaus.plexus.classworlds.launcher.Launcher.main 
(Launcher.java:347)
Caused by: org.eclipse.jgit.errors.TransportException: 
https://ggree...@stash.trusted.visa.com:7990/scm/dpd29aa/resp_group_mgmt.git: 
Authentication is required but no CredentialsProvider has been registered
at org.eclipse.jgit.transport.TransportHttp.connect (TransportHttp.java:537)
at org.eclipse.jgit.transport.TransportHttp.openFetch 
(TransportHttp.java:362)
at org.eclipse.jgit.transport.FetchProcess.executeImp 
(FetchProcess.java:138)
at org.eclipse.jgit.transport.FetchProcess.execute (FetchProcess.java:124)
at org.eclipse.jgit.transport.Transport.fetch (Transport.java:1271)
at org.eclipse.jgit.api.FetchCommand.call (FetchCommand.java:243)
at pl.project13.maven.git.JGitProvider.fetch (JGitProvider.java:352)
at pl.project13.maven.git.JGitProvider.getAheadBehind 
(JGitProvider.java:339)
at pl.project13.maven.git.GitDataProvider.lambda$loadGitData$17 
(GitDataProvider.java:174)
at pl.project13.maven.git.GitDataProvider.lambda$memoize$23 
(GitDataProvider.java:272)
at pl.project13.maven.git.GitDataProvider.lambda$loadGitData$18 
(GitDataProvider.java:175)
at pl.project13.maven.git.GitDataProvider.maybePut 
(GitDataProvider.java:255)
at pl.project13.maven.git.GitDataProvider.loadGitData 
(GitDataProvider.java:175)
at pl.project13.maven.git.GitCommitIdMojo.loadGitDataWithJGit 
(GitCommitIdMojo.java:604)
at pl.project13.maven.git.GitCommitIdMojo.loadGitData 
(GitCommitIdMojo.java:563)
at pl.project13.maven.git.GitCommitIdMojo.execute (GitCommitIdMojo.java:458)
at 

Re: NetBeans Platform "Golden Path"

[Neil C Smith]

On Wed, 7 Jul 2021 at 21:19, Emilian Bold  wrote:
> 2. Use Maven and nbm-maven-plugin.
...
> 4. Once you have a zip file with the launchers it's super easy to make
> a macOS DMG and a Windows installer (using Inno Setup).

Mostly agree with Emi, but despite using Maven for most things, I do
still use Ant for some platform projects.  There are some useful tasks
in there, and customising the build/layout, or extending to do things
like template an InnoSetup script and build the installer directly
from the build script is quite easy.  I guess it comes down to how
"typical" your platform application will be.

Best wishes,

Neil

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

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

Re: NetBeans Platform "Golden Path"

[Emma Atkinson]

"The jlink tool links a set of modules, along with their transitive
dependencies, to create a custom runtime image."

JPMS is necessary if you want to use jlink, according to the oracle manual.
It is the reason I am migrating my old programs to JPMS as and when the
mood takes me.


On Thu, 8 Jul 2021, 13:50 Scott Palmer,  wrote:

> Use of jlink and jpackage does NOT require that you use JPMS.
>
> I have never made a “modular” application using JPMS, but I use jpackage
> all the time (but I wasn’t making NetBeans platform apps). You just need to
> know which modules from the JDK to include in the runtime, assuming you
> don’t need all of them.
>
> In my projects I use a custom Gradle task to run jlink and jpackage. It
> might be more difficult with Maven, but it should be possible.
>
> Scott
>
> > Additionally, although recent developments like jlink and jpackage have
> made it somewhat easier to produce stand-alone application bundles that
> don't require the user to first install a JRE, which is nice, it seems that
> these tools sometimes require the use of JPMS modules, which can be
> problematic in NetBeans (see above).
>
> -
> To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.org
> For additional commands, e-mail: users-h...@netbeans.apache.org
>
> For further information about the NetBeans mailing lists, visit:
> https://cwiki.apache.org/confluence/display/NETBEANS/Mailing+lists
>
>

RE: @Nonnull?

[Eirik Bakke]

For Maven, I think you can find these annotations here:


  javax.annotation
  javax.annotation-api
  1.3.2


From: Owen Thomas 
Sent: Friday, June 25, 2021 10:22 AM
To: NetBeans Mailing List 
Subject: Re: @Nonnull?

No Maven or Gradle. Ant only. :b

On Fri, 25 Jun 2021 at 17:34, Owen Thomas 
mailto:owen.paul.tho...@gmail.com>> wrote:
I've just been informed that @Nonnull could be part of javax (the documentation 
does appear to state this). I don't think I have access to this package because 
I'm not using anything other than the Java SE API.

Re: NetBeans Platform "Golden Path"

[Scott Palmer]

Use of jlink and jpackage does NOT require that you use JPMS.

I have never made a “modular” application using JPMS, but I use jpackage all 
the time (but I wasn’t making NetBeans platform apps). You just need to know 
which modules from the JDK to include in the runtime, assuming you don’t need 
all of them. 

In my projects I use a custom Gradle task to run jlink and jpackage. It might 
be more difficult with Maven, but it should be possible. 

Scott

> Additionally, although recent developments like jlink and jpackage have made 
> it somewhat easier to produce stand-alone application bundles that don't 
> require the user to first install a JRE, which is nice, it seems that these 
> tools sometimes require the use of JPMS modules, which can be problematic in 
> NetBeans (see above). 

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

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

Re: users Digest 7 Jul 2021 19:24:25 -0000 Issue 1288

[Bradley Willcott]

Chris,
As you say "(rightly or wrongly)" - though a compiled 'exe' is just as 
risky.  Java cannot be blamed for that sort of thing.
However, I have not dealt with paranoid end-users so I'll just leave it 
with you there.


When you do get your answers, I would be interested in seeing them 
also.  That is, if they aren't already posted to the list.


Regards,
Brad.

On 8/7/21 6:43 pm, Chris Olsen wrote:

Bradley and All --

   Thank you for the lengthy response and pom.  I would like to briefly respond 
to your comment below:

---
Separately, I don't see any issue with an end-user having to install a
version of the JRE to run Java applications.  In Windows, it is quite
easy, isn't it?
---

   My own efforts at freeware target statistics teachers.  Many school districts (rightly 
or wrongly) have the idea that Java is a huge security risk, and any Java program is 
immediately suspect.  Also, many districts do not have the expertise to install FX.  
Thus, bundling an app with a JRE slips in "under the radar."  (Teachers 
typically do not have admin privileges on their classroom computers, and I typically 
offer the source code for inspection; however, many Districts are bereft of expertise in 
that area also.)

   -- Chris




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

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

RE: NetBeans Platform "Golden Path"

[Eirik Bakke]

I agree with everything Emilian said in the other post. My own experience:

1) I have never tried JPMS.
2) Yes, maven-based NetBeans Platform projects work great. I switched my 
NetBeans Platform project to Maven several years ago, and haven't had any 
problems with it compared to ant.
3) Yes, each external library must be wrapped in a NetBeans wrapper module 
(which is usually just a folder with one pom.xml file and one manifest.mf 
file). Usually there is no need to download the JAR manually, if Maven can find 
it.
4) In my case I have a custom script which generates a ZIP file for 
distribution of the application for Linux, a ZIP file for Windows, and a DMG 
file with an application bundle for MacOS. The script uses the ZIP file 
generated from the NetBeans Platform build as its input. It also copies in a 
platform-appropriate JRE for each OS, and points the netbeans.conf (or 
myapp.conf or whatnot) file to it.

I never used the NetBeans-generated installers, although at some point I'll 
want to figure out how to build a proper installer on Windows. Though I might 
look into building an MSI rather than an EXE installer there. 

In recent Java versions, you need to use the jlink command to generate a 
customized JRE from the JDK (which involves figuring out which JDK modules your 
applications needs).

When bundling a JRE/JDK, avoid using the Oracle one, as it has some unpleasant 
license terms--you can use e.g. Zulu's JDK distro instead.

On MacOS it is now more-or-less mandatory to "notarize" the application bundle 
before distributing it. This requires an Apple developer subscription and a 
MacOS machine.

I have never used jpackage.

-- Eirik
https://twitter.com/ultorg

-Original Message-
From: Chris Marusich  
Sent: Wednesday, July 7, 2021 9:24 PM
To: users@netbeans.apache.org
Subject: NetBeans Platform "Golden Path"

Hi,

What's the current "best practice" or "golden path" for building and 
distributing a NetBeans Platform application and managing its dependencies 
(e.g., from Maven central)?  That's a big general question, so I'll ask some 
specifics:

- Should I ever try to use JPMS modules when building a NetBeans Platform 
application?  I've found that in my projects (which are NetBeans Maven-based 
projects, not NetBeans Platform projects), when I use JPMS modules, it can 
cause problems for NetBeans [1], so I wonder if it's really wise to even try 
mixing JPMS modules with NetBeans projects at this time, let alone NetBeans 
Platform projects.

- Should I ever try to make a Maven-based NetBeans Platform application?
I see there are Maven templates in NetBeans that offer to create a Maven-based 
NetBeans Platform project.  However, all the examples online and in books that 
I've seen so far do NOT use Maven.  In spite of this, recent emails on this 
list have suggested that Maven-based NetBeans projects are generally preferred 
over the older Ant-based project types.
So I'm a bit confused about what the currently prevailing wisdom on this matter 
is, in the case of NetBeans Platform projects.  Perhaps Maven can be used to 
build NetBeans Platform applications/modules or not, depending on the 
situation.  As a beginner in the world of NetBeans Platform, I just want to try 
making a NetBeans Platform project using whatever approach is more likely to 
work without trouble and remain supported by the community.  But what approach 
might that be?

- If I want to use a library that is available from Maven central in my 
NetBeans Platform application, is the best option to just manually download the 
JAR file, manually create a NetBeans Platform "wrapper module" for the JAR, and 
then use the "wrapper module" in my application?  I tried using the 
nbm-maven-plugin to use dependencies from Maven in a simple NetBeans Platform 
application, but I encountered problems and couldn't figure out how to get it 
to work.  So to me it feels like the answer to this question is "yes, at the 
moment you should manage your JARs manually in order to have the best developer 
experience when working on a NetBeans Platform application," but I'm not sure.  
I'm curious to hear the opinions of people who have more experience with the 
NetBeans Platform.

- If I want to build a stand-alone release of my NetBeans Platform application 
that I can distribute to an end user, what's a good way to do it?  It seems 
that some of the features in NetBeans that build a stand-alone release will 
only work when your project is not a Maven-based NetBeans Platform application. 
 Additionally, although recent developments like jlink and jpackage have made 
it somewhat easier to produce stand-alone application bundles that don't 
require the user to first install a JRE, which is nice, it seems that these 
tools sometimes require the use of JPMS modules, which can be problematic in 
NetBeans (see above).  And in any case NetBeans does not yet seem to expose any 
way to take advantage of these new tools.  So what IS the most common 

Re: users Digest 7 Jul 2021 19:24:25 -0000 Issue 1288

[Chris Olsen]

Bradley and All --

  Thank you for the lengthy response and pom.  I would like to briefly respond 
to your comment below:

---
Separately, I don't see any issue with an end-user having to install a 
version of the JRE to run Java applications.  In Windows, it is quite 
easy, isn't it?
---

  My own efforts at freeware target statistics teachers.  Many school districts 
(rightly or wrongly) have the idea that Java is a huge security risk, and any 
Java program is immediately suspect.  Also, many districts do not have the 
expertise to install FX.  Thus, bundling an app with a JRE slips in "under the 
radar."  (Teachers typically do not have admin privileges on their classroom 
computers, and I typically offer the source code for inspection; however, many 
Districts are bereft of expertise in that area also.)

  -- Chris


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

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

Re: HTML Disable Auto Completion 12.4

[John Lavelle]

Emi,

Many thanks for that. Any chance you can give me a "heads-up" on the xml
file name?

Best regards,
John
j...@jql.co.uk
Bike Farkles: https://www.youtube.com/channel/UCPRV92Cf_R1ihviRtVU2teQ
JLavelle.uk https://www.youtube.com/jlavelleuk


On Thu, Jul 8, 2021 at 9:30 AM Emilian Bold  wrote:

> Back when I was working on this each such settings had a property that
> was being saved by NetBeans. So, just because there's no UI for it it
> doesn't mean you can't make a simple module that tweaks that property
> or just hand-edit an XML in your userdir.
>
> So now, the questions just is how was that property called?
>
> You can probably learn it by just tweaking the property in an older
> NetBeand then diff-ing the files. I'd guess just copying the XML to
> the 12.4 user dir would do the trick.
>
> --emi
>
> On Thu, Jul 8, 2021 at 10:24 AM John Lavelle  wrote:
> >
> > BUMP! BUMP!
> >
> > I assume that no one uses HTML in NetBeans so has no experience of this?
> >
> > Any answers or suggestions?
> >
> > Regards
> > John
> >
> > BUMP!
> >
> > Can anyone shed any light on this?
> >
> > Thanks
> > John
> >
> > Hi,
> >
> > You used to be able to disable the Auto Completion pop-up for HTML by
> deleting (must be deleted not just disabled) the items in
> "Tools>Palette>Code Clips" (why?) then in "Tools>Options>Editor>Code
> Completion>HTML" deselecting "Auto Popup Completion Window".
> >
> > In 12.4 it seems the only way to disable Code Completion for HTML is to
> disable it for every language in the "All languages" Code Completion
> section.
> >
> > Is there a way to disable Code Completion just for one language as the
> "old" system no longer seems to work correctly?
> >
> > Best regards,
> > John
> > j...@jql.co.uk
> > Bike Farkles: https://www.youtube.com/channel/UCPRV92Cf_R1ihviRtVU2teQ
> > JLavelle.uk https://www.youtube.com/jlavelleuk
>

Re: NetBeans Platform "Golden Path"

[Jerome Lelasseux]

 Chris,
I devevelop an Ant-based Netbeans platform application 
(https://github.com/jjazzboss/JJazzLab-X) and had to follow this path too. 

I use only 2 external libraries that are packed in wrapper modules. I let 
Netbeans build the launchers and I have a shell script that prepare the 
packages for each OS, bundling a JRE (I was hesitant at first, it adds ~40MB, 
but in the end it works well, most of my users don't even know it's a Java 
app), using Innosetup with code signing for Win, and zip for Linux and Mac.

Jerome

Le mercredi 7 juillet 2021 à 21:24:30 UTC+2, Chris Marusich 
 a écrit :  
 
 Hi,

What's the current "best practice" or "golden path" for building and
distributing a NetBeans Platform application and managing its
dependencies (e.g., from Maven central)?  That's a big general question,
so I'll ask some specifics:

- Should I ever try to use JPMS modules when building a NetBeans
Platform application?  I've found that in my projects (which are
NetBeans Maven-based projects, not NetBeans Platform projects), when I
use JPMS modules, it can cause problems for NetBeans [1], so I wonder if
it's really wise to even try mixing JPMS modules with NetBeans projects
at this time, let alone NetBeans Platform projects.

- Should I ever try to make a Maven-based NetBeans Platform application?
I see there are Maven templates in NetBeans that offer to create a
Maven-based NetBeans Platform project.  However, all the examples online
and in books that I've seen so far do NOT use Maven.  In spite of this,
recent emails on this list have suggested that Maven-based NetBeans
projects are generally preferred over the older Ant-based project types.
So I'm a bit confused about what the currently prevailing wisdom on this
matter is, in the case of NetBeans Platform projects.  Perhaps Maven can
be used to build NetBeans Platform applications/modules or not,
depending on the situation.  As a beginner in the world of NetBeans
Platform, I just want to try making a NetBeans Platform project using
whatever approach is more likely to work without trouble and remain
supported by the community.  But what approach might that be?

- If I want to use a library that is available from Maven central in my
NetBeans Platform application, is the best option to just manually
download the JAR file, manually create a NetBeans Platform "wrapper
module" for the JAR, and then use the "wrapper module" in my
application?  I tried using the nbm-maven-plugin to use dependencies
from Maven in a simple NetBeans Platform application, but I encountered
problems and couldn't figure out how to get it to work.  So to me it
feels like the answer to this question is "yes, at the moment you should
manage your JARs manually in order to have the best developer experience
when working on a NetBeans Platform application," but I'm not sure.  I'm
curious to hear the opinions of people who have more experience with the
NetBeans Platform.

- If I want to build a stand-alone release of my NetBeans Platform
application that I can distribute to an end user, what's a good way to
do it?  It seems that some of the features in NetBeans that build a
stand-alone release will only work when your project is not a
Maven-based NetBeans Platform application.  Additionally, although
recent developments like jlink and jpackage have made it somewhat easier
to produce stand-alone application bundles that don't require the user
to first install a JRE, which is nice, it seems that these tools
sometimes require the use of JPMS modules, which can be problematic in
NetBeans (see above).  And in any case NetBeans does not yet seem to
expose any way to take advantage of these new tools.  So what IS the
most common way that people build a release version of a NetBeans
Platform application, anyway?
  
Ultimately, I just don't understand what the current "best practice" or
"golden path" is for using NetBeans Platform.  I'd like to know, though.
I am happy to help improve the tutorials, but the problem is that even
after reading various tutorials and documentation, and even after
experimenting quite a bit on my own, I don't even understand what the
path of least resistance is supposed to be.

Footnotes:
[1] 
http://mail-archives.apache.org/mod_mbox/netbeans-users/202010.mbox/%3c87sg9wgt19@gmail.com%3E

-- 
Chris
  

Re: HTML Disable Auto Completion 12.4

[Emilian Bold]

Back when I was working on this each such settings had a property that
was being saved by NetBeans. So, just because there's no UI for it it
doesn't mean you can't make a simple module that tweaks that property
or just hand-edit an XML in your userdir.

So now, the questions just is how was that property called?

You can probably learn it by just tweaking the property in an older
NetBeand then diff-ing the files. I'd guess just copying the XML to
the 12.4 user dir would do the trick.

--emi

On Thu, Jul 8, 2021 at 10:24 AM John Lavelle  wrote:
>
> BUMP! BUMP!
>
> I assume that no one uses HTML in NetBeans so has no experience of this?
>
> Any answers or suggestions?
>
> Regards
> John
>
> BUMP!
>
> Can anyone shed any light on this?
>
> Thanks
> John
>
> Hi,
>
> You used to be able to disable the Auto Completion pop-up for HTML by 
> deleting (must be deleted not just disabled) the items in "Tools>Palette>Code 
> Clips" (why?) then in "Tools>Options>Editor>Code Completion>HTML" deselecting 
> "Auto Popup Completion Window".
>
> In 12.4 it seems the only way to disable Code Completion for HTML is to 
> disable it for every language in the "All languages" Code Completion section.
>
> Is there a way to disable Code Completion just for one language as the "old" 
> system no longer seems to work correctly?
>
> Best regards,
> John
> j...@jql.co.uk
> Bike Farkles: https://www.youtube.com/channel/UCPRV92Cf_R1ihviRtVU2teQ
> JLavelle.uk https://www.youtube.com/jlavelleuk

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

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

Fwd: HTML Disable Auto Completion 12.4

[John Lavelle]

BUMP! BUMP!

I assume that no one uses HTML in NetBeans so has no experience of this?

Any answers or suggestions?

Regards
John

BUMP!

Can anyone shed any light on this?

Thanks
John

Hi,

You used to be able to disable the Auto Completion pop-up for HTML by
deleting (must be deleted not just disabled) the items in
"Tools>Palette>Code Clips" (why?) then in "Tools>Options>Editor>Code
Completion>HTML" deselecting "Auto Popup Completion Window".

In 12.4 it seems the only way to disable Code Completion for HTML is to
disable it for every language in the "All languages" Code Completion
section.

Is there a way to disable Code Completion just for one language as the
"old" system no longer seems to work correctly?

Best regards,
John
j...@jql.co.uk
Bike Farkles: https://www.youtube.com/channel/UCPRV92Cf_R1ihviRtVU2teQ
JLavelle.uk https://www.youtube.com/jlavelleuk

Re: users Digest 7 Jul 2021 19:24:25 -0000 Issue 1288

[Bradley Willcott]

Hi Chris.
Firstly, I have no experience in developing Netbeans Platform projects.  
However, I have developed many others, all Open Source 
https://github.com/bewillcott .
As a suggestion to help with the deployment side, I wish to offer the 
following ideas for the Maven POM:




   ...

    
com.yourproject.Main
...




release-profile



org.codehaus.mojo
exec-maven-plugin


Zip Binary Jar and libs
verify

exec


zip

${project.build.directory}

false

true

-r

${project.build.finalName}.zip

${project.build.finalName}.jar
libs






   ...





...







src/main/resources



**/*




...





org.apache.maven.plugins
maven-dependency-plugin


copy-dependencies
prepare-package

copy-dependencies


runtime
test

${project.build.directory}/libs






org.apache.maven.plugins
maven-jar-plugin



true
libs/
${jar.manifest.mainClass}

true

true





...






org.codehaus.mojo
exec-maven-plugin
3.0.0


maven-dependency-plugin
3.1.2


maven-jar-plugin
3.2.0


...




...
 
    



What you will end-up with, amongst other files, is a Zip file with the 
program jar and a 'libs' directory containing all of the project's 
dependencies.  To install, just unpack the zip file into an application 
directory, and run the application from this directory ("java -jar 
.jar").  It will automatically find all of its dependencies 
in the 'lib' directory.


Separately, I don't see any issue with an end-user having to install a 
version of the JRE to run Java applications.  In Windows, it is quite 
easy, isn't it?


I know that this does not properly answer your questions, but I hope it 
helps.


Regards,
Brad.

On 8/7/21 3:24 am, Chris Marusich  wrote:

Subject:
NetBeans Platform "Golden Path"
From:
Chris Marusich 
Date:
8/7/21, 3:24 am

To:
users@netbeans.apache.org


Hi,

What's the current "best practice" or "golden path" for building and
distributing a NetBeans Platform application and managing its
dependencies (e.g., from Maven central)?  That's a big general question,
so I'll ask some specifics:

- Should I ever try to use JPMS modules when building a NetBeans
Platform application?  I've found that in my projects (which are
NetBeans Maven-based projects, not NetBeans Platform projects), when I
use JPMS modules, it can cause problems for NetBeans [1], so I wonder if
it's really wise to even try mixing JPMS modules with NetBeans projects
at this time, let alone NetBeans Platform projects.

- Should I ever try to make a Maven-based NetBeans Platform application?
I see there are Maven templates in NetBeans that offer to create a
Maven-based NetBeans Platform project.  However, all the examples online
and in books that I've seen so far do NOT use Maven.  In spite of this,
recent emails on this list have