-
-
Notifications
You must be signed in to change notification settings - Fork 11.3k
Conversation
Kobalt is a build system. The test creates a simple source file and a build file and then it calls Kobalt on it. The test asserts a .jar file gets produced.
@@ -0,0 +1,48 @@ | |||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please remove this empty line.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
What was the other error? |
I didn't see the error any more after removing the version, I just pushed a new commit that address the comments. |
class Kobalt < Formula | ||
desc "Build system" | ||
homepage "http://beust.com/kobalt" | ||
url "https://github.com/cbeust/kobalt/releases/download/0.633/kobalt-0.633.zip" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just saw this URL: we need to build from source.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you saying that when someone installs Kobalt, you will build it from the source and then install the resulting binaries? (sorry if it's a silly question, I'm not very familiar with Homebrew's internals)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. The exception we make is if this is Java code; it's OK for us to not build from source there because the "binaries" work cross-platform.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Kobalt is written in Kotlin actually but same thing: the zip file contains a jar which is cross platform.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🆒
New changes are in, please take another look. Thanks! |
|
||
system "#{bin}/kobaltw", "assemble" | ||
output = "kobaltBuild/libs/test-1.0.jar" | ||
assert File.exists?(output), "Couldn't find #{output}" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Use File.exist?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
I see that And how come these tests pass on my machine? |
You passed on Jenkins. The failure was on the 10.9 Travis; the Travis machines often have connectivity problems so that may well be the root cause of failure on that:
|
@DomT4 Got it, thanks for the explanation. Any other outstanding items I should look at? |
If others are okay with the binary usage, we're pretty much good IMO. |
Thanks for your contribution to Homebrew! Without people like you submitting PRs we couldn't run this project. You rock! |
@MikeMcQuaid and everyone else: thank you guys for the quick turnaround and making this process so seamless! |
All Submissions:
You can erase any parts of this template not applicable to your Pull Request.
New Formulae Submissions:
brew audit --strict --online <formula>
(where<formula>
is the name of the formula you're submitting)?I'm getting:
I tried to remove the
version
but then I get another error. Can you help me fix this warning?brew install <formula>
?Changes to Homebrew's Core:
brew tests
with your changes locally?Kobalt is a build system. The test creates a simple source file and a build file and then it calls Kobalt on it. The test asserts a .jar file gets produced.