Wojciech Żarski
Wojciech Żarski
I've same issue.
@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...
@ksoichiro @lukaszpol which versions of nodejs you have installed. I've 4.2.4. Could be a matter?
I've updated to newest 5.4.x and still works.
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...
Another PC. Windows this time: ``` 11:21:01.280 [LIFECYCLE] [class org.gradle.TaskExecutionLogger] :publisher:webResourceSetupNodeDependencies 11:21:01.280 [DEBUG] [org.gradle.api.internal.tasks.execution.ExecuteAtMostOnceTaskExecuter] Starting to execute task ':publisher:webResourceSetupNodeDependencies' 11:21:01.280 [DEBUG] [org.gradle.api.internal.tasks.execution.SkipUpToDateTaskExecuter] Determining if task ':publisher:webResourceSetupNodeDependencies' is up-to-date 11:21:01.285 [DEBUG]...
Pure bower works on both of this computers. 1st: I've been trying to cleanup this cache. And directories was in fact existing. 2nd: yep, he is using git on daily...
This could have something with failing update test.
Yeah, but this seams to be workaround. I think that such functionality should be standard one in such tool.