You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the war target, packageApp runs immediately before compilegsp,
Thus at eventPackagingEnd, we convert all haml files to gsp.
Unfortunately, packageApp also runs when we call "grail run-app",
so we will have .gsp files created throughout the view folder.
Currently seeking a work around for this. -- RM, 05/08/2010
I'm not sure what the problem is. Is PackagingEnd event triggered twice when running "grails run-app" ? or is it only triggered once? If it's triggered once then that's a good behavior right? What does "so we will have .gsp files created throughout the view folder." mean? Isn't that what we want?
Btw I'm trying to investigate this error message I'm getting when I run "grails run-app" : "Error Exception occurred trigger event [PackagingEnd]: com.cadrlife.jhaml.JHamlBatchConverter (Use --stacktrace to see the full trace)"
The text was updated successfully, but these errors were encountered:
In https://github.com/raymyers/haml4grails/blob/master/scripts/_Events.groovy
You have commented that
In the war target, packageApp runs immediately before compilegsp,
I'm not sure what the problem is. Is PackagingEnd event triggered twice when running "grails run-app" ? or is it only triggered once? If it's triggered once then that's a good behavior right? What does "so we will have .gsp files created throughout the view folder." mean? Isn't that what we want?
Btw I'm trying to investigate this error message I'm getting when I run "grails run-app" : "Error Exception occurred trigger event [PackagingEnd]: com.cadrlife.jhaml.JHamlBatchConverter (Use --stacktrace to see the full trace)"
The text was updated successfully, but these errors were encountered: