Probably good advice but I was trying to follow the direction of NetBeans
to use Maven as the preferred build tool.
At this point, for this semester, I am way too committed to Maven (it is an
online course with all the course content is done). This was a simple type
it in like the textbook
For those kind of projects use Ant or Gradle. They do not suffer from this
issue, and probably better suited for small student projects.
On Sat, Aug 28, 2021, 13:16 David Green wrote:
> Thanks for the reply and insight.
>
> That does work at the command line (as did running it from a jar file).
Thanks for the reply and insight.
That does work at the command line (as did running it from a jar file). I
am seeking to have it work in the NetBeans Output window and I found that
if I edited the Run (and Run File) Actions in the project properties to use
"java" instead of "exec", it does
In NetBeans 12.4 and verified to also behave this way on NetBeans
12.5-beta2, System.out.print is buffered such that it does not show up in
the NetBeans Output window until a System.out.println (or probably things
like program end, and some buffer full scenario).
Using JDK 15 and a Maven Project.
It’s the last piece of the donation process and is pretty much stuck. You
can ask and keep asking about this, the answer will be the same. I propse
that we should simply be happy with what we have and move on. Python
support, I suggest, should be lightweight and done via LSP rather than the
old
I know this has been asked many times before but what is the current status
of the Python Donation?
Some work based on previous releases have been worked, and it's working
locally, (although the build fails due to some out of date API needing
updates) but in the end the work is waiting on the
What is configuration is in use for this (i.e. Netbeans version, Java
version, Netbean...About) ?
What project are you using (i.e. how big is it)? Not sure if maybe this
requires a larger project to trigger more indexing behavior but...
1. Running with 12.5 Beta2...
2. Created a very
After manually setting my default netbeans jdk_home to successfully install
java 11 azul JDK, the plugins and activation and the download new open jdks
seems to work okay.
So maybe all of this was a side effect of running a newer (as default
JDK). Not sure if there is something needed going
With beta 2 it behaves a little better but I think there may still be some
quirkiness in the downloading and install logic (see my Beta 2 email for
more detail.
Eric Bresie
ebre...@gmail.com
On Thu, Aug 26, 2021 at 8:55 AM Neil C Smith wrote:
> On Mon, 23 Aug 2021 at 09:55, Neil C Smith
(1) Activate features
1. Tried activating HTML5, Java SE, Tools, JavaFX 2, Groovy, Java Web
and EE, Developing Netbeans, and Base IDE.
2. Hit "Activate" button which is followed by "Activation Failed: Cannot
enable* JavaFX2 Support" issue*
3. Not sure if this was due to nothing yet
10 matches
Mail list logo