It's runnable because it is a jar with a shell script prepended to it -- so
it involves a separate step.

--
Jason Dusek
pgp // solidsnack // C1EBC57DC55144F35460C8DF1FD4C6C1FED18A2B


2014-03-10 23:16 GMT+00:00 Ross Allen <notifications@github.com>:

> In .travis.yml:
>
> > @@ -1,7 +1,26 @@
> >  language: scala
> >  before_script:
> > -  - "pushd src/main/resources/assets/ && npm install && ./bin/build && popd"
> > +  - export PROJECT_VERSION="`sed -n 's|.*<version>\(.*\)</version>.*|\1|p' pom.xml | awk '{ print $1; exit }'`" && echo Project version is $PROJECT_VERSION
> > +  - export ARTIFACT="marathon-runnable_$PROJECT_VERSION.jar"
>
> Given our tendency to use dashes in repo names, I would use an underscore
> between "marathon" and "runnable" to make it apparent "runnable" is not
> part of the project name.
>
> Is "runnable" helpful to have in the artifact name? It almost seems
> superfluous.
>
> —
> Reply to this email directly or view it on GitHub<https://github.com/mesosphere/marathon/pull/177/files#r10455477>
> .
>