[MGNLGROOVY-124] Error saving a new script not having the "is a script" check Created: 10/Oct/14  Updated: 18/Sep/17  Resolved: 20/Oct/14

Status: Closed
Project: Magnolia Groovy Module
Component/s: None
Affects Version/s: 2.3
Fix Version/s: None

Type: Bug Priority: Critical
Reporter: Daniel Lipp Assignee: Unassigned
Resolution: Not an issue Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: JPEG File Screen Shot 2014-10-10 at 11.24.43.jpg    
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Date of First Response:

 Description   

Steps to reproduce:

  • open Groovy App
  • select "Add script"
  • type something into "source" (or don't - doesn't matter)
  • press SAVE CHANGES (do not select "Is a script?")
    -> "An error occurred while executing an action..."


 Comments   
Comment by Federico Grilli [ 20/Oct/14 ]

This is actually the expected behaviour. The errors refer to compilation problems encountered when saving what the groovy module assumes to be a class (not a script). In such a case, some compile-level checks are enabled, e.g. consistency of package and class names so that, if the script is used e.g. as a model class, the groovy classloader can find it in the script repo, compile it and load it.

Generated at Mon Feb 12 05:55:49 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.