Hi!
See https://github.com/apache/netbeans/issues/3725
Best regards, Pavel
On 4/2/24 6:42 PM, Tellis, Wyatt wrote:
Hi,
I'm trying to rename a method on a class and keep getting the following error:
Module Java Refactoring threw java.lang.IllegalStateException: java.lang.NullPointerExce
Hi,
I'm trying to rename a method on a class and keep getting the following error:
Module Java Refactoring threw java.lang.IllegalStateException:
java.lang.NullPointerException: Cannot invoke
"com.sun.tools.javac.code.Type.getThrownTypes()" because "tree.meth.type" is
Alonso and All --
What has helped me immensely to understand this subject is Fowler, M. (2019).
Refactoring: Improving the Design of Existing Code (2nd).
-- Chris
- Original Message -
From: "Alonso Del Arte"
To: "NetBeans Mailing List"
Sent: Monday, August
Refactoring usually involves making multiple changes in multiple files. For
example, in a Java project, say you decide to rename the MoneyAmount class
to just Money. If that class is referenced by a dozen other classes and
interfaces, then the change will impact at least a dozen lines in other
Hi Tom.
Refactoring is simply moving stuff around in your source code without
making any (major) change to the functionality of your program.
You may want to do this when for instance you are preparing to implement a
functional enhancement that makes use of a particular design pattern, and
your
Newbie question. I'm working on an HTML project. When I change a file
name, Netbeans wants to know if I want to "refactor" or not. What does
it mean to refactor?
-
To unsubscribe, e-mail: users-unsubscr...@netbeans.apache.or
Posting some follow up information for this problem.
I just discovered that refactoring issues I’ve been having with 12 for over a
year now seem to be related to the existence of nb-javac. For some reason I
thought nb-javac needed to be installed. I think I made this assumption
because I
fix.
>
>
>
> I’ve also noticed that the Find Usages function will work, but after the
> first several results produces the wrong line numbers where the usage
> actually occurs. It finds the correct file, but the lines displayed in the
> results window are off by several lines.
usage
actually occurs. It finds the correct file, but the lines displayed in the
results window are off by several lines. I suspect the refactoring issue
and this issue are somehow related as both problems seem to occur when there
are more than about a dozen dependents on the code being refactor
steps to reproduce so that this can be fixed?
Gj
On Fri, 2 Jul 2021 at 18:36, Ty Young <mailto:youngty1...@gmail.com>> wrote:
I reported refactoring issues here more than a year(2?) ago. While
someone did respond and provided a fix, it seems like the "fix"
was
What are some steps to reproduce so that this can be fixed?
Gj
On Fri, 2 Jul 2021 at 18:36, Ty Young wrote:
> I reported refactoring issues here more than a year(2?) ago. While someone
> did respond and provided a fix, it seems like the "fix" was just to
> suppress the is
I reported refactoring issues here more than a year(2?) ago. While
someone did respond and provided a fix, it seems like the "fix" was just
to suppress the issue(exceptions) and not fix the issue itself.
Refactoring on Netbeans is completely and utterly broken and has been
for a **V
Is refactoring affected by whether you use nb-javac or not?
On 02.07.21 16:56, Geertjan Wielenga wrote:
Just tried moving a Java class, no problems at all, using 12.4 on JDK
16.0.1 on Mac OSX.
GJ
On Fri, Jul 2, 2021 at 4:51 PM Marvin P. Warble Jr.
wrote:
In all versions of Netbeans
toring.spi.impl.ParametersPanel$Prepare.run(ParametersPanel.java:1063)
>
> at
> org.openide.util.RequestProcessor$Task.run(RequestProcessor.java:1418)
>
> at
> org.netbeans.modules.openide.util.GlobalLookup.execute(GlobalLookup.java:45)
>
> at org.openide.util.lookup.Lookups.executeWith(Lookups.java:278)
>
> at
> org.openide.util.RequestProcessor$Processor.run(RequestProcessor.java:2033)
>
>
>
>
>
> 3.When renaming a class, NB will sometimes rename the file, but fail
> to rename the actual class.
>
>
>
>
>
> The refactoring problems are making development quite difficult.
>
>
>
>
>
When renaming a class, NB will sometimes rename the file, but fail to
rename the actual class.
The refactoring problems are making development quite difficult.
No, it hasn’t been only right now for the current release.
Can you report your refactoring issues or point to the specific issues
you’re encountering?
Yes, there have been several performance enhancements, can you spend some
time on the 11.2 features page on netbeans.apache.org?
And, yes
installed, ever. No one is going to know that refactoring is borked
because nb-javac is bugged to high hell(and has been for 5 releases now!).
Maybe it's just my imagination(or some other system update) but Netbeans
11.2 runs faster in general anyway, even without nb-javac.
Also
On Sat, Nov 9, 2019 at 9:19 AM Ty Young wrote:
>
>
>
> Anyway, I can rename methods now but i'm a bit too scared to rename any
> packages or move classes around.
That implies you need to get your code into a versioning system, e.g., on
GitHub.
Gj
> Does that work for you after removing it?
We're working hard on implementing the special sauce that nb-javac adds
into NetBeans itself so that ultimately nb-javac won't be needed at all
anymore, e.g.:
https://github.com/apache/netbeans/pull/1319
In the meantime, if you can avoid using nb-javac, even though when it works
correctly (someth
On 11/9/19 2:09 AM, Thomas Kellerer wrote:
Ty Young schrieb am 09.11.2019 um 08:58:
On 11/9/19 1:53 AM, Geertjan Wielenga wrote:
What happens when you uninstall nb-javac?
Gj
I deactivated it and still have the same issue.
Disabling is not enough as I found out, you need to completely re
Ty Young schrieb am 09.11.2019 um 08:58:
On 11/9/19 1:53 AM, Geertjan Wielenga wrote:
What happens when you uninstall nb-javac?
Gj
I deactivated it and still have the same issue.
Disabling is not enough as I found out, you need to completely remove it.
--
ten worse. Now attempting to
rename any
method results in a "Java Refactoring threw java.lang.AssertionError"
error with zero indication as to why it fails.
What's going on here? Why is refactoring so borked?
---
hich forces manual refractoring(changing
> imports, mostly). This situation hasn't improved since Netbeans 9 and in
> Netbeans 11.2 it has somehow gotten worse. Now attempting to rename any
> method results in a "Java Refactoring threw java.lang.AssertionError"
>
nd in
Netbeans 11.2 it has somehow gotten worse. Now attempting to rename any
method results in a "Java Refactoring threw java.lang.AssertionError"
error with zero indication as to why it fails.
What's going on here? Why is r
I am using this feature of Netbeans very often.
In prior versions fields that already have getters and/or setters were marked
with gray dots on the popup screen.
I do not see them in version 11.1
Was it removed intentionally or I need to tweak some settings to see it?
Gary Greenberg
Staff Softwar
Cc: Mark J Koch; Neil C Smith; NetBeans Mailing List
Subject: Re: Refactoring Error when moving/renaming class.
Which of them has the highest priority to you? Are any blockers for the release?
Gj
On Fri, 5 Jul 2019 at 21:35, joe schmo
mailto:geekyguy...@hotmail.com>> wrote:
I have reteste
ley Campbell
> --
> *From:* joe schmo
> *Sent:* July 5, 2019 7:04 AM
> *To:* Geertjan Wielenga
> *Cc:* Neil C Smith; Mark J Koch; NetBeans Mailing List
> *Subject:* Re: Refactoring Error when moving/renaming class.
>
> Ok, would be happy to do that.
>
> BC
>
: Refactoring Error when moving/renaming class.
Ok, would be happy to do that.
BC
From: Geertjan Wielenga
Sent: July 5, 2019 6:41 AM
To: joe schmo
Cc: Neil C Smith; Mark J Koch; NetBeans Mailing List
Subject: Re: Refactoring Error when moving/renaming class.
It would
Ok, would be happy to do that.
BC
From: Geertjan Wielenga
Sent: July 5, 2019 6:41 AM
To: joe schmo
Cc: Neil C Smith; Mark J Koch; NetBeans Mailing List
Subject: Re: Refactoring Error when moving/renaming class.
It would be good if you'd verify if all
It would be good if you'd verify if all those issues are still issues with
11.1 beta-3 and specify that if so in those issues.
Gj
On Fri, Jul 5, 2019 at 11:25 AM joe schmo wrote:
> Just an FYI, before you open another issue..I've opened several issues
> ar
Just an FYI, before you open another issue..I've opened several issues
around refactoring
1503,1523,1532,1533,1535,1541,1542
Bailey Campbell
From: Neil C Smith
Sent: July 5, 2019 6:18 AM
To: Mark J Koch; NetBeans Mailing List
Subject: Re: Refactoring
Hi,
On Fri, 5 Jul 2019 at 07:18, Mark J Koch wrote:
> On NB 10 and also 11.1. I get this popup error when attempting to rename a
> Java class or move it to a new package. It tells me to look in var/logs for
> any error message but I’m not seeing any Java or NB related logs. OSX
> Mohave do
On Fri, 5 Jul 2019 at 08:01, Helmut Leininger wrote:
>
> see https://issues.apache.org/jira/browse/NETBEANS-2786?filter=-2
>
The log in this thread is on beta3. The log on that issue seems to be
beta2? Please recheck with beta3 as a fix for this issue was merged.
Thanks,
Neil
---
see https://issues.apache.org/jira/browse/NETBEANS-2786?filter=-2
Am 05.07.2019 um 08:33 schrieb Mark J Koch:
> I found this log under Notifications tab in the IDE and it seems to have the
> stack trace near the end.
>
>
>
>
>> On Jul 4, 2019, at 11:18 PM, Mark J Koch wrote:
>>
>> On NB 10 and
I found this log under Notifications tab in the IDE and it seems to have the
stack trace near the end.
---
>Log Session: Thursday, July 4, 2019 at 1:12:34 PM Pacific Daylight Time
>System Info:
Product Version
On NB 10 and also 11.1. I get this popup error when attempting to rename a Java
class or move it to a new package. It tells me to look in var/logs for any
error message but I’m not seeing any Java or NB related logs. OSX Mohave does
not seem to have a /var/log/messages at all on my system.
homas Kellerer wrote:
> Hello,
>
> with NB 11 I consistently get a NPE when trying to do any refactoring
> (rename class, constant, enum) in my Maven based project.
> This happened already with v1 and vc2, but id does NOT happen with NB 10
> on the same code base.
>
> The error
Hello,
with NB 11 I consistently get a NPE when trying to do any refactoring (rename
class, constant, enum) in my Maven based project.
This happened already with v1 and vc2, but id does NOT happen with NB 10 on the
same code base.
The error message asks me to attach the dump file from the
I have NetBeans 9.0 built from source and it seems to be working as well
(if not better) than 8.2 so far. I found the section that does
refactoring and am interested right now in the "Convert Constructor to
Builder" section as the generated code has to be tweaked to get it to
match
39 matches
Mail list logo
