[
https://issues.apache.org/jira/browse/BUILDR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924380#action_12924380
]
Gerolf Seitz commented on BUILDR-303:
-------------------------------------
Alex, thanks for the clarification. It was indeed an environment issue + layer
8 fail.
First, my /usr/bin/buildr was a softlink to the (outdated) buildr executable in
/var/lib/gems/1.8/gems/buildr-1.4.0/bin/buildr.
Second, only after installing the buildr gem again with verbose output did I
see that there's also a script at /var/lib/gems/1.8/bin/buildr.
This script has all the magic wrt to the _1.4.3_ parameter.
Since I only use ruby and rubygems for buildr, I'm not very familiar with the
gem environment and I only looked for the buildr script in the
.../1.8/gems/buildr-xxx directory.
With the correct link in place, all is fine now.
Maybe it would be good to mention this on the website in the install section.
Thanks for the help and please feel free to close this issue again.
> Release task assumes _1.3.4_ command-line argument convention works across
> platforms
> ------------------------------------------------------------------------------------
>
> Key: BUILDR-303
> URL: https://issues.apache.org/jira/browse/BUILDR-303
> Project: Buildr
> Issue Type: Bug
> Components: Core features
> Affects Versions: 1.3.4
> Reporter: Alex Boisvert
>
> Joel Muzzerall reported:
> I am trying to run
> buildr release
> but it produces this error:
> /usr/bin/ruby1.8 -S buildr _1.3.4_ --buildfile *snip* --environment
> development clean upload DEBUG=no
> (in *snip*, development)
> Buildr aborted!
> Don't know how to build task '_1.3.4_'
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
