How to disable caching of compiled code

Description

*This issue has moved*

This issue has been moved permanently to Adaptavist's Product Support JIRA instance.

All existing users of this instance should have the same username on our Product Support instance. However, you will very likely need to click on the
Can't access your account link in order to reset to a new password.

Jamie,

In you introduced the caching of the compiled groovy script, so it can be reused.

Is there a way to disable this 'recompilation' behaviour.
I'm trying to do some development, but the changes are not being
picked up although the file timestamp is changed ...

Francis

Environment

None

Activity

Show:
Jamie Echlin
March 18, 2012, 11:38 AM

Possibly slightly optimistic, but resolving this as a dupe of GRV-96. Have done a lot of work on class-reloading and it's working for me. Not totally sure about dependent classes, but it's worth a look.

Francis Martens (iDalko)
December 28, 2011, 4:32 AM

Jamie,

Can you revisit this issue.
The trick you provided to recompile dependent code doesn't work for 1.7.14.
(Sorry I never marked this as resolved)

Francis

Jamie Echlin
June 17, 2011, 12:18 PM

OK, if it's a dependent class that's a bit different. Is it a compiled class? The following code may work, and only need to be executed once:

OTOH, I paid for JRebel (with my own money too), which works very well for me.

Francis Martens (iDalko)
June 16, 2011, 11:18 AM

Dependent class.
It's pretty easy to test

put something like log.debug("statement 1")
run it
change it into log.debug("statement 2")
run it again

if 'statement 1' is in the logging you know you're in trouble.
It is easily reproducible on 1.7.6. Reverting to 1.6 solves the problem.

Will try the clear cache trick.

Francis Martens (iDalko)
June 16, 2011, 11:18 AM

Dependent class.
It's pretty easy to test

put something like log.debug("statement 1")
run it
change it into log.debug("statement 2")
run it again

if 'statement 1' is in the logging you know you're in trouble.
It is easily reproducible on 1.7.6. Reverting to 1.6 solves the problem.

Will try the clear cache trick.

Duplicate
Your pinned fields
Click on the next to a field label to start pinning.

Assignee

Jamie Echlin

Reporter

Francis Martens (iDalko)

Internal Complexity

Unknown

Internal Value

Unknown