Giters

bertramdev / grails-asset-pipeline

Grails Asset Pipeline

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

asset-precompile should always compile Config.groovy

aadrian opened this issue · comments

commented

When running the asset-precompile, it should always compile the Config.groovy file with it's settings (or pick the changes to this file).

With version 2.9.1 + Grails 2.5.4 this is not the case and saved changes done by the user in Config.groovy seem to be ignored.

commented

This appears to work fine for me can you produce a test project?

Sent from my iPhone

On Jun 9, 2016, at 8:29 AM, aadrian notifications@github.com wrote:

When running the asset-precompile, it should always compile the Config.groovy file with it's settings (or pick the changes to this file).

With version 2.9.1 + Grails 2.5.4 this is not the case and saved changes done by the user in Config.groovy seem to be ignored.

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

commented

I can see this problem on several Windows machines (win7, win8.1, win10):

  • create a new project with grails create-app myproj
  • update the plug-ins to use 2.9.1 (or the latest) as suggested by grails list-plugin-updates
  • use Bower ( http://bower.io ) to get some JS dependencies under /myproj/grails-app/assets/bower_comopnents. Usual libs like momentjs, underscore, bootstrap, etc.,
  • because those libs also contain allot of junk, constant tweaking of Config.groovy (e.g. what to ignore) is required until asset-precompile delivers the correct and clean results.
    The effect is that once at the Grails prompt, changes made in Config.groovy won't be picked even if the user executes compile. Restarting of the shell and cleaning of /target is required in order for the changes to take effect.