Wrong Groovy version (1.7.5) disables Groovy in JasperReports

Description

Groovy version 1.7.5 in org.adempiere.base causes Groovy to not function in JasperReports 5.1.2 which requires Groovy 2.0.1.

Solution, upgrade groovy in org.adempiere.base to Groovy 2.0.1.

Suggested code solution:
https://bitbucket.org/dantam/idempiere.se-historic/commits/d96dc6d3f18faf98967433d41d2aa8ab801c1611

Environment

None

Activity

Show:
Hiep Lq
October 5, 2015, 9:15 AM

Hi , what's way you deploy jasper report to idempiere? use source file or binary compile by ireport?
it's best to deploy source file.
also maybe add new configuration to set compatible level when idempiere compile jasper report.

Daniel Tamm
October 5, 2015, 9:27 AM

I actually mostly use binary compiled attachments. Thanks for the info. I'll start using sources from now on

Carlos Ruiz
October 5, 2015, 11:37 AM

Yes , will be great if you can help with tests for the upcoming release and maybe jasper 6.1.1

In my case I prefer to binaries instead of sources to avoid the overhead of compiling jasper every time.

Regards,

Carlos Ruiz

Daniel Tamm
December 25, 2015, 6:53 PM

Bumping this ticket. I really think Groovy JasperReports should be working in 3.1 ... but I'm guessing everyone is using Java since it hasn't been working out of the box for a long time in iDempiere...

https://bitbucket.org/dantam/idempiere-gaap/commits/e1816e772c6f699e8640939f82eb7e039c775bf6?at=release-3.1-dt-patch

Carlos Ruiz
February 22, 2019, 2:38 PM

Cannot reproduce in latest version 6.2 - groovy can be used.

Assignee

Daniel Tamm

Reporter

Daniel Tamm

Labels

Tested By

None

Time tracking

1h

Components

Affects versions

Due date

2015/09/25

Priority

Major
Configure