When I check out `arrow-core` and run `./gradlew b...
# arrow
j
When I check out
arrow-core
and run
./gradlew build
, I get this error:
Copy code
FAILURE: Build failed with an exception.

* Where:
Build file '/Users/bayo/dev/arrow-core/build.gradle' line: 2

* What went wrong:
A problem occurred evaluating root project 'arrow-core-lib'.
> Could not read '<https://raw.githubusercontent.com/arrow-kt/arrow/master/setup.gradle>' as it does not exist.
What am I doing wrong? I just want to be able to open and explore the source with all the features of IntelliJ that assist that to be available.
j
My guess would be that you are building a version of arrow that is not the current snapshot or you somehow don't have read access to our github repo containing the shared build files. Either way @Rachel will probably know best ^^
Also, @Rachel, if this is a version issue: Can on each release fix build files to a commit on master? This would ensure that at least every release rebuilds fine because without that we won't even be able to rebuild old releases right?
j
Thanks @Jannis! If read access isn't public, I'm pretty sure I don't have it. Is building the current snapshot the same as building master?
j
It should be public, this is the file it is most likely meant to use: https://raw.githubusercontent.com/arrow-kt/arrow/master/gradle/setup.gradle And the links come from here: https://github.com/arrow-kt/arrow-core/blob/master/gradle.properties and 4 days ago the links were changed there so make sure you are on a commit made in the last 4 days
r
Thanks @Jannis ๐Ÿ™Œ Hi @julian, please, try to update your workspace with the latest version of the
master
branch
and yes,
master
branch corresponds to the latest SNAPSHOT
please, let us know when it's working for you, thanks!!
๐Ÿ™๐Ÿพ 1
@Jannis to rebuild old releases, just a checkout of the same tag for the
arrow
repository and use local paths with
file://
I can share the scripts to do it if you're interested on it ๐Ÿ™Œ
@julian, is it working with a fresh workspace?
j
Hmm ok, are there any drawbacks with pinning the commit for each project though? That does seem like a nicer solution to me...
j
Thanks @Rachel! I'm about to try.
Wonderful! Built perfectly. Thank you @Rachel!
r
Great @julian!! ๐Ÿ‘ Thanks for the idea @Jannis !! No, there aren't drawbacks and Julian wouldn't have had this issue. Let's do it!! ๐Ÿ™Œ Thanks!!
๐Ÿ‘ 1