gvSIG bugs #4355

Scripting composer: Groovy printf statement is ignored in the console tab (log messages)

Added by Antonio Falciano over 7 years ago. Updated over 6 years ago.

Status:Closed% Done:

0%

Priority:NormalSpent time:-
Assignee:Joaquín del Cerro Murciano
Category:Scripting
Target version:2.4.0-2840 (rev. org.gvsig.desktop-2.0.208)
Severity:Major Add-on version:
gvSIG version:2.3.0 Add-on build:
gvSIG build:2444 Add-on resolve version:
Operative System: Add-on resolve build:
Keywords: Proyecto:
Has patch: Hito:
Add-on name:Unknown

Description

Same of #4250 and #4354 but relative to Groovy scripts. To reproduce the bug simply create the default Groovy script and execute it. Result: no "hola" is printed in the console.

Associated revisions

Revision 43553
Added by Joaquín del Cerro Murciano over 6 years ago

refs #4355, update groovy version to 2.4.12

History

#1 Updated by Joaquín del Cerro Murciano over 7 years ago

  • Target version changed from 2.3.0-2447-final (rev. org.gvsig.desktop-2.0.153) to 2.4.0-2850-final (rev. org.gvsig.desktop-2.0.220)

#2 Updated by Álvaro Anguix almost 7 years ago

  • Target version deleted (2.4.0-2850-final (rev. org.gvsig.desktop-2.0.220))

#3 Updated by Andrea Antonello over 6 years ago

I had not seen that this wa sknow for a year now.

I think we should not claim that groovy works if it definitely does not. This should either be solved or the groovy option in scripting should be removed from the possible options.

#4 Updated by Andrea Antonello over 6 years ago

  • Target version set to 2.4.0-2841-RC3 (rev. org.gvsig.desktop-2.0.209)

I will try to set the RC3 as target version, it would be really good to have.

#5 Updated by Antonio Falciano over 6 years ago

Andrea Antonello wrote:

I think we should not claim that groovy works if it definitely does not. This should either be solved or the groovy option in scripting should be removed from the possible options.

Hi Andrea,
I think that it should be fixed (if possible) it just in time, if someone has time and resources to do it. For instance, consider also #4646. It's incredible that nobody has noticed that System.out.println doesn't work since gvSIG 1.x! Fortunately, we can print in Jython at least. Instead, Groovy support is relatively more recent, but not tested clearly. So I'm agree with you: if a feature is broken, it's better to remove it or type in capital letters that it's unstable. My two cents.

#6 Updated by Joaquín del Cerro Murciano over 6 years ago

  • Target version changed from 2.4.0-2841-RC3 (rev. org.gvsig.desktop-2.0.209) to 2.5.1-3044

#7 Updated by Joaquín del Cerro Murciano over 6 years ago

Se trata de un bug de Groovy reconocido desde 2014:

Redirection of output in javax.script.ScriptEngine.invokeFunction() doesn't work
  https://issues.apache.org/jira/browse/GROOVY-7150

Parece que esta arreglado en la version 2.4.8 de Groovy (Jan, 2017).

Actualizare a la version 2.4.12 (Jun, 2017) que es la ultima estable.

#8 Updated by Joaquín del Cerro Murciano over 6 years ago

  • Target version changed from 2.5.1-3044 to 2.4.0-2840 (rev. org.gvsig.desktop-2.0.208)
  • Assignee set to Joaquín del Cerro Murciano
  • Status changed from New to Fixed

#9 Updated by Antonio Falciano over 6 years ago

Joaquín del Cerro Murciano wrote:

Se trata de un bug de Groovy reconocido desde 2014:

Redirection of output in javax.script.ScriptEngine.invokeFunction() doesn't work
https://issues.apache.org/jira/browse/GROOVY-7150

Parece que esta arreglado en la version 2.4.8 de Groovy (Jan, 2017).

Actualizare a la version 2.4.12 (Jun, 2017) que es la ultima estable.

Thank you very much, Joaquín!

#10 Updated by Antonio Falciano over 6 years ago

  • Status changed from Fixed to Closed

Also available in: Atom PDF