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
I understand this might not be the primary objective of this Gradle plugin, but maybe it's a nice feature to have.
I see your plugin is already able to provide a working sass that uses jruby, itself automatically provided by the jruby-gradle-plugin.
However, that sass tool is not callable from the command line directly.
My goal is to integrate gradle/sass/grunt/grunt-contrib-sass properly.
The grunt-contrib-sass plugin is checking for the sass binary in the environment PATH.
I'm using the com.moowork.grunt Gradle plugin to call grunt.
And I'm able to configure the environment PATH from Gradle on the grunt_build task (GruntTask).
Is there someway I could ask for the sass tool to be installed locally (with a compassInstall task for example), and then retrieve the path of the executable, to be used in an external tool ?
Thank you!
Regards,
Olivier
The text was updated successfully, but these errors were encountered:
Hello,
I understand this might not be the primary objective of this Gradle plugin, but maybe it's a nice feature to have.
I see your plugin is already able to provide a working sass that uses jruby, itself automatically provided by the jruby-gradle-plugin.
However, that sass tool is not callable from the command line directly.
My goal is to integrate gradle/sass/grunt/grunt-contrib-sass properly.
The grunt-contrib-sass plugin is checking for the sass binary in the environment PATH.
I'm using the com.moowork.grunt Gradle plugin to call grunt.
And I'm able to configure the environment PATH from Gradle on the grunt_build task (GruntTask).
Is there someway I could ask for the sass tool to be installed locally (with a compassInstall task for example), and then retrieve the path of the executable, to be used in an external tool ?
Thank you!
Regards,
Olivier
The text was updated successfully, but these errors were encountered: