ksoichiro / gradle-web-resource-plugin

Gradle plugin to use CoffeeScript, LESS and Bower libraries without Node.js/npm.
Apache License 2.0
23 stars 5 forks source link

wrong download path #5

Open lukaszpol opened 8 years ago

lukaszpol commented 8 years ago

hello, It seems that for some reason plugin is downloading all components to build/webResource/src/main/webapp/bower_components instead of build/webResource/bower_components. After that it doesn't move all downloaded components to lib (I think it is caused because of wrong path where all components are downloading). I am using Ubuntu 14.04 and Intellij Idea Ultimate 14. My gradle config is: webResource { base { src 'src/main' dest 'src/main/webapp/static'

}

bower {
    dependencies {
        install name: "jquery", version: "1.10.2"
        install name: "bootstrap", version: "3.3.6"
    }
}

}

ksoichiro commented 8 years ago

Thank you for your feedback. Unfortunately, I couldn't reproduce the problem (though it's Mac environment). What version of the plugin are you using? At least, with the latest version (v1.1.1), it should download dependencies to build/webResource/bower_components whether base.src is changed or not.

sratatata commented 8 years ago

@lukaszpol is using 1.1.1 version, he is in same team with me. Same Ubuntu system, same gradle file.. (Gradle is newest, bower is installed locally also (works)) I've no idea why it's downloading to build/webResource/src/main/webapp/bower_components.

Path is really strange, smilliar tour dest path, but differ as @lukaszpol mentioned in his post.

I've tried almost everything there... no idea.

ksoichiro commented 8 years ago

@sratatata Oh, thanks for your comment! I understand.

sratatata commented 8 years ago

@ksoichiro @lukaszpol which versions of nodejs you have installed. I've 4.2.4. Could be a matter?

sratatata commented 8 years ago

I've updated to newest 5.4.x and still works.

ksoichiro commented 8 years ago

You mean, globally installed node? In my environment it's v5.3.0, but I think it's not related to this issue. This plugin does not depend on node/npm.

lukaszpol commented 8 years ago

@sratatata I have npm 2.14.9 and nodejs v0.12.9, but ksoichiro state it doesn't depend on nodejs...

sratatata commented 8 years ago

You know drawning man catches at a straw. I just can't imagine why I'm the only one person in my team where this works. It has to be something with environment.