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
The example from the README fails like this for me:
...
> Task :generateProto FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':generateProto'.
> Could not resolve all files for configuration ':protobufToolsLocator_reactor'.
> Could not find reactor-grpc-1.2.4-linux-x86_64.exe (com.salesforce.servicelibs:reactor-grpc:1.2.4).
Searched in the following locations:
file:/home/dsyer/.m2/repository/com/salesforce/servicelibs/reactor-grpc/1.2.4/reactor-grpc-1.2.4-linux-x86_64.exe
...
I can see that .exe file in Maven Central. It works with Maven.
UPDATE: (hopefully useful for others in the same pickle, including future me) it works for me if you put mavenLocal()aftermavenCentral() in the repositories declaration. So someone, somewhere is not taking into account all the repositories.
The text was updated successfully, but these errors were encountered:
Not sure where exactly you mean I should do that. Here's the result:
> Task :generateProto FAILED
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':generateProto'.
> Could not resolve all files for configuration ':protobufToolsLocator_reactor'.
> Could not find reactive-grpc-1.2.4-linux-x86_64.exe (com.salesforce.servicelibs:reactive-grpc:1.2.4).
Searched in the following locations:
https://repo.maven.apache.org/maven2/com/salesforce/servicelibs/reactive-grpc/1.2.4/reactive-grpc-1.2.4-linux-x86_64.exe
The example from the README fails like this for me:
I can see that .exe file in Maven Central. It works with Maven.
UPDATE: (hopefully useful for others in the same pickle, including future me) it works for me if you put
mavenLocal()
aftermavenCentral()
in therepositories
declaration. So someone, somewhere is not taking into account all the repositories.The text was updated successfully, but these errors were encountered: