asset:image tag w/ directory does not produce a hashed filename about grails-asset-pipeline

[davydotcom]

Ok I tried to reproduce this issue this morning and had no such luck. Can I ask which version of asset-pipeline you are running and which grails version? Also any other diagnostic information you might have

[jamesfredley]

I am running grails 2.3.6 with asset-pipeline 1.7.2. I saw this same behavior in 1.6.2 and tried 1.7.2 last evening before submitting.

I am building the site in GGTS 3.5.0.M2 which does not support Grails 2.3.7 properly, yet.

|Precompiling Assets!
|Processing File 1 of 346 - 180x180.png
|Processing File 2 of 346 - small\180x180.png

Plugins:

plugins {
        // plugins for the build system only
        build ":tomcat:7.0.50.1"

        // plugins for the compile step
        compile ":scaffolding:2.0.2" 
        compile ':cache:1.1.1'

        // plugins needed at runtime but not for compilation
        runtime ":hibernate:3.6.10.8" // or ":hibernate4:4.3.1.1"
        runtime ":database-migration:1.3.8"
        runtime ":jquery:1.11.0"
        runtime ":resources:1.2.7"

        // An alternative to the default resources plugin is the asset-pipeline plugin
        compile ":asset-pipeline:1.7.2"

        // Uncomment these to enable additional asset-pipeline capabilities
        //compile ":sass-asset-pipeline:1.5.1"
        //compile ":less-asset-pipeline:1.5.0"
        //compile ":coffee-asset-pipeline:1.5.0"
        //compile ":handlebars-asset-pipeline:1.0.0.3"
    }

[davydotcom]

I see the problem already…your on windows :) Backslash ill fix. thanks
-- 
David Estes
Sent with Airmail

On March 27, 2014 at 8:36:12 AM, jamesfredley ([email protected]) wrote:

I am running grails 2.3.6 with asset-pipeline 1.7.2. I saw this same behavior in 1.6.2 and tried 1.7.2 last evening before submitting.

I am building the site in GGTS 3.5.0.M2 which does not support Grails 2.3.7 properly, yet.

|Precompiling Assets!
|Processing File 1 of 346 - 180x180.png
|Processing File 2 of 346 - small\180x180.png

Plugins:

plugins {
// plugins for the build system only
build ":tomcat:7.0.50.1"

    // plugins for the compile step
    compile ":scaffolding:2.0.2"  
    compile ':cache:1.1.1'

    // plugins needed at runtime but not for compilation
    runtime ":hibernate:3.6.10.8" // or ":hibernate4:4.3.1.1"
    runtime ":database-migration:1.3.8"
    runtime ":jquery:1.11.0"
    runtime ":resources:1.2.7"

    // An alternative to the default resources plugin is the asset-pipeline plugin
    compile ":asset-pipeline:1.7.2"

    // Uncomment these to enable additional asset-pipeline capabilities
    //compile ":sass-asset-pipeline:1.5.1"
    //compile ":less-asset-pipeline:1.5.0"
    //compile ":coffee-asset-pipeline:1.5.0"
    //compile ":handlebars-asset-pipeline:1.0.0.3"
}

—
Reply to this email directly or view it on GitHub.

[davydotcom]

Ok if you go ahead and try out 1.7.3 run a grails asset-clean before trying to build your war. This should resolve your issue.

[jamesfredley]

No luck.

/assets/small/180x180-c903e2c9036ed0577a2351d8d597933d.png, does exist in the war. I also checked the previous builds and they included files with hashed names in the directories.

<asset:image src="small/180x180.png"/>

still becomes

<img src="/assets/small/180x180.png">

instead of the expected

<img src="/assets/small/180x180-c903e2c9036ed0577a2351d8d597933d.png">

I built the war a few times. Also tried removing resources:1.2.7.

[davydotcom]

Ok time to break out the PC

Sent from my iPhone

On Mar 27, 2014, at 8:49 PM, jamesfredley [email protected] wrote:

No luck.

/assets/small/180x180-c903e2c9036ed0577a2351d8d597933d.png, does exist in the war. I also checked the previous builds and they included files with hashed names in the directories.

<asset:image src="small/180x180.png"/>
still becomes

instead of the expected I built the war a few times. Also tried removing resources:1.2.7.

—
Reply to this email directly or view it on GitHub.

[davydotcom]

Confirmed this is fixed in asset-pipeline version 1.7.6

Make sure you run the commands listed below to ensure we clear out the old asset manifest.

grails clean
grails refresh-dependencies
grails asset-clean

[jamesfredley]

Works great. Thanks.