[jira] [Created] (GROOVY-11091) Reflection bug

2023-06-10 Thread Blake McBride (Jira) 
Blake McBride created GROOVY-11091:
--

 Summary: Reflection bug
 Key: GROOVY-11091
 URL: https://issues.apache.org/jira/browse/GROOVY-11091
 Project: Groovy
  Issue Type: Bug
  Components: groovy-runtime
Affects Versions: 4.0.12
 Environment: Linux 64
Java 17.0.7
Groovy 4.0.12
Reporter: Blake McBride
 Attachments: Test3.java, Test4.groovy

groovyClass.getMethod throws an exception if the method name is "main" AND it 
takes a single, Object argument.  The attached simple sample demonstrates it.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Created] (GROOVY-8893) Breakpoints aren't working on NetBeans for dynamically loaded Groovy

2018-11-18 Thread Blake McBride (JIRA) 
Blake McBride created GROOVY-8893:
-

 Summary: Breakpoints aren't working on NetBeans for dynamically 
loaded Groovy
 Key: GROOVY-8893
 URL: https://issues.apache.org/jira/browse/GROOVY-8893
 Project: Groovy
  Issue Type: Bug
  Components: bytecode
Affects Versions: 2.4.15
Reporter: Blake McBride


Greetings,
 
I am using Groovy 2.4.15 under NetBeans 8.2 and Java 8 on a 64 bit Linux box.
 
I am dynamically loading Groovy with the following code:
 
if (groovyLoader == null)
groovyLoader = new GroovyClassLoader(GroovyClass.class.getClassLoader());
groovyClass = groovyLoader.parseClass(new GroovyCodeSource(new File(path + 
sourceFile)), false);
 
 
Doing it this way, when debugging the loaded class, I am able to set 
breakpoints from within IntelliJ and it works as expected.  However, NetBeans & 
VSCode ignore the breakpoints.
 
I do a similar thing with Java files, and NetBeans & VSCode honors those 
breakpoints.
 
There must be something different between dynamically loaded Java and 
dynamically loaded Groovy.
 
Thanks.
 
Blake McBride



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)