groovy

GroovyClassLoader should attempt to reload class after compilation error

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 1.0-JSR-5
  • Fix Version/s: 1.0-JSR-6
  • Component/s: None
  • Labels:
    None
  • Number of attachments :
    0

Description

Currently if you modify a class and then reload it with the new GCL reloading capability and the compilation fails all future calls to loadClass will throw ClassNotFoundException even if you correct the problem causing the compilation error. The GCL should attempt to reload the class even if a compilation error occured previously thus allowing users to fix the problem and reload again.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Graeme Rocher added a comment -

Sorry ignore me.. was my mistake

Show
Graeme Rocher added a comment - Sorry ignore me.. was my mistake
Hide
Permalink
Graeme Rocher added a comment -

Actually this is the case. It is quite important that this one is fixed as if you get a compilation error in Grails you have to restart the server

Show
Graeme Rocher added a comment - Actually this is the case. It is quite important that this one is fixed as if you get a compilation error in Grails you have to restart the server
Hide
Permalink
blackdrag blackdrag added a comment -

the GCL now doesn't cache entries for failed parsing or missing classes, so this is fixed

Show
blackdrag blackdrag added a comment - the GCL now doesn't cache entries for failed parsing or missing classes, so this is fixed

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.