[73cat] Re: Groovy / Java refactoring

  • From: Unai Vivi < >
  • To:
  • Subject: [73cat] Re: Groovy / Java refactoring
  • Date: Sat, 20 Oct 2012 10:07:13 +0200
  • Organization: V&V technologies

I would say bug, given that applying such refactoring does break your code

--
Unai Vivi
V&V technologies

On 20/10/2012 02:34, José Galaviz wrote:
One common use case of Groovy is the usage of Groovy classes with Java
projects.

I was trying to refactor a Java class which is referenced within a
groovy class like this:

/public class JavaClass {//}/

and

/class GroovyClass { def var=new JavaClass().toString();}/

If I try to refactor the Java class then I'm expecting the groovy class
to change the call to such class but it doesn't happen.

Should I file this a bug or as a feature request?

José Galaviz



[73cat] Groovy / Java refactoring

José Galaviz 10/20/2012

[73cat] Re: Groovy / Java refactoring

Unai Vivi 10/20/2012

[73cat] Re: Groovy / Java refactoring

Benno Markiewicz 10/20/2012

[73cat] Re: Groovy / Java refactoring

José Galaviz 10/22/2012

Project Features

About this Project

www was started in November 2009, is owned by jpirek, and has 21 members.
By use of this website, you agree to the NetBeans Policies and Terms of Use (revision 20140418.2d69abc). © 2013, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo
 
 
Close
loading
Please Confirm
Close