[
https://issues.apache.org/jira/browse/BUILDR-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12924017#action_12924017
]
Gerolf Seitz edited comment on BUILDR-303 at 10/22/10 4:43 PM:
---------------------------------------------------------------
This happened to me too.
My setup is:
Ubuntu 9.10
ruby 1.8
buildr 1.4.3
i removed all "buildr" executables from the path and specifically executed the
buildr executable from the gem => same result.
As Alex mentioned on the mailing list [0], adding -V removes the symptom, but
not the actual issue behind that.
[0] http://markmail.org/message/jck3oabsvobtzvfy
was (Author: seitz):
This happened to me too.
My setup is:
Ubuntu 9.10
ruby 1.8
buildr 1.4.3
i removed all "buildr" executables from the path and specifically executed the
buildr executable from the gem => same result.
As Alex mentioned on the mailing list
(http://markmail.org/message/jck3oabsvobtzvfy), adding -V removes the symptom,
but not the actual issue behind that.
> 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.
