Every once in a while verification starts slipping, suggestions for
automatic verification renewal gain traction, then verification starts
up again.
Wondering if there's a causal relationship.
-
To unsubscribe, e-mail: dev-uns
Hi all,
4 years ago I created the jfx archetyes repository,
https://github.com/errael/javafx-maven-archetypes-netbeans, so that jfx
projects would work "out of the box" with debugging, profiling, jlink...
on NetBeans. It's artifact is on maven and used from
javafx/javafx2.kit/src/org/netbeans
nts file is for the hints file
itself. It is not added to the refactored sources or anything like that.
Imports are added automatically when the hint is applied if new
imports are needed, there is no way to control this mechanism.
-mbien
On 15.02.24 07:09, Ernie Rael wrote:
Using the f
Using the follow does most of the conversion work, requires some manual
fixup for certain log4j arguments. But *import static
java.lang.System.Logger.Level.*;* doesn't get added. Any suggestions for
a way to add that as part of the refactoring?
-ernie
org.apache.logging.log4j.Log
On 24/02/05 9:03 AM, Ernie Rael wrote:
On 24/02/05 7:02 AM, Neil C Smith wrote:
Hi,
On Sun, 4 Feb 2024 at 23:33, Ernie Rael wrote:
If there's going to be an RC-3, I'll wait for that. (was it skipped last
week?)
If possible could you test the dev build at
DONE
This PR build
i
On 24/02/05 7:02 AM, Neil C Smith wrote:
Hi,
On Sun, 4 Feb 2024 at 23:33, Ernie Rael wrote:
If there's going to be an RC-3, I'll wait for that. (was it skipped last
week?)
If possible could you test the dev build at
DONE
This PR build
is prior to merging that to see if the fal
On 24/02/04 3:20 PM, Neil C Smith wrote:
On Sun, 4 Feb 2024, 22:12 Ernie Rael, wrote:
On 24/02/04 7:11 AM, Neil C Smith wrote:
On Thu, 25 Jan 2024 at 20:21, Ernie Rael wrote:
With NB-21-RC2, running on JDK-21,
doing: NewProject > JavaWithGradle > JavaClassLibrary
And there is the &q
On 24/02/04 7:11 AM, Neil C Smith wrote:
On Thu, 25 Jan 2024 at 20:21, Ernie Rael wrote:
With NB-21-RC2, running on JDK-21,
doing: NewProject > JavaWithGradle > JavaClassLibrary
And there is the "resolve problems" icon.
$ ./gradlew --version
Gradle 8.4
I presume you're
With NB-21-RC2, running on JDK-21,
doing: NewProject > JavaWithGradle > JavaClassLibrary
And there is the "resolve problems" icon.
$ ./gradlew --version
Gradle 8.4
I thought this would be Gradle-8.5, especially since there was talk with
NB-20
of waiting for Gradle-8.5.
Unlike with NB-20, with
I too used windows for several years (linux now, it's wonderful and no
more cygwin), I don't recall having seen this issue. But I use jVi which
has it's own cut/paste handling that behaves like vim's (there's even a
flavor so blockmode copy/paste works between vim/jVi). Otherwise
clipboard inte
> The requirement to sign the plugins is questionable in itself
Especially considering that it's in maven central.
-ernie
On 23/08/13 1:10 PM, Matthias Bläsing wrote:
Hi again,
I just noticed, that the LDIF Editor and LDAP Explorer plugins were
rejected for the plugin portal for 19.
Reasonin
Using a newish large memory, multi-core laptop. The fan made itself known.
Indexing took ~15 minutes.
Over a weeks worth of logs, only one indexing of central. There's a little
"2nd thought" bouncing that seems to go on immediately after the indexing.
An aside
While taking a look at this I ra
On 23/05/22 2:29 AM, Eric Barboni wrote:
This is to propose the creation of new repository to manage javaEE archetype
that we use in Apache NetBeans on Apache NetBeans infrastructure.
We already have some archetype for platform and app creation
https://github.com/apache/netbeans-mavenutils-arche
Hi Eric and all,
In
javafx/javafx2.kit/src/org/netbeans/modules/javafx2/kit/JavaFXWizardIterator.java
there's references like
return definedFXArchetype("com.raelity.jfx",
"javafx-archetype-fxml-netbeans",
"0.0.4", Bundle.LBL_Maven_FXML_Archetype());
The m
Just got this, good to be reminded. (and it's not even for an RC)
Couple problems
The link has a double '//' which breaks it with firefox.
On the plugin "version management" page "NB 18" is listed,
but there is no "Request verification" button for that release.
-ernie
On 23/04/21 1:41 PM, Ne
On 23/02/05 11:31 AM, Michael Bien wrote:
NB 16/17 ships nb-javac which is based on JDK 19. Which means the
minimum bytecode level is 7 already. Once nb-javac updates to 20 that
number would be 8. (JDK 14 dropped support for 6, 20 dropped support
for 7,
The link Neil gave
https://www.orac
(Apologies if you see this twice. First sent this 3 hours ago. It was
not delivered to me; anyone?)
As Neil says
The question is whether it is worth it?
And Scott
An informed decision needs to be based on these details. Holding back
for
JDK 8 compatibility helps no one if there isn't actuall
As Neil says
The question is whether it is worth it?
And Scott
An informed decision needs to be based on these details. Holding back for
JDK 8 compatibility helps no one if there isn't actually any real demand to
do so.
AFAICT, there's no stats on JDK version and NBP projects. Maybe the
close
I'm starting to work with some unfamiliar code. For example I've got
class DerivedTableModel extends AbstractTableModel
class DerivedJTable extends JTable
I want a list of all methods in DerivedTableModel that are not in
AbstractTableModel. I tried "Refactor > ExtractInterface" but the li
On 23/02/11 5:26 PM, Arafat BOUCHAFRA wrote:
Hi,
I'm here to help, just create a GitHub repository, and a discord server
channel, and share them with me
In a later message:
https://github.com/vieiro/netbeans-cnd/tree/rust
Regards
Le sam. 11 févr. 2023 à 15:54, Antonio a
écrit :
Hi all
It's too bad there are no NetBeans specific statistics, both IDE and
platform.
It sure would be nice if there were some reference to stats on jdk
version usage
in these deliberations.
What I've seen in reports, the most recent I've found from mid 2022,
even though Java 11 had been available
On 23/02/07 3:29 AM, Neil C Smith wrote:
On Mon, 6 Feb 2023 at 17:28, Ernie Rael wrote:
Here's my understanding: squashing and force pushing to a PR branch, in
particular one that I opened, does not run into issues.
Yes, you're all good.
Note that by default, every committer
On 23/02/05 7:52 AM, Neil C Smith wrote:
On Wed, 11 Jan 2023 at 11:03, Neil C Smith wrote:
Yes, the sooner we can update what was agreed for NB13, the better.
But that requires notice (so not NB17, and possibly not NB18), a new
lazy consensus proposal, and no vetoes!
Let's talk some more about
On 23/02/06 12:34 PM, Neil C Smith wrote:
On Sat, 4 Feb 2023 at 00:51, Michael Bien wrote:
yeah it seems like nobody is using the triage label the way it was
originally intended.
We could probably just remove that label (or don't let gh set it by
default at the very least). If something is mis
Looking for clarification on some issues that arose in a side discussion
in a PR.It comes down to this statement:
So if I get this right, a pattern is to push several commits to a
PR, then after approval, can squash locally (using mercurial in my
case) and force push to the PR.
There w
About using build.properties and nbjdk.home
There's a thread from last year,
https://lists.apache.org/thread/4qvk880rkn4norzk7t9tt92ppmnf48kp, where
it was not sufficient to set nbjdk.home, JAVA_HOME also had to be set.
I was using nbbuild/user.build.properties, not ~/.nbbuild.properties;
do
On 23/01/26 10:25 AM, Scott Palmer wrote:
Well, yeah of course.. but is there a documented public API?
The maven plugin doesn't actually do refactoring, right? It just
identifies hints?
At: https://netbeans.apache.org/jackpot/
To apply the changes produced by the declarative hints, run
jackp
On 23/01/26 7:01 AM, Scott Palmer wrote:
I wanted to experiment with Jackpot for a project I'm working on. How
dependent on the NetBeans Platform is the Jackpot code at
https://github.com/apache/netbeans-jackpot30 ?
Is there such a thing as a jackpot library jar that does not depend on
NetBeans
ll handle/respond.
-ernie
On 23/01/20 9:28 AM, Ernie Rael wrote:
Just received:
Plugin: jVi Update Center JDK-11
NetBeans version: 17
Verification status: NOGO
Comments: On uninstall of the downloaded plugin
(nbupdatecenter-jdk11-1.0.nbm), update center is not removed.
"update cente
Just received:
Plugin: jVi Update Center JDK-11
NetBeans version: 17
Verification status: NOGO
Comments: On uninstall of the downloaded plugin (nbupdatecenter-jdk11-1.0.nbm),
update center is not removed.
"update center not removed" has been a problem for over 10 years. My
understanding has be
On 23/01/18 11:18 AM, Neil C Smith wrote:
On Wed, 18 Jan 2023, 18:42 Ernie Rael, wrote:
Changed it to just a comment. I'm not sure how many people really use the
affected code without the window system.
And I commented, quoted warning from Frame.getFrames() javadoc.
If rebased on del
On 23/01/18 9:59 AM, Neil C Smith wrote:
Looking at https://github.com/apache/netbeans/pull/5280 it had
approval from one of the four people requested to review.
This is somewhat of a grey area to me. I often see PRs merged where
some reviewers don't weigh in. In any event, the PR should have b
On 23/01/18 8:40 AM, Neil C Smith wrote:
Any particular PR in mind? Is it a candidate for RC2?
https://github.com/apache/netbeans/pull/5280
It hardly seems a candidate. Been around, easy workaround...
-ernie
-
To unsubscri
you need
to bug people.
That's what I meant by politics
the activities associated with the governance of a country or other
area, especially the debate or conflict among individuals or parties
having or hoping to achieve [merge]
-ernie
On 23/01/18 8:40 AM, Neil C Smith wrote:
On Wed, 18 Ja
napproved pull requests..."
And I'm usually so literal...
The universe conspires so I'll run a custom version of NB.
-ernie
milestones are just a way to roughly organize PRs around deadlines.
-mbien
On 18.01.23 16:47, Ernie Rael wrote:
I would have thought that any approved PR wi
I would have thought that any approved PR with NB-17 milestone gets
merged. Guess not.
I didn't realize there was more politics after that.
-ernie
-
To unsubscribe, e-mail: dev-unsubscr...@netbeans.apache.org
For additional c
On 23/01/11 2:05 AM, Neil C Smith wrote:
Unless we've ended up in mid-2025 without me noticing, could you try
importing a recent KEYS file and check again?
Was getting expired, imported KEYS, got rid of expired.
-ernie
-
To
just today (signed on 21. Nov 2022)
Maybe the release should be signed next time by a key which is at
least 6 months before expiration or something like that, so it
survives to the next release.
-S.
On 11. 01. 23 3:37, Ernie Rael wrote:
Just downloaded source from https://netbeans.apa
Just downloaded source from https://netbeans.apache.org/download/nb16/
I'm getting verification failures with both sha and gpg.
I have to figure it out every time, could be cockpit error; but this
seems like a real failure.
-ernie
On 23/01/10 6:16 AM, Michael Bien wrote:
Given that NB doesn't really support running on JDK 11 since a while I
would simply opt for 2) and merge.
Typo? JDK-11 --> JDK-8
-ernie
-
To unsubscribe, e-mail: dev-unsubscr...
Just updated to the final bits; and wondering about a /backwards seeming
dependency/. I started with the first check release of 16-u1, so this
normally wouldn't be seen.
Using plugin manager, uninstall everything with "gradle". Still had
org.netbeans.modules.gradle/2 [2.29.1
Netbeans/ne
Under javadoc for ActionRegistration annotation, in the verbose doc for
lazy, the Presenter.* links work.
-ernie
On 23/01/05 2:29 PM, Ernie Rael wrote:
Came across another unexpected "Oracle Transition".
1. Goto PopupAction
2. Click on something under "Nested Class Summar
Came across another unexpected "Oracle Transition".
1. Goto PopupAction
2. Click on something under "Nested Class Summary".
Can't find Presenter either. Not sure how widespread this nested class
issue is.
-ernie
On 23/01/04 5:25 PM, Ernie Rael wrote:
Clicki
etbeans/nbbuild/JavadocIndex.java#L115
A typical interface line looks like:
ErrorManager.Annotation
I try to edit the regexp but I did not succed to swallow the span element.
Start thinking using jsoup to do the job 😝 (but that's because I'm not goot at
regexp)
Regards
Eric
-Mes
I ran into this, and didn't find a simple solution.
https://lists.apache.org/thread/lto47nxlhj2r6fbk16l93qs3vy9g2rtg
https://lists.apache.org/thread/tk263h5xco04kwpcfrt55p0lnlmokb0m
I think you need to hookup a new test runner. I didn't pursue it because
ant is a dead end.
My solution,
I've just opened this issue
https://github.com/apache/netbeans/issues/5120
It has lots of info gathered at the point of failure. But I suspect the
problem comes from things done at project open.
I could compare some things between maven project open and gradle
project open if that makes s
On 22/12/15 9:34 AM, László Kishalmi wrote:
Thanks for your understanding!
Went ahead and merged the delivery to the release160 branch. The update can
be tested by adding the following update center URL:
https://ci-builds.apache.org/job/Netbeans/job/netbeans-TLP/job/netbeans/job/release160/14/a
I'm salivating at the thought of running NetBeans on a recent jdk and
work on old gradle version projects.
For testing, is it possible and simple to have a nb16u1 update center,
which I can manually add locally?
-ernie
On 22/11/27 3:25 PM, Laszlo Kishalmi wrote:
Dear all,
This is a kind of
On 22/11/20 2:30 AM, Neil C Smith wrote:
On Fri, 28 Oct 2022 at 10:04, Neil C Smith wrote:
I totally agree with the points raised there. We haven't had a
vaguely useful plugin catalog since NetBeans 13. The plugin catalog
for 16 is currently empty, so we're missing possibilities for testing.
especially if it was long ago). Of
course there has to be something to vote on, not to mention the manpower
that puts the voting candidate together.
-ernie
On 22/11/16 9:26 AM, Neil C Smith wrote:
On Wed, 16 Nov 2022 at 16:35, Ernie Rael wrote:
Is there an obstacle/problem preventing NB13'
On 22/11/16 2:48 AM, Neil C Smith wrote:
On Wed, 16 Nov 2022 at 01:25, Ernie Rael wrote:
Guess automatic re-verification for existing plugins didn't make it for
NB-16.
Guess not! :-\ Although as there's only 3 plugins verified in NB15
still, that might not have led to m
On 22/11/15 4:56 PM, Junichi Yamamoto wrote:
Hi,
I haven't received it yet...
I haven't seen it either.
Did go to the portal and saw NB-16, so I requested verification.
Guess automatic re-verification for existing plugins didn't make it for
NB-16.
-ernie
PS. apologies if anyone sees this
On 22/11/15 4:56 PM, Junichi Yamamoto wrote:
Hi,
I haven't received it yet...
I haven't seen it either.
Did go to the portal and saw NB-16, so I requested verification.
Guess automatic re-verification for existing plugins didn't make it for
NB-16.
-ernie
I've also checked a spam folder
On 22/11/05 9:09 PM, Scott Palmer wrote:
Somewhat related to the issue described already…
My project wants to use JDK 19 features.
Gradle 7.5.1 wants to run on something older, e.g. JDK 17.
I had a similar issue, the IDE used the wrong source version. The
problem was fixed, in my case, by exp
On 22/10/29 1:48 AM, Neil C Smith wrote:
On Sat, 29 Oct 2022 at 00:28, Ernie Rael wrote:
I left a comment in the code where I ran into the problem; it references
https://github.com/apache/felix/pull/114
which led me to believe it was a JDK incompatibility; could just be that
issue&#
In NB-16-rc, there's a PR: "Dialog parent should not be null"
https://github.com/apache/netbeans/pull/4739
Any test/feedback of changed dialogs' behavior, and observations for
dialogs that are misplaced, appreciated.
Before this change, these dialogs would show up in the center of Java's
def
On 22/10/28 3:52 PM, Michael Bien wrote:
On 29.10.22 00:27, Ernie Rael wrote:
On 22/10/28 3:08 PM, Michael Bien wrote:
Search for "ByteBuffer NoSuchMethodError" for a taste.
Looks familiar, think I ran into that. Wasn't that considered a bug
in the JDK release?
no,
On 22/10/28 3:08 PM, Michael Bien wrote:
and I wish I could count on the fact that there's been no bug report;
but that's another story.
Given that sigtest failed, I'm surprised that there's so much
surprise that there's an issue.
nobody is surprised. If you would have read the PR you w
On 22/10/28 3:08 PM, Michael Bien wrote:
Search for "ByteBuffer NoSuchMethodError" for a taste.
Looks familiar, think I ran into that. Wasn't that considered a bug in
the JDK release?
-ernie
-
To unsubscribe, e-mail: dev-
On 22/10/28 9:47 AM, Neil C Smith wrote:
On Fri, 28 Oct 2022 at 17:14, Ernie Rael wrote:
So does the workaround I suggested work for you?
Seems to.
I'm checking out the 16 build on 15 now that I can run it.
-ernie
Best wishes,
On 22/10/28 2:27 AM, Neil C Smith wrote:
On Thu, 27 Oct 2022 at 21:35, Matthias Bläsing
wrote:
Am Donnerstag, dem 27.10.2022 um 20:51 +0100 schrieb Neil C Smith:
I'm not sure that's correct from the JVM perspective. The Object
method should still be generated as a bridge?
It should be backw
On 22/10/27 4:26 PM, Michael Bien wrote:
On 27.10.22 22:51, Ernie Rael wrote:
I'm still confused. I always thought generics were syntactic sugar,
nah they do influence method signatures, add bridge methods you never
wrote etc. Its more than just compile time checks.
Matthias showe
On 22/10/27 12:52 PM, Michael Bien wrote:
On 27.10.22 21:46, Ernie Rael wrote:
On 22/10/27 12:33 PM, Michael Bien wrote:
On 27.10.22 21:14, Matthias Bläsing wrote:
Hi,
Am Donnerstag, dem 27.10.2022 um 20:32 +0200 schrieb Michael Bien:
On 27.10.22 20:17, Neil C Smith wrote:
On Thu, 27 Oct
On 22/10/27 12:51 PM, Neil C Smith wrote:
On Thu, 27 Oct 2022 at 20:14, Matthias Bläsing
wrote:
Am Donnerstag, dem 27.10.2022 um 20:32 +0200 schrieb Michael Bien:
I am still a bit surprised that this causes issues. Since the class is
final which removes an entire can of worms of potential over
On 22/10/27 12:33 PM, Michael Bien wrote:
On 27.10.22 21:14, Matthias Bläsing wrote:
Hi,
Am Donnerstag, dem 27.10.2022 um 20:32 +0200 schrieb Michael Bien:
On 27.10.22 20:17, Neil C Smith wrote:
On Thu, 27 Oct 2022, 19:03 Ernie Rael, wrote:
This is very strange. If I build the plugin on
On 22/10/27 11:17 AM, Neil C Smith wrote:
On Thu, 27 Oct 2022, 19:03 Ernie Rael, wrote:
This is very strange. If I build the plugin on 15 it runs on 15. If I
build it with 16-RC2 it will not install on 15. I noticed this a few
days ago, but wanted to wait for RC2 before mentioning it.
I&#x
This is very strange. If I build the plugin on 15 it runs on 15. If I
build it with 16-RC2 it will not install on 15. I noticed this a few
days ago, but wanted to wait for RC2 before mentioning it.
I'll try to narrow it down, wondering if anyone has some ideas about this.
-ernie
SEVERE [org.n
thing to pursue.
The situation arises when using an old userdir (which has a variety of
update centers). In this case, if I disable the NB8 update center, I
still see an "update available", but the 8.2... is gone.
-ernie
-mbien
On 27.10.22 18:42, Ernie Rael wrote:
In help
In help > about, I see
Product Version: Apache NetBeans IDE 16-rc2
Updates: Updates available to version NetBeans 8.2 Patch 2
Java: 11.0.2; OpenJDK 64-Bit Server VM 11.0.2+9
Is the reference to NB-8.2 something weird about my userdir? Or ...?
-ernie
On 22/10/27 2:59 AM, Neil C Smith wrote:
On Wed, 26 Oct 2022 at 21:12, Ernie Rael wrote:
NetBeans found
refuge in the powerful walled city state of Apache; where residents are
only allowed commerce with those within its walls or with some who it
explicitly approves.
Your text amused me,
At
On 22/10/17 12:54 AM, Oliver Rettig wrote:
Hi all,
since years we miss a modern (on- and offline) help-viewer for your netbeans
platform applications. Now, we have just started a student project at the
Cooperative State University Karlsruhe (Germany) to fill this gap. It will run
the next six mo
On 22/10/24 9:42 AM, Neil C Smith wrote:
OTOH, I don't think this is all suited to technical discussion on
individual code changes either, as there are also questions of broad
direction of travel raised here that need to be reconciled.
In the before time, in the Kingdom of Java, NetBeans was in
On 22/10/24 9:42 AM, Neil C Smith wrote:
On Mon, 24 Oct 2022 at 17:02, Michael Bien wrote:
On 24.10.22 17:27, Ernie Rael wrote:
The link to apache's guidelines for voting was clarifying for me. I'd
like to see a more technical discussion.
for me too, I withdrew the -1 vote th
On 22/10/24 8:58 AM, Michael Bien wrote:
On 24.10.22 17:27, Ernie Rael wrote:
The link to apache's guidelines for voting was clarifying for me. I'd
like to see a more technical discussion.
for me too, I withdrew the -1 vote the moment I realized that this
could qualify as veto
On 22/10/24 4:50 AM, Neil C Smith wrote:
On Mon, 24 Oct 2022 at 12:31, Geertjan Wielenga
wrote:
On Mon, Oct 24, 2022 at 1:25 PM Neil C Smith wrote:
Multiple people have expressed massive reservations on this already.
Michael expressed a -0.99 already. Given code changes are really +1
or -1 a
On 22/10/22 5:09 AM, Michael Bien wrote:
On 21.10.22 14:24, Neil C Smith wrote:
On Fri, 21 Oct 2022 at 12:43, Michael Bien wrote:
well, this was my first suggestion but it met resistance :)
I know. I agree with you. My issue with the resistance, and some
points are definitely valid, is that
There are two PRs that have been approved. I'd like to use them from a
plugin if/when they are merged.
Keyboard focus can activate top component
https://github.com/apache/netbeans/pull/4603
and
After file external change fire reloaded event
https://github.com/apache/netbeans/pull/4
Let me confess that I'm not sure what is proposed, in my simplistic view
it's letting NB users have target less than source. I don't entirely
understand all the stuff this msg is addressing.
But considering these points
- How useful is frgaal for NB/java user community? Makes NB more
attracti
For the following (important in a multi screen setup, should read "don't
use null")
Dialog parent main window instead of null
https://github.com/apache/netbeans/pull/4739
I want to move a method, private FileChooserBuilder.findDialogParent(),
to a public spot. My first thought was Dialog
On 10/7/22 3:41 PM, Ernie Rael wrote:
BTW, for command line use, I have an alias, use it like javac
frgaal is aliased to
`mvn-repo/org/frgaal/compiler/19.0.0/compiler-19.0.0.jar'
Uhh, that would be
aliased to `java -jar
mvn-repo/org/frgaal/compiler/19.0.0/compiler-19.0.
This is about "target < source"; talk about changing the JDK version
obfuscates the point. Changing JDK version is not available to many
(most?) (just guessing).
The only technical points against (that have registered with me, and not
saying that I fully agree with them, and there may be more)
For the following (important in a multi screen setup, should read "don't
use null")
Dialog parent main window instead of null
https://github.com/apache/netbeans/pull/4739
I want to move a method, private FileChooserBuilder.findDialogParent(),
to a public spot. My first thought was DialogDis
On 10/6/22 8:16 PM, Michael Bien wrote:
On 06.10.22 19:55, Ernie Rael wrote:
On 10/6/22 10:41 AM, Neil C Smith wrote:
On Thu, 6 Oct 2022 at 18:02, Ernie Rael wrote:
Is the claim that using older JDK for runtime rarely happens? I don't
have any data, but...; NetBeans is a case in point
Thought I'd mention...
I was just testing some stuff in a standalone/plugin project (so has to
be binary 11) for an in progress NB PR. Made a change in a file I
haven't been in for a while, saw several hint flags, in this case for
both instanceof and switch pattern matching, made the changes;
On 10/6/22 10:41 AM, Neil C Smith wrote:
On Thu, 6 Oct 2022 at 18:02, Ernie Rael wrote:
Is the claim that using older JDK for runtime rarely happens? I don't
have any data, but...; NetBeans is a case in point, and I know of
others; it can be a corporate (ie irrational:-) ) decision.
-1 to DISCUSSION? Wow. That's pretty draconian.
Could we agree on "what are the issues?" It feels like FUD right now.
> if you are sure you never want to leave the hole you dug
What does that mean? If the java "promise" is true. Then at any time you
can use a released JDK >= SourceLevel.
>
group which means it wasn't too much out of date yet :)
-mbien
On 05.10.22 04:41, Ernie Rael wrote:
Inspired by @mbien to setup for doing some jackpot (declarative
refactoring) across all of NetBeans, I used two scripts to set up a
project group with all the projects. Here they are in
Inspired by @mbien to setup for doing some jackpot (declarative
refactoring) across all of NetBeans, I used two scripts to set up a
project group with all the projects. Here they are in case someone might
find them useful. They don't find gradle or maven projects (AFAIK). Run
them like the foll
On 10/1/22 2:12 PM, Michael Bien wrote:
Hi Ernie,
On 01.10.22 21:07, Ernie Rael wrote:
As a an experiment, there's the hint seen below. Is there a way to
run it on all projects, not just the open projects?
I don't think there is. When I ran repo wide refactorings (e.g #3844)
I
There are dialogs scattered around NetBeans that do not specify a
parent. So when they come up they are on the "default screen", which for
me is typically not the screen with the NetBeans main window. More that
once I've wondered why NB is hung (maybe I'm a little too focused).
There's PR "Chec
> automatically backported nb-javac
I wouldn't say automatically makes it "technically the same"; I don't
know much about the mechanisms that do javac --> nbjavac, maybe it's not
that bad. If frgaal was automatically generated from javac, would that
make them the same and alleviate concerns ab
I wanted to take a look at ContextAwareAction. But entering this in the
search box has no results. Found it in the source, searched for
imageutil from the same package, clicked AllClasses, found it there.
I think this has been an issue for a long time. Might have to do with
"Interface".
erni
There are some excellent answers, perhaps you are blocked on your side.
You can view the thread at:
https://lists.apache.org/list?dev@netbeans.apache.org:2022-9
-ernie
On 9/24/22 8:11 AM, Peter Cheung wrote:
am i being blocked? whatever i ask, no one willing to answer 🙁
Thanks
From Peter
deps(task, 'jvi', jvi_proj, ':clean')
}
tasks.register('build') { task ->
deps(task, 'jvi', jvi_proj, ':build')
}
tasks.register('run') {
dependsOn gradle.includedBuild('jvi').task(':jvi-cmd:run')
}
On Fri, S
--debug-jvm
The first doesn't get an error, but hangs just the same. The second
doesn't find check in jvi.
I thought about running the debugger from the 'buildInclude' project
directly, but I suspect in a more general case the dependencies would be
wrong.
-ernie
On 9/22/
On 9/22/22 9:15 AM, László Kishalmi wrote:
You may find reading this one useful:
https://docs.gradle.org/current/userguide/composite_builds.html
Thanks, this looks promising. I started, only for one project, with
settings.gradle
rootProject.name = 'jvi-ide'
includeBuild '/src/jvi-dev/j
On 9/16/22 9:09 AM, Michael Bien wrote:
On 16.09.22 17:19, Ernie Rael wrote:
On 9/15/22 10:44 PM, Michael Bien wrote:
On 16.09.22 07:31, Laszlo Kishalmi wrote:
I started to reply on this, but not sure if I really pressed the
send button, and I do not see my reply. So I'm sorry i
dn't have to copy them
manually.
So you can influence what is migrated simply by editing this file
before first launch :)
-mbien
On 9/15/22 10:34, Ernie Rael wrote:
On 9/14/22 5:55 PM, Michael Bien wrote:
On 10.09.22 01:53, Ernie Rael wrote:
With release 15 I did something like
On 9/14/22 5:55 PM, Michael Bien wrote:
On 10.09.22 01:53, Ernie Rael wrote:
With release 15 I did something like
mkdir 15
cp -a 14/userdir 15/userdir
Then start NetBeans-15 using 15/userdir and a fresh cachedir.
Simpler than import settings. Is there any problem/downside doing this
The bug
Editor with Keyboard focus is not active TopComponent (undo/redo
don't work while editing)#4437
https://github.com/apache/netbeans/issues/4437
Has a fix
Keyboard focus can activate top component #4603
https://github.com/apache/netbeans/pull/4603
which needs review. It's
1 - 100 of 394 matches
Mail list logo
