So, what I've done for this?
I do the tecreations SystemCompiler. That depends on the javac, for the
version you're running. You can set release version, mine is currently at 8.
If the classes are current when you do a ca.tecreations.apps.Deploy,
'like' thing, that might work. You'd have to test.
If it signs, if desired (only using jarsigner, ... , or their current
software..., latest is best, but I'll use your worst. ).
If it passes, deploy to remote.
I know. Tim does PKI.
Build.
Tim
On 29/03/2023 5:44 p.m., Sean Carrick wrote:
From what I've seen, it's been an issue since JDK 9. After the JDK was
modularized, it seems that this has been the way it is. The last
version of NetBeans that imports SQL package is NetBeans 8.2 when
using Ctrl+Shift+I.
If you use a newer version of NetBeans and have your default JDK as 8,
the automatic imports for the SQL package works. It's only an issue
with JDK 9+…
All I know is that this is not a NetBeans issue. Rather, it seems to
be an issue with the JDK…
On Sun, Mar 26, 2023, 09:56 Petri Koskelainen
<petri.koskelai...@gmail.com> wrote:
Hi!
NetBeans won´t suggest import any java.sql package class (that light
bulb on the leftside).
It does find java.sql package and classes if i manually write
import to
the code.
I have tried make new project, all new netbeans settings files,
diffent
jdk.
nothing works to fix it.
What to do?
- Pete
---------------------------------------------------------------------
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