[ 
https://issues.apache.org/jira/browse/WHIRR-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12982195#action_12982195
 ] 

Tom White commented on WHIRR-209:
---------------------------------

This is since WHIRR-210, I think. I'm not sure why the JAR is not longer being 
created, but this is the correct behaviour since we shouldn't ship all the test 
dependencies (which is what WHIRR-210 fixed). I'm fine with closing this issue. 
We might also look at making the build less brittle by excluding the test jar 
from the binary distribution in whirr-build-tools/src/assemble-bin.xml.

> bin/whirr fails on a new release
> --------------------------------
>
>                 Key: WHIRR-209
>                 URL: https://issues.apache.org/jira/browse/WHIRR-209
>             Project: Whirr
>          Issue Type: Bug
>          Components: cli
>    Affects Versions: 0.3.0
>            Reporter: Andrei Savu
>            Assignee: Andrei Savu
>            Priority: Blocker
>             Fix For: 0.3.0
>
>
> Steps to reproduce: 
> {code}
> $ mvn package assembly:assembly
> $ cp target/whirr-0.3.0-incubating-SNAPSHOT.tar.gz /tmp
> $ cd /tmp
> $ tar xvfz whirr-0.3.0-incubating-SNAPSHOT.tar.gz
> $ cd whirr-0.3.0-incubating-SNAPSHOT/
> $ ./bin/whirr
> ./bin/whirr: line 24: [: 
> /tmp/whirr-0.3.0-incubating-SNAPSHOT/bin/../whirr-cli-0.3.0-incubating-SNAPSHOT.jar:
>  binary operator expected
> No CLI JAR found.
> {code}
> This is related to the changes made in WHIRR-156. I will provide a fix. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to